So I read up on this, and it would be great to learn more. Such as..
API & Third-party Integrations: Does La Suite expose APIs that allow integration with external tools and services?
What's the current roadmap for pre-built connectors or integrations with commonly-used government systems?
Cross-Tool Workflows: Beyond the "same interface" access, how seamlessly can users automate workflows across different La Suite tools?
For example, can a Visio meeting recording automatically trigger document creation in Docs, or data collection in Grist?
Does La Suite support webhooks, automation rules, or workflow orchestration (IFTTT-style logic) to reduce manual repetitive tasks?
Identity & Access Management Integration: Beyond ProConnect, can La Suite integrate with existing government LDAP/Active Directory systems for organizations with different identity providers?
Data Synchronization: Are there automated sync capabilities between Grist databases and other data sources, or between Fichiers and external file storage systems?
Export Format Coverage: The site mentions reversibility in standard formats (.ppt, .xls, .odt). Does this apply equally to all tools?
Specifically, what export formats are supported from Docs, Grist, and other collaborative tools?
Import Capabilities: Can users import content from competing tools?
For instance, can users migrate Grist tables from Excel with full formula preservation, or import documents from other collaborative platforms?
When collaborating in Docs or Grist, can users work with non-native file formats (e.g., editing .docx files directly without conversion loss)?
Metadata Preservation: Does La Suite preserve document metadata, formatting, comments, and revision history when exporting and re-importing files?
Interoperability with Open Standards: Beyond exporting to common formats, does La Suite use open file standards internally (e.g., ODF for documents, OpenDocument Spreadsheet for Grist)?
Lock-in Prevention: Are there documented procedures and guarantees for bulk data export in case an organization decides to migrate away from La Suite?
Well yes it has changed. But look at everything that can be accomplished with these abstractions/libraries/frameworks that exist.
Why reinvent the wheel.
Yes, there might be less room for the Wild Wild West approach, as mentioned in the article: But that is the structure of compounded knowledge/tooling/code available to developers/others to create more enriched software, in the sense that it runs on what is available now and provides value in today's age of computing.
I also had a 486DX2-66. And I recall coding in Assembly, Pascal, C etc.
I do not miss it. These days I can create experiences that reach so many more people (a matured Interneet with realtime possibilities - to simplify) and with so much more potential for Good. Good in the sense of usefulness for users, good in the sense of making money (yeah, that aspect still exists).
I do understand your sentiment and the despairing tone. There have been times when I was struck by the same.
But I do not miss 1995 and struggling with a low-level formatted HD and Assembly that screwed up my floppy disks, or the worms that reached my box, or the awful web sites in terms of UX that were around, or pulling coaxial cables around for LAN parties.
It's just a different world now. But I get what you are saying, and respect it. Stay optimistic. :)
The pressure to go all-in on Microsoft 365 is real—but so are the costs and lock-in risks. A hybrid approach can make sense, but only if you understand what you’re actually paying for. This isn’t an argument against M365. It’s about being honest about trade-offs.
Completely agree. SO is full of self-proclaimed "experts" who simply are not helpful. It is a toxic site. Amusingly, I have noticed how the most unwelcoming, unreliable, and lone wolf developers (colleagues) in my past five companies used their SO metrics as signs of their worth.
"This essay by Christopher Henner, a former Wikimedia Foundation Board Chair, argues that Wikipedia faces an existential crisis: while global internet users grew 83% since 2016, Wikipedia's page views declined 9%, and new contributor registrations dropped 36%. He attributes this to Wikipedia's failure to serve the Global South (where most new internet users came from), its outdated desktop-centric design, and AI systems that train on Wikipedia content without sending traffic back. Henner calls for urgent action within two years, including diversified revenue through AI partnerships, aggressive investment in knowledge equity, and a willingness to fundamentally restructure the organization's governance and priorities.
As for whether he's whining: I'd say no. The piece is data-driven, self-critical (he acknowledges his own role in building the systems that created these problems), and proposes concrete solutions rather than just lamenting the situation. It reads more like a wake-up call from someone who genuinely cares about an institution he's devoted two decades to, even if the tone is occasionally dramatic. The frustration is palpable, but it's directed at mobilizing action rather than seeking sympathy."
Please, feel free to use this summary and save precious time instead of reading the long, oh so long, text that is linked to.
This is an awful initiative, if true. For a company like Microsoft with (to say the least) a strained relationship with privacy advocates, users, and corporations - This can only lead to even less trust in Microsoft's business practices.
Yes, this does come across as a lengthy quasi-philosophical piece by a developer. Many words, simple truth: Software development does not need -only- human software developers trained in computer science anymore. Thanks.
I agree with the question "is Wordpress.org GDPR compliant?", but I think that the scope can be widened: "Is Wordpress.org subject to illegal management?"
