That's an Ubuntu issue though, they ship lots of outdated software. Nginx, PHP, PostgreSQL, Podman, etc, the critical software that must be updated asap, even with stable versions they all require a PPA to be properly updated.
It's works great until you need that one option from Docker Compose that is missing in Podman Compose (which is written in Python for whatever reason, yeah...).
ASRock has Zen 5 CPUs dying with stock settings from brief core voltage spikes on idle (max core frequencies). I believe either PBO has to be enabled to allow undervolting headroom or VSOC has to be permanently fixed to a value lower than 1.2V.
Are they out of their minds? How can a tiny startup without their own actual product (nowadays anyone can strap OpenAI/Anthropic API or fork open source models, such as Deepseek, on top of web scraping) buy the largest browser used by billions made by a company making trillions?
I can't imagine searching with Google these days unless it's something very niche. Even free AI with web search are marginally better, even with the traffic spam they create, Google Search has made itself unbearable.
Somewhat solved by type annotations + a good static type checker, such as pyright (it's 2025, there must be type annotations everywhere), and dynamic cases (very rare, probably due to poor or unfortunate design decisions) can be solved with validators, e.g. the aforementioned Pydantic. This isn't a silver bullet, but it works really well.
An easier/moderate approach: make a proper base DTO model, which can be extended by validators, such as Pydantic, and the db model is the Domain is just whatever an ORM offers/dataclasses.
Apart from dataclasses (which generally should have slots and/or be frozen), this article gives way too much inapplicable advice, which is not scalable even in a small sized project.
Why so? Just after the forking process Valkey has gone beyond what Redis is capable of due to high volumes of funding and new attention from devs wanting to improve Redis's performance.
Some "smart" folks even downvote this advice. Yeah, I've seen articles on musl's horrible performance back in 2017-2018, and apparently it still holds, yet I get a downvote.
It's hasn't been performant for me all the 3 times I've tried. It kept chugging an entire CPU core. Never had a similar experience with Sway, it's still extremely responsive and light on the system (especially with Vulkan).
Yes, I do agree on most of AI's side effects, but it's already cheap, accurate and reliable enough to be used with a fine-tuned context/pretrained model + tooling (web and local db search in particular) at various monotonous applications without breaking a bank. A human can intervene to guide, add extra context, or even continue working from what an AI model has come up with.
It's not about "good" or "bad", we have to live with it. And as always, those who don't adapt - vanish.
I switched to Monaspace Argon as default, it's a tiny bit more variative compared to JetBrains Mono, which enchances its readability without going full crazy.
Probably they meant that GC introduces a certain level of uncertainty, whereas OS or "systems" programming leans heavily towards manual handling (except when the compiler allows to avoid it, not the runtime).
The article is weirdly framed in favour of Biden's administration, who delayed heavy weapons by a year, and didn't fully utilize the allocated budget. Now we have a stupidly long conflict.
-march=native + mimalloc (or jemalloc) should be sufficient without causing significant undefined behavior like -O3 or most extra optimization related compiler arguments.
IO multithreading is still not fully there, there were significant improvements within the first couple of iterations, hopefully, it will improve further. I see that Dragonfly uses iouring, which is not recommended by Google due to security vulnerabilities.