Can’t these changes be still done? Maybe within 5-10 yrs these “mistakes” will deprecate eventually.

If the variable was defined in the calling function itself, and a pointer was passed, I guess the variable will still be in the heap?

Pointers escape to the heap by default.

Can you also consider adapting Linux from scratch as a part of this series? Or Maybe after this series, you can expand what is learnt to build a minimal Linux distribution. I suppose that might give a good understanding on how to apply this knowledge and a have a foundation on the internals of the os itself.

I want to keep this series focused, but LFS-style content is definitely something I'm considering for later, I think it's a good idea.

That said, this series will also give you practical, applicable knowledge as we progress.

The other day, another os - tiny core Linux - was posted. Today this, I really wonder what is the trade off? Day to day use, security, and something else surely will be missing?

How is uniqueness of devices even calculated?

I am curious - there are many x11 only apps, will they stop working OOTB?

No, XWayland isn't going away. Just X.org for running them.

> Just X.org for running them

What does that mean?

X11 applications will still "work" on Plasma Wayland session by utilizing XWayland, a tool that (afaik) runs a compact X11 session for each application.

What is being removed is running an X11-native Plasma session, only Wayland Plasma sessions will be available starting with Plasma 6.8.

You don’t need an extension to do this. Simply add a “before:” search filter to your search query, eg - https://www.google.com/search?q=Happiness+before%3A2022

I hope you will continue maintaining a mirror in GH. Some tools like deepwiki are excellent resources to learn about a codebase when their is not much documentation going around. But these tools only support pulling from GH.

I have the exact opposite experience where I had to block multiple such "excellent resources" from my search results.

How is pulling dependent on github?

Git pulling isn't unique to github and it works over http or ssh?

A neat thing about GitHub is that every file on it can be accessed from URLs like https://raw.githubusercontent.com/simonw/llm-prices/refs/hea... which are served through a CDN with open CORS headers - which means any JavaScript application running anywhere can access them.

Demo: https://tools.simonwillison.net/cors-fetch?url=https%3A%2F%2...

That feature seems common to other git hosts / forges. For example, here's one of Dillo's files, from a few commits ago, from their cgit-based host

https://git.dillo-browser.org/dillo/plain/src/ui.cc?id=29a46...

That doesn't have open CORS headers: https://tools.simonwillison.net/cors-fetch?url=https%3A%2F%2...

It's also not being served via a caching CDN, which means I don't feel comfortable running anything automated against it as that might add load to the server that they aren't ready for.

It's less about pulling and more about tools like DeepWiki making the assumption that its inputs live in GitHub, so repository URLs are expected to be GH URLs as opposed to a URL to a git repository anywhere.

That being said, there's no reason for tools like it to have those constraints other than pushing users into an ecosystem they prefer (i.e. GitHub instead of other forges).

Firefox already provides this feature in about:config using resist fingerprint - https://support.mozilla.org/en-US/kb/resist-fingerprinting

The value of the biomarkers are they applicable for all age range? What if someone already had a heart attack, then what should be the normal values post incident?

AFAIU, for LDL and ApoB, the real danger lies in the area under the curve. Lifetime exposure. That's not to say that lifestyle improvement can't help in other ways, but the damage caused by LDL is very difficult (impossible) to reverse.

So, if you hit the point where you already had a heart attack, you really want to prevent any further damage, but the "accumulated" risk is still there.

I think that's part of what makes LDL so tragic. You should care about it your whole life, but when you are young, you just don't.

Worse, high LDL is becoming a thing in children as well, that's an extra decade of accumulation which has historically not happened.

I don't think people should panic about these things, but I think it highlights the importance of developing good habits early, and the role parents and society has in making those habits easy for young people to adopt.