Starting with raw HTML, then provides more features with JS

Aujourd’­hui c’est Google Chrome qui a la main et on voit appa­raitre le même schéma que par le passé. [...]
La situa­tion n’est pas exac­te­ment la même que celle des années 2000 mais elle n’est pas si éloi­gnées que ça.

Il y a plein de navi­ga­teurs mais en réalité Brave, Opera, Vivaldi, Inter­net Explo­rer et les autres sont des déri­vés de Chro­mium. Chro­mium c’est la base open source de Chrome, contrô­lée par Google.

Une fois qu’on a retiré tout ce qui se base sur Chro­mium, il reste Safari et Fire­fox.

Rust tends to attract those that:

1. understand the intrinsic complexity of software;
2. have a realistic opinion about their ability to deal with accidental complexity (or lack thereof);
3. that look beyond the happy path and methodically reason about failure modes;
4. value consistency and predictability.

🇫🇷 Carte des territoires européens selon le nombre d'années passées sous contrôle de la France (843-2025)

Aussi disponible sur Reddit https://www.reddit.com/r/france/comments/1j05d6x/carte_des_territoires_europ%C3%A9ens_selon_le_nombre/

Hyping yourself is about accurately explaining the value that you contribute. It’s about saying, “Here are all my accomplishments; here is what I’ve been up to; here are the ways that I’ve been growing and will continue to grow.” You demonstrate to others why you’re worth it and you show up with the receipts to back every claim you make.

Keep a Hype doc for it.

A Hype Doc is a running list of all your accomplishments and successes. It’s a place where you keep track of your growth, and regularly jot down the things you’re proud of doing.

It includes: technical work completed, projects led or contributed to, mentorship and development, leadership opportunities, blog psots and talks revelant to your work, involvment in recruiting and interviewing, valuable contributions to discussions, kudos and feedback from others, significant moments of growth or learning.

Update it regularly (weekly?), it should be easy to edit and can be shared to managers.

Why Firefox forks is not a solution.

1. No fork is doing large-scale engineering work on the browser.
2. Some forks keep insecure APIs
3. Mozilla code is still running under the hood. They must be trusted as for the Firefox browser.
4. The fork is still 99.99% Mozilla code contributions
5. The fork can need more time to apply fixes

A lightweight browser of automation.

It integrates well with Puppeteer or Playwright.

A bundle size analyzer for rust

Un retour pertinent sur les choix entre PAAS et faire soi-même.

The business apps are characteristic because their main complexity comes from the domain: which is not hardware/software related but it's more about modelling complexities of human interactions in code.

The author tells Rust is not good for business apps.

• The stdlib abstractions are right in size and scope, but they are lacking concrete implementations (RNG, cryptoghraphy, serialization, ...). The crate ecosystem is enormous, but it takes time and attention to to sift the wheat from the chaff. Attention that is limited and could be put to better use elsewhere.
• Business apps requires solid defaults for common problems that are desired
• Lifetime and mutability modifiers can not be abstracted the same degree as regular generics
• Cyclic data structures are hard in Rust, because of the borrow checker
• The borrow checker also explicitly makes a conservative assumption that if you call method over some reference, this method will try to access ALL fields of that references, forcing any other field accessed outside of it to be invalidated: the structs must be build in respect to the borrow checker.
• Performance of business apps rarely matters, because the underlying
• To gain performance optimization out of Rust, you need more than "it compiles". Its performance ceiling are excellent (some platforms .NET or Swift choose to work closer to the metal), but its time to performance is low: it falls behind many managed languages on that metric.
• Arc/Rc or Box have few issues: this technique of allocating is nowhere near as fast as bump pointer allocators that managed languages use. The actual win here is when we need to release memory: which in Rust doesn't introduce GC pauses.
  and more

  You're here to solve business problems, yet on every step you need to solve "plumbing issues", make decisions about memory model including possible feature changes and refactoring they'll require in the future. [...] you're not going to be praised because your asset management app takes 10% less CPU while the task backlog has doubled in the meantime.