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.
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).
That’s an entirely subjective thing, though. I’ve used Macs more than PCs and I can’t stand what feels to me like Windows’s abysmal window management.
I don’t say that to argue that macOS is better at it, just that I strongly prefer the Mac way as much as you prefer the way Windows does things, and that’s perfectly fine.
I’ve used both interchangeably for decades and can swap between them without slowing.
So much of this comes down to knowledge of and experiences with the quick/er ways for getting around.
For quite sometime using search tools is vastly more efficient for navigation and file movement than Explorer or Finder anyway.
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.
I keep reading unpleasant without any arguments. React is simple by nature, what made it unpleasant and unproductive?
Granted I mostly do work on Shopify apps, so most of the heavy work has been done for me, I just put components together. This works fine, and I'd rather do this in React than e.g. Angular due to the small scale of the apps. Then again web components would've also been fine.
Perhaps "simple by nature" is not at the top of everyone's mind.
Simple is great until you build something complex, or need to create a large reactive UI that is not a simple CRUD fetcher. Things like non-linear video editors, 3d editors, games, things with a large component tree that takes work to plan, build, and non-trivial to re-arrange thereafter.
Your "simple by nature" framework with one-way binding and render-the-whole-tree-when-something-changes now means you spend more time coding (fighting) React than you do your application logic. You could have focused on improving algorithms, but nah you're stuck architecting hooks, context providers, state management, and adding libraries that cement you deep into the React hole.
I think React developers all secretly want to use Solid but they're stuck using React at work, and just chant React is the best React is the best React is the best
Yeah, it's one of my bugbears that a framework like React is built to solve a niche problem (running an enormously big and complex app like Facebook for an audience where timing is critical), and then gets doled out for everyone, even though most web apps have much lower requirements.
Not ultra experienced with react, but I have shot myself in the foot just because the way react is made compared to other frameworks:
- infinite loop due to re-rendering on the render function (it happens every single time i come back to react)
- using useEffect when not required
- nested object updates (dunno if this is still an issue)
- class vs whatever the name is (className?)
Overall as another comment said I feel more fighting against react pitfalls than focusing on my application's logic. That really takes a toll in productivity as part of your brain loses a small portion of 'RAM'/cognitive load as you need to make an active effort to not shoot yourself in the foot. I guess most people get used to it, but for me it just never clicks knowing there are similarly performant frameworks with way more friendly APIs.
> React is simple by nature, what made it unpleasant and unproductive?
It isn't "simply by nature" at all. I have lost so much time battling through the minutiae of the different use...() hooks, trying to figure out either why something never updates, or updates too often, or updates but the state is stale etc etc. I never run into issues like this at all with Vue. Things update simply and predictably for me.
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.
reply