Emen15

The interesting question is not "can LibreOffice replace Word" but whether Denmark is restructuring identity, device management, and procurement to avoid recreating lock in elsewhere. Office is visible, but AD or Entra, MDM, compliance tooling, and vendor tied workflows are the real gravity wells. The success metric is not feature parity. It is whether dependency risk is measurably reduced over a 5 to 10 year horizon without fragmenting operational continuity.

Since dyslexia exists on a spectrum, it's not surprising that no single dyslexia font shows consistent benefits in controlled studies. Fonts may still affect comfort or personal preference for some individuals, which isn't the same as consistent gains.

Right, I noticed my best tools come from solving a problem that I personally hit daily. Generalizing too early made progess slow, and quality drops.

Perl 5's non-breaking conservatism kept old scripts running forever, but it also meant there was never a clear migration path the way Python 3 eventually provided, and that made long term planning a lot harder.

What really stands out to me in this migration story isn't the technical side at all, but the reminder that "feature parity" isn't the real hurdle here. Codeberg is already good enough for most day to day workflows; what it doesn't have is the gravitational pull GitHub built through network effects, integrations, and plain old inertia.

Feels like this is carving out a middle layer, simpler than other gateways out there, but way more practical than just a unified client library.