345 private links
The website we needed
The website we needed
For a software release, it is relevant to include what the software is doing.
I just have no idea what three quarters of these projects actually do. When you announce a new release, please give us (your adoring but slightly confused audience) just a tiny bit of context. What the software does, why the release is cool and what it requires to work.
It claims complying with the GDPR
A free open-source chat platform
Lessons from maintaining an open source tool:
- Simplicity is a feature
- Real users reveal problems
- open source is a marathon
Yet through all these changes, the need for efficient HTML delivery remains constant. That's perhaps the most interesting lesson: fundamental problems persist even as technologies evolve.
The small libraries will disappear. The one function util libraries can be generated by AI.
The open source model is kind of broken because og 6 points detailed in the post. The author retails then the example of Quiet UI by Cory Laviska
The guy launched Showelace, Web Awesome and Quiet UI.
Google uses AI to report security vulnerability.
They order a fix and they plan to release the vulnerability after 90 days.
FFmpeg is an open source project though. The project owes nothing to Google, and Google has no right to impose anything on the project. The company can largely finance or submit fixes.
So RSS won't be supported anymore and other formats too.
Only the web HTML + CSS + JS will remain and Chrome is pushing implementations at a faster pace that the other browsers can not . There is effectively an attempt to capture the web by Google.
I remember the library for XLST used in browsers is not maintained by the big corporations. Ah it's LibXML.
The depreciation notice: https://groups.google.com/a/chromium.org/g/blink-dev/c/CxL4gYZeSJA/m/yNs4EsD5AQAJ
Ah yes, a maintainability thing "Chromium uses the libxslt library to process these transformations, and libxslt was unmaintained for ~6 months of 2025".
Usage of the JS XSLTProcessor API is fairly volatile, registering somewhere between 0.01% and 0.1% of page loads, averaging around 0.05% over time. These numbers are above the typical 0.001% deprecation threshold. Again, we feel that the increased potential for breakage is balanced by the reduced security risk to 100% of Chromium users.
It's for security reason? XSLT users hacked are 0. Where are the security vulnerability?
Libxml2 maintainer steps down. He is thanklessly maintaining the thing since 1999. Literally the XKCD comic about "a project some random person in Nebraska has been thanklessly maintaining since 2003". All browsers vendors and companies are using it under the hood.
Garbage security reports are generated and it floods the cURL project.
The unpaid work of volunteers for core libraries is unsustainable. We can all agree on that.
There is few comments suggesting sustainable models.