394 private links
A great explanation of how servo came to be and how is it developed now.
It highlights Rust advantages over C++ (massive parallelism, ...) and its independance. Servo is hosted under the Linux Foundation and managed openly by the Technical Steering Committee.
A webview (for android and apps) is currently built!
Recent developments: Incremental layout (computation optimisation), WebDriver support to automate the browser (and testing), SVG support and DevTools from Firefox
Plans: editability and interactivity enhancements, CSS Grid Layout support, Embedding API, initial accessibility support and performance improvements.
Long-term: leading embeddable web rendering engine ecosystem, powering innovative applications and framework, offering unparalleled performance, stability and modern web standards compliance.
All infos can be found on https://github.com/servo or https://servo.org/
An example of semantic class names and a teaser on server of Kelp to have dynamic HTML through WebComponents.
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.
Geburt des ersten Kindes: -1.6 auf einer Skala von 0 (unglücklich) bis 10 (glücklich(.
Zum Vergleich:
- Tod des Partners: −1
- Arbeitslosigkeit: −1
- Scheidung: −0,6
Studie im 2015 veröffentlicht.
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?
Pas lu, mais ce sera utile pour plus tard.
Je ne dis pas que l'outils CompactGUI est mauvais. Je dis juste qu'encore une fois ce sont des développeurs indépendants qui compensent un manque de Windows.
Alors je sais, mais je vais mon vieux chieur linuxien bien lourd avec cette vieille blague pourrie : "Linux, il a y moins bien, mais c'est plus cher : Windows."
one [idea] that I’m calling “just call clone (or alias)”. This proposal specializes the clone and alias methods so that, in a new edition, the compiler will (1) remove redundant or unnecessary calls (with a lint); and (2) automatically capture clones or aliases in move closures where needed.
Cela fait du bien d'avoir des sites de professionnels qui ne sont pas du tout versé dans l'informatique.
Domain-Specific Languages are small languages designed to focus on a specific aspect of a software system. We deal with DSLs every day: SQL can be considered a DSL, LaTeX is a DSL, AWK is a DSL, Kubernetes’ YAMLs are a DSL.
The Token-Oriented Object Notation is optimized to have fewer tokens to parse for LLMs.
A domain-specific language is by definition smaller in scope than a general-purpose language, so it should be easier to design and implement; moreover, if the language is designed well, it should lead to a more efficient usage of the context window.
If we can abstract away parts of our domain into a higher-level language, we can effectively use the LLM to
- generate the implementation of a DSL
- generate documentation and examples for such our DSL
- point the LLM to docs and examples and prompt it to generate more code using our DSL
So, instead of trying to come up with a general-purpose language for LLMs, we define a tiny DSL for each specific subsystem we mean to realize.
Examples
- Piano
- Business Rule
About maintenance: the author claims they can be automated with LLMs.
The cost of defining an external DSL (own language with syntax and parser) is reduced compared to internal DSL (in a generic programming language). Also not a problem with LLMs.
In recent years, there has been something of a “winter” in DSL design and development due to the high maintenance costs and the tooling expectations from end users. This blog post explored the syntactic dimension of “token-efficiency” in DSL design: I invite you to explore more of this space, including semantics; I, for one, will welcome more crazy DSL implementations!
Faker again. T1 remporte les championnats du monde pour la sixième fois, c'est impressionnant de régularité.
Par sa popularité, la discipline est devenue une source de fierté nationale pour la Corée du Sud.
and the use of AI on the codebase. KeepassXC rules are clear for AI usage:
- As an additional pair of “eyes” in code reviews.
- For creating pull requests that solve simple and focused issues, add boilerplate code and test cases.