NetBSD integrated Lua, but Rust is a non-starter in the core of NetBSD because: rust does not compile verywhere, keeping rust working is quite a bit of work, the bootstrap relies on a binary package of the previous version, the compiler would have to be part of the base system and the release cycle of Rust is not compatible with the NetBSD ones.

Bloctel est dedié au téléphone, en dehors du démarchage pour les travaux sur la rénovation énergétique.

SignalSpam est le service dédié aux mails.

Signal Conso est dédié au reste il me semble.

That's awesome for dev and UX feedback. It w. It follows the trend that the tool only exports into a human readable format and that's more than enough.
The UI or the interpretation of the JSON can be built later on.

Uxnote is an annotation bar for mockups and websites. Drop a single script to get text highlights, element pins, numbered cards, color theming, a dimmed focus mode, import/export, and email handoff. No plugin and no backend required.

It's similar to https://loomflows.com/ but minimalistic and provide full-control over the data.

It is made with single goal of minimizing friction between citizens and Emergency services - featuring real-time communication, location-based reporting, seamless interaction between reporters and authorities, and live tracking.

Built during an hackathon, so there are many potential improvments. The project looks great though.

Add a beautiful background to the screenshot

from https://www.jaydip.me/

It can be very interesting for all cases where a cms is too much, but static site generator is not usable enough for content editors

Enshittification of Postman (no offline mode), the performance crisis

I know hurl that can be useful. The author lists the ideal API tool:

• local-first
• file-system centric to be stored in the VCS
• zero login wall
• git native collaboration
• native performance
• extensible design
• universal imports (OpenAPI, GraphQL, ...)
• proxy agnostic. It must be designed to proxy traffic through any interception tool. Proxy-aware or browser-based architecture is must have.
• scripting & Auth flows. Pre-request & post-response hooks.
• Straightforward testing. Built-in support for writing and running tests against API responses by code.

For every Postman or Insomnia, there’s a Bruno, Hurl, or Httpie

Idea -> Programming -> Feedback. Repeat.

Half of those [students] who started from scratch had working designs.

Script a demo in a demo.tape file and generate a gif for it.

It can be useful for later. It seems broken on Firefox though.

A dialog transition. It can be definitely useful instead of heavy implementations. Here is a lightweight implementation without JS.

With the tool https://weasyprint.org/

Following Building a browser API in one shot, the Codex CLI agent built a minimal web browsers with 20 000 lines of Rust that successfully renders HTML, CSS with no Rust create dependencies at all. It uses OSes for it.

See the flexbox implementation: https://github.com/embedding-shapes/one-agent-one-browser/blob/0.1.0/src/layout/flex.rs

The project: https://github.com/embedding-shapes/one-agent-one-browser

and the original post of the author https://emsh.cat/one-human-one-agent-one-browser/

IndexedDB built with 92% successful tests

I enjoyed the experience and don’t regret it, but experiments like this cheapen the efforts I’ve made over the years. It reduces the value of things. I think this is partly why so many of us have a knee-jerk reaction to reject these tools: if they work, then they’re frankly insulting.

Simon Willison predicts a webbrowser will be built by AI until 2029.