React reactive framework: - are you moving a slider? lets re-render the whole tree every frame - oh you didn't want to re-render the whole page? shoulda used hooks ;)

Modern reactive framework: - looks like your slider is only updating one value on the page, let me surgically update that for you. no sweat ;)

With the React Compiler, this isn't the case any longer.

I wish it were that simple too.. except React Compiler is yet another disappointment. Other frameworks got it right from the start, React is now following suit but not without a ton of caveats and more React rules.

How about simple proposition: I want to spend time on MY application logic not on "React code" aka hooks, resolvers, providers, etc etc etc?

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.

copilot can help with translation

"This folder contains React components. Create a new folder `components-vue`, and translate every component from React to Vue/Solid/Vanilla"

ymmv

Thou shall not Cheat Thou shall not Defraud Thou shall not Deceive Thou shall not Trick Thou shall not Swindle Thou shall not Scam Thou shall not Con Thou shall not Dupe Thou shall not Hoodwink Thou shall not Mislead Thou shall not Bamboozle Thou shall not ...

I've found myself to be depending on ChatGPT for more and more micro-tasks. I've found that once you get comfortable with the prompting workflow, you start to wish you could do it faster and with fewer keystrokes and clicks. Fumbling with text files of prepared prompts quickly gets cumbersome.

So I had a bit of a vision - I wanted to have a contact-list of assistants that I've "hired" on demand simply by writing their biography. With AI-generated profile pics.

This is a beta, right now it's a bring-your-own key model (will enable oauth as soon as OpenAI provides it), and a fraction of the whole vision, but I wanted to put this out there to see what people think, I wonder if I got the UX right, and if others find it compelling or not. Right now the 'workers' don't have memory of previous messages, to reduce token costs, each request has its own context, and gets treated as a new task. I just think sending entire chat log histories just to provide context is wasteful, without some smart filtering, or at least user-control.