54 points pier25 58 minutes ago 13 comments
ishritmadaan 48 minutes ago | parent
pier25 45 minutes ago | parent
maxloh 24 minutes ago | parent
It just feels like the right way React should be.
ale 21 minutes ago | parent
aurareturn 14 minutes ago | parent
So if a framework is made so that coding agents can use it well, why is it a negative?
I’m not going to be writing SolidJS by hand.
croes 12 minutes ago | parent
rafram 10 minutes ago | parent
_nothing 8 minutes ago | parent
Honestly, I was probably just so tired of React that it felt refreshing to develop in something so un-React-like, and it ergonomically felt better at the time than writing something similar to React via Solid, even if the latter was still holding its own in performance on paper. If you've spent years learning French then it might feel more refreshing to start learning Japanese than Italian.
It turns out Solid had a lot of it right all along. And after using Svelte for a while, something starting feeling... weird. For all its complexity, something I always appreciated about React was that I was ultimately just writing JavaScript, and with Svelte it felt like I was writing in something only made to resemble JavaScript.
I still really appreciate Svelte, but I'm wondering if this would be a good time to see if Solid will feel more "natural" to me, having worked with JavaScript all these years. Curious if anyone can confirm if that would be the case.
Now might also be a good time to tinker with it myself before the coding models are fully up to date on 2.0 and I turn to laziness (/efficiency) and have them handle the rest.