sadness2

Killing a larger animal really sucks, at least it did for me the first time and I hope never to do so again

For gamers, I expect these will be priced such that Intel will offer a better price-to-performance ratio than AMD. I've seen so many industry pundits talking about the defeat of Intel for the last 2 generations, but gamers just quietly look the frames-per-second to $ ratio and keep buying Intel and the cheaper Intel-based motherboards. I think Rocket Lake will allow this trend to continue while Intel prepares Alder Lake.

I recently watched a video where three cats waited half a day by the door, waiting for their owner's return.

This article is an Idealogue, not Journalism.

The performance is in the same ballpark for cost-performance as Intel 10th gen, and the 10th gen Intel platform will be compatible with Intel's 2021 chips, whereas if you get an AMD board now, this will be the last processor which it supports. The AMD boards are more expensive for comparable features. Intel 10th gen also has better all-core boosting, which might be important for upcoming games with better multicore support.

Fear of thousands of eventual deaths is very rational.

Thank you for this generous offering! Do you have any tips around expected costs or power/performance requirement?

I'd adopt this immediately if it could integrate with editors like vscode

I wonder whether you have some reason to think they haven't read that work, and this isn't them building on it

Yikes. You haven't reduced inter-component communication. You've basically got an interface distributed across all your components, and defined as a data schema. Any change to this can now potentially break communication between any two or more processes.

Radical! Some counter-points, though.

- Infrastructure as code and schemas as code make it easier to keep environmental parity, because everything can be rolled back/forwards/reset with easy source control and CD operations. Visual environment diffing and drift detection can make this even easier.

- Make your stage and prod into a blue-green situation, where if stage is ready to go, you flip users onto it. I can guarantee your stage and prod will both be respected as prod then. Failing that, just add load/stress tests to stage to make it more prod-like.

- Non-prod environments and attention are not necessarily debt, but they are expensive insurance premiums. You should only pay those premiums if you need the insurance. It's about risk management.

- As time passes, the people who wrote a specific part of a system don't know it anymore, so having them babysit 'their' code in production has diminishing returns. On the other hand, having a systems quality team who have a broad mandate to bugfix, put in preventative measure, reduce technical debt, improve observibility and establish good patterns for developers to do these things, can enabled these things to actually happen, when just telling devs who are busy making features that they should happen often doesn't make them happen. Also there are devs who enjoy creating new things, and others who love trouble-shooting and metrics.

Context is everything

Our kids would definitely be worse off without screens. We don't have time to give them their ideal levels and kinds stimulation, and screens are a tool which helps their parents' sanity. Us, as their parents being driven insane would adversely affect these children. One of them has special needs and the other 2 crave constant input. Overall screens are the lesser evil, and they're all doing just fine. It's all contextual and this article is nowhere near holistic enough.