In fact, it's almost a direct relationship.

The biggest impact isn't in the material objects it has allowed be to buy, but in the freedom it provides to self-actualize, to pursue activities and build skills that would've been near impossible if it weren't for money.

Valve doesn't need this to do well to survive. And you don't need a steam machine (or any >$1000 machine) to play PC games. Just wait it out or buy used hardware. Hell, even an rog ally x plays just about anything (and also supports steamOS), and you can still get that at reasonable prices.

Mainly want to see the people who are building stuff I've never even thought of.

If you want a more in depth explanation, go look for interviews with devs who were already super-productive before LLMs and now came around to using them everyday.

I still write code manually to keep my trad-coding skills from withering away, but using AI without a doubt has allowed me to better test my existing apps. Create playwright automations I would've never had the time for. Allowed me to search through docs many times faster. And it just making programming more fun when I do use it for more challenging problems, and I actually get something working at the end of the day.

Please stop posting.

Every line I put in my app, I still reason about myself. But when deciding between 5+ ways of building some random, non-straightforward feature, it's nice to have what's essentially a "mentor" AI.

I want to use those as references to fix my UI (on increased font-sizes on small screens) before releasing an app I've spent 4+ months on.

Also, not having ridiculously oversized margins, like so many 2019-2022 websites trying to look "modern" used to use.

old.reddit.com is one example where the paddings still look good when magnification is set to 150-170% (which I have to do because of the tiny default font size). I think doing it that way but with better readability at 100% zoom, would be a decent solution.

10-20 seconds times a couple turns on a new feature isn't bad. Kimi is also similarly fast if not faster.

I do agree with smaller models for more constrained/routine tasks though.

Why would I build my little web-apps and backends in the cloud when I can run things faster locally?

Definitely not a developer machine based on how they presented it in google IO. So if you write software, it's not looking like it'll be relevant whatsoever. I hope to be proven wrong.

I generally prefer solidJS nowadays, but the react ecosystem has enabled lots of amazing user experiences (and developer experiences too if you don't fall into the trap of overcomplexity).

Lots of examples on x and on reddit of similarly styled apps made with the help of opus.

Gleam, lustre, and tauri? Amazing

But I 100% see where the author's coming from, considering the massive fragmentation of react codebases/patterns and decision paralysis of React development in general. I really doubt most React apps, even the more accessible ones, are testing their multi-page form wizards with JS completely turned off.

HTML-first does seem highly underutilized in the commercial web, and I learnt a lot from reading this (as a solidJS/react dev).