France's homegrown open source online office suite

French and European open source context

• Many commenters highlight that France has a long, underrated FOSS history (VLC, QEMU, ffmpeg, Docker, Scikit-learn, Framasoft, PeerTube, etc.).
• La Suite is framed as part of a wider European “digital sovereignty” push, with similar efforts in Germany (OpenDesk) and the Netherlands (MijnBureau).
• Some see this as a concrete example of “public money, public code” and note collaboration across countries and with existing OSS like Matrix, LiveKit, OnlyOffice/Collabora, BlockNote, and Yjs.

Online suite and digital sovereignty goals

• Online delivery is defended for:
  • Cross‑OS availability with just a browser.
  • Easier deployment, updates, and collaboration (Google Docs–style sharing).
  • Server‑side document management in mixed OS environments.
• Critics argue that relying on web standards and browsers dominated by non‑EU actors weakens “sovereignty.”
• Supporters counter that browsers (e.g., Firefox forks) and Git-based infrastructure are forkable and replaceable, whereas proprietary office/cloud services are not.

GitHub and dependency concerns

• Hosting source on GitHub is seen by some as ironic for a sovereignty project; others call it pragmatic:
  • Code is easy to mirror or move; Git removes lock‑in.
  • Only source code, not state documents, is on GitHub.
  • Many assume an internal government repo is the authoritative origin.

Scope: office suite or collaboration wiki?

• Multiple commenters say this is not (yet) a full “office suite” but more like Notion/Confluence:
  • Focus on notes, wikis, collaborative docs, chat, video, etc.
  • Traditional formatted word-processing and spreadsheet use is expected to be handled via LibreOffice/OnlyOffice/Collabora.
• Project FAQ explicitly states it is not trying to be a Microsoft Office drop‑in replacement; goal is “content over form,” fewer features, less lock‑in.

Technology choices and performance

• Backend in Django/Python and frontend in React/TypeScript draws mixed reactions:
  • Critics worry about performance, scaling, and “LLM‑like” React code full of useEffect and any.
  • Defenders emphasize Django’s maturity, speed of development, built‑in admin, and adequacy for government-scale use.
  • Debate ensues about whether dynamic languages are inherently too slow vs. issues being mostly design/DB-related.
  • Some argue a serious Office/Google Docs competitor would need C++/WASM‑style engineering; others say this project doesn’t need hyperscaler scale.

Funding, strategy, and realism

• One camp argues real independence would require guaranteed, long‑term funding in the tens of billions, even at the cost of higher taxes; another calls that economically misguided and prefers private enterprise plus strong antitrust.
• Skeptics call the current effort a “toy” or hackathon‑level; supporters respond that it’s a multi‑year DINUM initiative already deployed in some administrations, and that replacing US suites partially and gradually is both realistic and strategically valuable.