> The trigger was outages in cloud services with sometimes significant impacts on other internet services. Shortly before, an approximately 15-hour outage of the AWS cloud in the US meant that not only Amazon's own streaming services but also Atlassian, Docker, Epic Games, and the Signal messenger were unavailable or severely restricted.
If I remember correctly, it was a us-east-1 issue specifically. Why is everyone hosted in us-east-1, especially in Europe where stable and reliable regions are available (eu-west-1, eu-west-3, ...)?
> MariaDB (and MySQL‑family engines) avoid this entire class of problems by cleaning up row versions at transaction time. There is no background janitor. No vacuum lag. No wraparound timer. No need to tune autovacuum workers or throttle I/O to keep the system responsive.
The article seems a bit misleading. AFAIK, MariaDB (InnoDB) have to "vacuum" too. The implementation details are different between InnoDB and PostgreSQL, and maybe the InnoDB's Undo Log approach is less subject to bloat and maintenance cost, but it still exist as the InnoDB Purge Thread: https://mariadb.com/docs/server/server-usage/storage-engines...
1. Yeah, AWS and Cloudflare suffered from bad outages a few weeks/months ago. In my experience AWS has been very stable in the regions I use (us-east-2, eu-west-*), though.
I worked at companies in Paris where it’d be considered "uncommitted" as well, if done consistently. Especially in "small" companies (let’s say fewer than than 20 people). I guess it’s a matter of company culture.
It may be 1000 comments, but including answers to comments, and answers to answers to comments and so on. Since it’s possible to fold "sub threads" of answers in which I am not interested, it becomes pretty manageable.
To read more.
I know it sounds cliché, but here is the plan: instead of setting a quantitative bar (e.g., read 20 books in 2026), I have 5-6 topics I want to explore and get reasonably knowledgeable about. That’s the goal.
> Viral traffic from Hacker News, Twitter, etc. fades quickly; One-time spikes provide no long-term value; Focus on sustainable organic growth instead
I guess it depends on the audience. Our audience is tech-savvy and like RSS feeds, and it can change everything.
You need to make one big "spike", then some people will subscribe to your RSS feed, and some of them will silently follow you and read the future articles that won’t make it to the HN front page.
Looks pretty bad... Hackers on BreachForums are claiming they did that and now have criminal records (wanted persons, victims files, ...) data, and emails from +16M people. If the files contain info on key witnesses, they are now at risk.
macOS/iOS 26.1 had some minor (but annoying) UI bugs. Some of them are still here after having upgraded to 26.2, e.g., the menu displaying wrong Bluetooth device statuses (despite the device working as expected).
> This appears in the release notes as a fairly minor change but it significantly boosts the defense against one of the sneakiest problems in data management - silent data corruption.
I’ve always been puzzled about the fact there was no checksum by default. Integrity of data is a core job of a DB after all. I’m curious to know if there was a technical justification for that.