Issues with SQLite:

1. The test suite is not open source
2. External contributions are not welcomed
3. It's written in C, which is nowadays prone to easily-avoidable bugs, hard to maintain and add new features
4. SQLite does not support concurrent writes
5. Columns are weakly typed

Note the SQLite documentation hints Rust as a potential language for a rewrite under conditions listed at the end of the page.

Where Turso is good: scaling (instead of switching to PostgreSQL). Also it's simple to build an extension for it

I don't know if SASS is relevant for most projects nowadays.

A powerful demo

I also use the folder model to understand it. The way I undestood it is with some trials. I got it with position:absolute that somehow create a new stack. This stack inherits the z-index of the DOM node.

a thing you absolutely cannot do is nest one interactive control inside another

it has few examples.

Some things to consider in this reset:

• an anonymous layer is used.
• border-box for all
• reset margins and borders
• reset body margins and paddings.
• min body height is 100%
• typography: line-height 1.5; prevent text-size-adjust for mobile
• but headings, button, input and label get a smaller line-height
• prevent media content overflow with max-inline-size: 100%; display: block; block-size: auto
• fill svg with currentColor for svg without fill properties
• inherit fonts in fields
• textarea should resize only vertically
• remove fieldset borders
• text with text-wrap: pretty
• every digit has its own size (use tabular-nums for tables, time, math) with font-variant-numeric: proportional-nums
• overflow-wrap: break-word on texts and heading to avoid inline overflows
• get the numbers on the same baseline with font-variant-numeric: lining-nums;
• hanging punctuation must be set properly
• code clarity is a must, so font-variant-numeric: slashed-zero is useful.
• collapse table borders
• reset sup and sub line-height because they are messing with it in texts
• align opacity with :disabled to 0.8 for all browsers and set the cursor: not-allowed
• add an outline-offset to 0.2rem for :focus-visible

Shadcn makes the radio button overly complex, even if <input type="radio" name="beverage" value="coffee" /> with 30 lines of CSS is enough.
The library uses 3 imports (and 2 components) and 45 lines of code and ARIA.

Text rotating at the borders of an image

A Rick-roll in the source code

Rust is the best language so far to replace today's most used crypto libraries: OpenSSL, BoringSSL and libsodium.

C libraries often contain a lof of assembly code making them really fast, but potentially unsafe.
pure-Rust libraries benefit from Rust strong typing and generally offer a better API, compile for all platforms including WebAssembly.

It's important to note that pure-Rust libraries might be slightly slower than C and assembly wrappers, but still fast enough for most use cases.

• aws-lc-rs is a cryptograhy create
• libcrux is a Rust wrapper for formally verified C, Assembly and Rust code.
• ring is focused on the implementation, testing, and optimization of a core set of cryptographic operations exposed via an easy-to-use (and hard-to-misuse)
• boring is a safe wrapper around google's boringssl
• dalek-cryptography is a Github organization about pure-Rust elliptic curve cryptography, used by Signal and Diem
• graviola is promising because it's faster than other projects, but not mature enough yet.

There is also blake3

In short, RustCrypto to get pure-Rust implenentations, or aws-lc-rs for linux-servers and best perforamances with FIPS certification.

HTML and CSS only 😃

Why? Costs, operational complexity, data consistency

1. Caching with UNLOGGED table (that I've also found in other posts)
2. Pub/Sub with LISTEN/NOTIFY
3. Job Queues with SKIP LOCKED
4. Rate Limiting is also possible
5. Sessions with JSONB

PostgresSQL ist nearly 2 times slower compared to Redis, but is it worth it?

When to keep Redis?

1. extreme performance needed
2. using redis-specific data structures

Migration strategy:

1. Side by side
2. Read from Postgres
3. Write to Postgres only
4. Remove Redis

and Prisma provide for example typedSQL to have a smooth integration with Typescript.

I’m currently building an app that pulls a ton of data from an external API. If you use Rust, you know the drill: you get a UserDTO from the API, but you want a User in your domain. This usually leads to writing the same From trait implementation over and over again.

What’s in the sandbox so far? I built a macro called FromDTO. Instead of manually mapping dozens of fields, I can just do this:

Note the serde create do that for JSON and other formats

ReliCSS is a "CSS hack" detection tool designed to help developers identify and replace outdated browser-specific CSS hacks with modern, standards-compliant alternatives.

Real-time "CSS hack" detection and analysis with instant feedback
Context-aware modern CSS suggestions
Client-side processing - your code never leaves your device

Differences:

• light-dark() requires a color-scheme
• prefer-color-scheme doesn't consider the color-scheme

They are browser specific (Payment API, Passkeys, Speech recognition). It matters because the portability between browsers is then an illusion, the respect of the privacy is unreliable and they are a way to keep small competitors out

The JS Date object is not consistent: there are quirks with its constructor, the JS date is a time object, no sense of time zones beyond one and GMT, absence of daylight savings time, a need for third-party library that is a performance drain. "My problem with Date is that using it means deviating from the fundamental nature of time itself."

The Time is a location in the flow of which events occurs.
Date represents a (readable for human) time

The date object is itself mutable, so it's ok to set a day in place. It can cause unintended side-effects in codebases.

So Temporal comes in. it's a namespace object like Math. There are multiple useful functions, but another magic is in the prototype chain: equals, add, inLeapYear, monthCode.

First, there are plenty of methods and properties devoted to access, format and manipulate the details of the temporal object.
Secondly, "none of these transformations required us to manually spin up any new objects, and that the value of the object referenced by nowTemporal remains unchanged."

Using temporal reduce the boilerplate so much!
Temporal.Now.plainDateISO().add({ days: 1 })

Also Temporal have some time for experimentation.