The 'vibe coding as fast fashion' analogy is interesting, and the article makes some valid points about code quality, maintenance burden, and the 'don't build it' philosophy. As an OSS maintainer, the 'who's going to maintain it?' question hits home.
However, I find the analogy a bit off the mark. LLMs are, fundamentally, tools. Their effectiveness and the quality of output depend on the user's expertise and domain knowledge. For prototyping, exploring ideas, or debugging (as the author's Docker Compose example illustrates), they can be incredibly powerful (not to mention time-savers).
The risk of producing bloated, unmaintainable code isn't new. LLMs might accelerate the production of it, but the ultimate responsibility for the quality and maintainability still rests with the person pressing the proverbial "ship" button. A skilled developer can use LLMs to quickly iterate on well-defined problems or discard flawed approaches early.
I do agree that we need clearer definitions of 'good quality' and 'maintainable' code, regardless of AI's role. The 'YMMV' factor is key here: it feels like the tool amplifies the user's capabilities, for better or worse.
EU's reluctance towards AC, often bordering on what feels like superstition (e.g., "thermal shock" fears), is increasingly at odds with reality. Living in Europe (outside the EU), where summers regularly hit 43°C, I can't imagine functioning without it.
With the growing number of annual heat-related deaths in the EU, this is not just a matter of comfort, but a matter of survival.
As a PC gamer, I'd definitely be interested in something like this!
I currently use a Legion Go with Bazzite installed, paired with a cheap AliExpress dock and an eGPU dock (also from AliExpress) housing a Radeon 7600 XT. Overall, it's been a great experience. With some minor tweaking, I can play pretty much everything you're describing – PC games via Proton, retro games, and PlayStation titles through emulators.
Given that my entire setup cost around $1200 (Legion Go, dock, eGPU enclosure, and Radeon 7600 XT), I would absolutely go for a pre-built system like yours if I didn't already have my current setup. It truly offers the appeal of a Nintendo Switch but with significantly more horsepower and flexibility (and none of the console vendor lock-in).
Based on my experience and what I've spent, I'd fall squarely into category C. $1000 - $2500 for such a setup. The convenience of having everything pre-configured and optimized for gaming right out of the box is a huge selling point.
It sounds like you've put a tremendous amount of effort into this, and the idea of a "best of many worlds" gaming OS with minimal setup is highly appealing to gamers. Good luck with your project!
This resonates strongly. The Pixel 7 is my current holdout due to its 'acceptable' size, even though it's not exactly "mini".
It's a shame to see manufacturers like Asus move away from compact form factors, as I'd have been an immediate buyer for a smaller ZenFone.
The market's push towards larger devices is making e-ink 'dumb' phones increasingly appealing for me.
It's an old article, and things have changed quite a bit in the pricing and features landscape when it comes to auth. I'm working at SuperTokens, so here are some thoughts and updates from my angle:
- `create-supertokens-app` is primarily a learning tool to help you understand how SuperTokens works and how to best integrate it with your app. The reasoning behind this is fairly simple - apps usually don't start with auth as a first concern. It's added at some point, and in my opinion, having an example handy (especially in your stack or close to it) is one of the easiest methods to help you understand how to integrate SuperTokens in your app. The CLI tool isn't meant as a scaffold but can work as one. Although, I wonder - would a more barebones setup work as a scaffold better? It might be worth exploring.
- I'm not sure where the bundle size number (430kb) comes from, but our current version is nowhere near that.
- I agree that the NextJS example could be better. It's mostly just boilerplate, though, and it can be made to look better.
- I don't see why the 5 cookies are an issue, to be honest. Correct me if I'm wrong on this one, but I fail to understand how the number of cookies has security implications.
- I find myself disagreeing with most of the conclusion - SuperTokens isn't too different from how the classic SSR frameworks integrate auth - you still have to do all of that configuration just once.
Plus, riding the hype wave.