Because it is possible, someone mare a page with every HTML tags in it.

How an array was built before Ecmascript v1

Another one :D

Compilers are pipelines with a serie of step. Each step transform the input and provides data to the next.

Each step has then a contract with the input provided and its output 😃

The author goes in depth.

We can completely segment one component of the compiler from another by having the right form of data structure in between them. To build that data structure, you don’t need to know anything that happens to it afterwards, you just need to know what it means.

Writing about Rust, Elixir and programming stuff

you reminded me in this episode of the day that someone published a crate named "nul" which made it so no one on Windows could use any crates

"error: [20/-1] Cannot checkout to invalid path '3/n/nul'" LOL

To solve XDG misconfiguration, if wanted.

That would be awesome indeed: using @scope (.classname) to specify styles that only applies from this class.

Ok un générateur d'idées, cela arrive...

What would you do if you weren’t afraid?

When I asked myself that question I realized I should be working for myself, building things that help people, consulting with people to help them, and putting that content into the world somehow.

Daniel Miessler runs Unsupervised Learning, so he's building the platform. He's doing some consulting and advising related to customers for a service company. He also has the podcast and newsletter :)

The result from all of this is that the promise of going to school, getting a stable job at a company, and having some sort of future from that is—or at least feels—more tenuous than ever.

I believe that the time for being identified by—and tied to—corporate jobs is passing, and it’s time to transition to what comes next

Think about work like a relationship. It’s hard to be a good partner if you’re not first healthy and independent on your own.

Courses that somehow seems relevant to every web developer. There is a 10-day trial.

So the question is, when you have done everything "right" in your attempt to do the right thing and it still doesn't work, at what point do you give up and when do you push on and try to make it right?

What to do?

1. Do nothing (and it degrades user experience for years until a fix is made)
2. Suggest an alternative (and it takes years to fix to go through the roadmap)
3. Work around it
4. Engineer a solution

Use accessibility APIs of OSes that contains building blocks. These building blocks have 3 kinds of information about a UI element.

The first is a role: What kind of element is this?
The second is a name: a label or an identifier for this element.
The third is state and other properties: Other functional aspects of an element that would be relevant for a user or an assistive technology to be aware of. Is a checkbox checked or unchecked, etc...

It looks like ARIA, oh wait!

The web browsers now expose this accessibility tree.

htmx does not have a build step and delivers the source file as a single 3500 LOC file. Alexander Petrois justifies this choice, as it is a tradeoff.

A Jupyter notebook demo style for JS.

blog-cells can turn any web page into an interactive code notebook, similar to Jupyter notebooks, but powered by JavaScript and running entirely in the browser.

There's no server-side component, so you can share your notebooks on static site hosts like GitHub pages. Check out the source for this page here.

Check it out https://github.com/rameshvarun/blog-cells

Advantages of apps over websites:

• Gobbling data: an app does not get its request blocked as a website does.
• Making money: This one applies more to indie developers than to big companies but I'm sure people are more willing to pay for an app than access to a website.
• people want app: Think about that for a second: people want to download an app to track deliveries of their white goods, something which most people order at most once a year.