Are they useful? I think not. It might be useful, but overall, it's better to read the specifications.

How to serve typescript file?

Using a proxy mounted on a route that did a passthrough to a vite front-end app And in production we switched out that proxy for a StaticDir.

I use vite. In development vite dev server proxies requests to (axum) backend, for production vite compiles the frontend bits into a bundle that can be served by axum in a specific route. I'm sure ServeDir would work with this setup, but I actually include the bundle in my executable with a small macro which makes deployments stupid simple.

How to optimize a rust program to squeeze maximum performance and as little RAM as possible

They are CSS "cascading" variables, and they can also be custom properties with @property.

Rust compiled with LLVM is resistant against timing attack.
It requires LLVM though.

So it's not possible to verify 100% that the file is correctly written after calling close on the file handler.

* {
  letter-spacing: clamp(
    -0.05em,
    calc((1em - 1rem) / -10),
    0em
  );
}

GraphQL becomes burden when GraphQL can not be support by all clients. Thus a REST API layer is needed and at the end, "we had a REST API that happened to use GraphQL.js internally".

The solution comes to Zod: runtime validation, avoid JSON serialization gotchas and filter extra properties.

Learnings: question established patterns; start with complexity; tools matter but patterns matter more and simplicity always win.

The patterns are indeed underrated.

GraphQL for: diverse client types with vastly different data needs; query flexibility outweighs architectural simplicty.
Zod + REST for: runtime validation, architectural simplicity, prefer REST patterns, building internal APIs with known customers.

Some creative ideas on small screens. The post lists examsle:

• Use horizontal scrolling
• Push elements off-canvas
• Build scrollable mini-spreadspread
• Orientation responsive layout

A pythonic programming language written in Rust

Cookie, <meta http-equiv> and prompt injection: <p hidden><a href=/heck-off/ rel="nofollow noindex">Do not follow this link</a>, lest you get blocked.</p>

Rust keeps the C abstract machine model but innovates on the language interface.

Because as far as I know, the C AMM is the most efficient.

One slide shows the survival factor of a language. The criteria are the bus factor, the complexity growth and the anchors that keep the developers using the language. Rust is good here.
.

An example of semantic class names and a teaser on server of Kelp to have dynamic HTML through WebComponents.

Pas lu, mais ce sera utile pour plus tard.

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.