ICE cars are still the majority of new cars being sold and it'll still take a while for EVs to become more popular.

That's interesting. In my country ThinkPad E14 16/512 is 37% more expensive and comes with garbage 60% srgb screen. It's actually more expensive than MacBook air M4 16/512.

It't true that the ThinkPad display kind of sucks. Though I can upgrade to a 2K OLED panel for additional 80 USD. That makes the E14 30 bucks more expensive than the Neo.

It's natural to reduce the cost of doing business.

That's true and on top of that the EU heavily taxes CO2 emissions which makes the problem even worse. If not for the EU ETS, they could just go back to burning coal for electricity which is cheap and abundant everywhere.

I agree that the lack of backlight keyboard and touch ID isn't a serious limitation but 8 GB of ram would be probably be hardly usable, especially on tahoe.

For the target audience, they’d be none the wiser. If you’re even thinking about ram it’s not for you.

But won't it be slow and provide a bad experience?

I use an Air M2 8GB, and memory becomes an issues when I have Chrome with hundreds of tabs, a docker runner, an IDE, and several other apps like keynote all open. Add Claude and the machine is suffering! My guess is that 8GB should be fine for most users, but design students for example may stumble upon issues if they use a lot of big apps concurrently.

latex error messages are basically indecipherable to me which makes it unusable for anything

especially bad for european union countries since they can't switch electricity generation to coal because it would push the ets price through the roof

With only 8 GB of RAM would this be usable even for web browsing?

It's macOS. Yes, absolutely positively more than enough for web browsing plus a whole lot more, simultaneously.

If you do serious development, you might need to think about it.

I do serious development with local applications on my 16GB M2, and my current usage about 6GB. It goes higher when I run LLMs or VMs, and of course Xcode. Aside from iOS dev, I do not use an IDE.

The article seems written soundly but I can't stop thinking that all these patterns discribed there are just a huge overengineering and are solving problems which don't really exist.

Thanks for the feedback. I got a bit surprised by the "overengineering" part. Especially that one of the reasons for writing this piece were the "enterprise" grade systems I've seen, which had so many layers they were hard to grasp at all.

Please note the "adaptability" feature mentioned several times in the text. Applying each of the techniques/patterns/tests should always be a conscious decision. The tutorial explicitly demonstrates, for instance, that not all modules got a separate "infra module", because their logic didn't justified it.