I see where this sort of take comes from. Reviews are not a place for subjective comments that just slow down or block progress, signaling, excessive nitpicking, etc. However, the reviewer should be thinking beyond the immediate "hey, this is progress", and also consider how this change affects the codebase and how it aligns with feature and technical direction. A few happy approvals and a great codebase becomes hard to work with, if contributors are inexperienced.
Code reviews are also an opportunity for learning, and provide real-life scenarios to inform decisions that are otherwise not grounded and mostly opinion. Of course, not all comments and discussions should block approval, but there is a balance. No one is going to die if this feature is delayed by a few days if you get a better result _and_ are investing in team growth.
In my experience and my family's you are lucky if they last 3 years. If they last 5 years there's usually a subpar experience, e.g. they overheat significantly at 2 years. OTOH, we have a few macbooks > 10 years still working.
There's the need to dust fans and then there's the possibility that OS computing requirements have risen which isn't often a Linux thing on old hardware.. OsX had exactly the same problem and had to make a minimizing release IIRC.
Computing kind of stagnated since 2010 and plenty of hardware since then still works fine today and is usable enough for many tasks. Apple was nice for needing not all that many different drivers but its statnge integrations like drive fans to bios are obnoxious.
I've owned old macbooks… I got scalded by the metal screws on the bottom in the summer because apple thought looking sleek was more important than proper cooling.
The other laptops overheat soon after purchasing, often with just the bare OS running. There is a 3 yo laptop that my parents still use, but it has to always be plugged in, and the fans will spin loudly even in suspension.
My >10 yo macbooks also have bad batteries. One of them won't last one minute, and will also overheat with minor workloads. They were not immune to overheating when new, but unreasonable overhearing (for the time) definitely didn't become an issue at within 3 years of purchase.
And that's with Intel macbooks. My M1 from Dec 2020 works like new (I'm sure the battery life has shortened, but not in a way that I notice). It overheated a couple times running LLMs—that's it. That's how I know the fans work.
I like Ecto's approach in Elixir. Bring SQL to the language to handle security, and then build opt-in solutions to real problems in app-land like schema structs and changesets. Underneath, everything is simple (e.g. queries are structs, remain composable), and at the driver layer it taks full advantage of the BEAM.
It's hard to find similarly mature and complete solutions. In the JS/TS world, I like where Drizzle is going, but there is an unavoidable baseline complexity level from the runtime and the type system (not to criticize type systems, but TS was not initially built with this level of sophistication in mind, and it shows in complexity, even if it is capable).
Ecto is a gold-standard ORM, in no small part because it doesn't eat your database, nor your codebase. It lives right at the intersection, and does it's job well.
And they're really good. I'm so glad I've discovered this paradigm.
I use a vertical task bar on KDE and a vertical task bar on Windows at work. It's such a huge productivity boost. First, I can see WAY more window previews at one time than before. And second, I can use text to tell the windows apart. 5 Excel workbooks open? No problem, they each have a name. No more clicking on one icon and then squinting at window previews to see which one you need.
