WuxiFingerHold

You are not wrong, but not to my point.

Depends on the criteria, e.g. if dev speed has highest prio, a full blown component lib like Material UI would be superior to shadcn. CSS can obviously do things that tailwind can't, so it is more powerful.

This is very much about Claude Code and agentic coding. OP at Reddit describes their situation as a soul-sucking "pressing enter" existence. Not using any human traits. Not even communicating with other humans. That is vastly different to the hustling culture before LLMs. Company culture is orthogonal to the effect AI usage can have on mental health.

I think I get your point as omarchy represents a different kind of UI, but if it was just about getting a rock solid stable working environment, Fedora or Ubuntu with either Gnome and KDE work perfectly fine. I don't even use a third party terminal (just konsole). Keyboard driven terminal workflows works fine on KDE for me.

The problem is not the hype, the problem is that it's a vibe coded distro. AI lowers the bar substantially in terms of needed competence and diligence to create something like this. Of course bugs and issues are present in human created software as well, but now that everyone can vibe code a distro the chances of low quality software are much greater.

I think this is ingenious. As many great solutions for complex problems, it seems so simple in retrospection.

As I see it, this is a whole new level of DX. One simple unified API for all fetching and reactivity problems. I'm not sure if I'm overestimating this or others underestimating or not understanding how significantly this simplifies data and state management. Congrats to Ryan and the team.

I hate to say it, but Windows is much more productive than MacOS for the usually tasks you perform on an OS (with GUI, both have CLIs, but I'm not talking about them). I'm using both at work all day long switching between them. When reflecting why, I think it comes down to windows management and the file explorer (vs finder).

Yes, quite an oversight ... as Vue has it all: Adoption, maturity, ecosystem, features, DX and speed (with upcoming Vapor mode even on par with Svelte and Solid).

It's quite an oversight of the author did not to include Vue. Vue has it all and is as of now in terms of DX, features, ecosystem and performance (with upcoming Vue Vapor mode basically the same as Solid and Vue) the best choice.

No OP, but I've also used Angular, React, Vue, Solid and Svelte in real world projects and my default choice is Vue, because it's on par with Solid and Svelte (and with Vue Vapor those three are basically the same) but with the larger ecosystem (vuerouter, vueuse, nuxt, nuxt-ui, primevue, nuxt-content, ...). I must also say that React was by far the most unpleasant and unproductive to use.

The most infuriating thing is that people still believe that you need isomorphic rendering (Next, Sveltekit, Nuxt) to have a fast, interactive and SEO friendly apps.

It can. DX is pretty much the same for backend and CLI stuff using VS Code on Mac, Linux and Windows. I'm working daily on C# backend and CLI stuff on a Mac (those are the dev machines at my employer). DX is on par with Go and Rust (at least dotnet CLI, LSP, Debugger, I can't speak for the profiler as I've never used it). I like the Rust tooling most, but dotnet CLI is not far behind.

Language and std lib wise, C# sits in the sweet spot.