Différent ways to handle errors in Rust.

In favor of the clap crate that allows delevopers to build quickly in Rust.

Structurally speaking, then, a paragraph is a group of related inline elements. In this case, inline words, but it could also include any of the items described as “phrasing content"

<hgroup> issu the tag to use for heading with multiple inline content.

Ok but why o_O

Still interesting, but I already have few use cases for container queries. Maybe because I am too dependent of design that uses screen sizes.

There are 3 error or exception handling: unchecked exceptions (JS), Checked Exceptions (Go) or an integrated type (Result in Rust) that handle one case or the other.

Explicit is always better.
One thing with an integrated type, is the normal case and the other case. That's a great type to handle more than errors: a lookup of a key in a map, opening a file with a name for which there is no file is normal business. Maybe I will find more.

And for quality software, its function must be so blatantly obvious that everybody thinks: wow, this is trivial code, even a monkey could've programmed this.

All I see so far is this will need more computation or battery drain for this.

The library is available at https://github.com/Specy/liquid-glass

• Call Stack
• Primitive Types
• Value Types and Reference Types
• Explicit, Nominal, Structuring and Duck Typing },
• == vs === vs typeof
• Function Scope, Block Scope and Lexical Scope
• Expression vs Statement
• IIFE, Modules and Namespaces
• Message Queue and Event Loop
• setTimeout, setInterval and requestAnimationFrame
• JavaScript Engines
• Bitwise Operators, Type Arrays and Array Buffers
• DOM and Layout Trees
• Factories and Classes
• this, call, apply and bind
• new, Constructor, instanceof and Instances
• Prototype Inheritance and Prototype Chain
• Object.create and Object.assign
• map, reduce, filter
• Pure Functions, Side Effects, State Mutation and Event Propagation
• Closures
• High Order Functions
• Recursion
• Collections and Generators
• Promises
• async/await
• Data Structures
• Expensive Operation and Big O Notation
• Algorithms
• Inheritance, Polymorphism and Code Reuse
• Design Patterns
• Partial Applications, Currying, Compose and Pipe
• Clean Code

A demo of a vue component built with Liquid Glass Design (iOS 26)

It does not work on my Raspberry Pi yet.
I get a:

atuin: /lib/arm-linux-gnueabihf/libc.so.6: version `GLIBC_2.39' not found (required by atuin)

1. rustup target add armv7-unknown-linux-gnueabihf
2. sudo apt-get install gcc-arm-linux-gnueabihf libgcc-13-dev-armhf-cross
3. In ~/.cargo/config.toml:

   [target.armv7-unknown-linux-gnueabihf]
   linker = "arm-linux-gnueabihf-gcc"

4. cargo install --target=armv7-unknown-linux-gnueabihf --target-dir=$(pwd) --root=$(pwd) BINARY
5. Upload the binray to the raspberry pi, i.e. /usr/local/bin

After a first successful installation, only 4. and 5. are of course required.

A valid minimal HTML page

1. avoid uneccessary default features
2. use specialized lighter crates

The migration schematics automate code changes between angular versions

I have the same idea for a node js backend serving a fancy UI :)

It would be better to split the UI and the server while developing to benefit from hot reloading.

Example: https://git.sr.ht/~pyrossh/rust-embed/tree/master/item/examples/axum-spa/main.rs

• relying on shared mutation
• treat the compiler as something trying to help
• ignoring proper module organization

You have to unlearn a few habits.

1. Writing Rust code like other languages
2. Neglecting the most important 20% of Rust. Trying to learn everything at once: you don't need to learn all at once. Focus on the 20% that gives the 80%.
3. Being a productive procrastinator: watch a video or read a blog post.
4. Thinking you can vibe code Rust like JS...

Hands on practice! The programmer has to internalize the concepts of Rust. Getting a grasp is not enough.

A points on many HTML tags (aside, mark, section, hgroup, video, progress, base): how to use them. Many good tips or rules to follow.
The CSS @import rule, [attr$=value] is a CSS selector for suffix values, box shadows with inset, cursor: zoom-in

Translated pages with <link rel="alternate"> and hreflang

Some usages such as HTML in script to reuse them as <template />, gpt or instappaper_ignore class names

The web is big and messy and bloated, and there are lots of reasons to be pessimistic about the state of modern web development – but there are also lots of people doing cool and interesting stuff with it.