Out of curiosity, I compared Solid 2 with Octane, the new JS renderer on the block.
https://gist.github.com/aleclarson/0f4266d63fd83c7a5ea551244...
Solid 2.0 RC: The Big
51–60 of 64 posts
Re: Solid 2.0 RC: The Big <Reveal>
#52Earlier quoted context omitted.
Is Claude really this bad, though? E.g. "The problem that never went away was async. Every framework, including ours, treated it as a condition that happened to it." Async treated as a condition ? And a condition happens ? And on grammar, the second it is ... the framework?? I rather suspect this is second-order output. Writings of a brain rotted by "AI". Shame, because enough of the message gets through the fog to t…
Like a cold. Sometimes people call an illness a condition. A condition that can happen to you. We have frameworks essentially living in a completely synchronous world--like a 2D plane--and they can't tell that there is another dimension out there except for when something inserts itself into its view out of nowhere. The protocol that we arrive at to deal with async is convoluted, because it is a state that is basical…
Ah. The medical meaning, for an analogy. I think 99% of readers will, like me, take the software meaning. I'm sure Claude would know that if left to its own knowledge base, so I presume it was prompted to go way outside its training, hence the wierd word salad.
Re: Solid 2.0 RC: The Big <Reveal>
#53Hey Ryan, just want to congratulate you on this. I've _loved_ solid since well before it's v1 release, and use it in all my side projects.
If anyone hasn't tried it I highly recommend it. Simply put: Solid makes the "dumb and naive code" the optimal code. It takes all the pain of React away.
I agree with your sentiment that we've pushed web frontend performance as far as we should bother. I think optimizing calls is the next frontier. On that end, I like the approach for async, but maybe I have a suggestion?
Solid needs a tightly coupled request library that emits signals/resources directly. That "server-side" data binding layer would be the missing glue. I think server actions sort of get at that, but I've never really been satisfied with them. Just my 2c.
Step one of all my projects is always wrap a bunch of fetch calls into whichever correct incantation of solid primitives. Plus, the solid compiler should be able to early load those requests via static analysis and improve real life FCP / LCP times without the developer needing to do gymnastics.
Re: Solid 2.0 RC: The Big <Reveal>
#54Earlier quoted context omitted.
> And honestly :) The AI tone in the announcement is light enough to be barely noticeable, but it’s there. Note that posting AI-generated comments to HN is explicitly forbidden.
Before: Anyone who has spoken to me knows I talk in run-on sentences. I never complete a thought without interrupting myself. And I write the way I talk. I used to heavily edit that out of my writing, but now AI uses the proper punctuation and fills in where I miss words. It's like what I hear in my head but better. Because it is grammatically sound. After: Anyone who's spoken to me knows I talk in run-on sentences.…
FWIW I also prefer the before. "whole editing passes beating that out" and "what I hear in my head, but grammatically sound" might not be immediate AI tells like 'and honestly' and 'load-bearing', but they are phrases you'd expect in a magazine article, not a forum comment. That kind of language in this context makes it smell like AI.
Re: Solid 2.0 RC: The Big <Reveal>
#55Earlier quoted context omitted.
The article reads eerily like the Claude-authored drafts I did for some internal explanations of Relay’s design philosophy (it’s a GraphQL client I’ve been advocating for). I’m not one to make accusations of AI authorship, but it was a particularly striking impression with this one. I had to rewrite the drafts very heavily in my own voice in order for people to enjoy reading them —- not that I’m a great writer, but I…
Hey want to see what AI generates when I ask it to talk about Solid 2.0. It's not that. It is: https://hackmd.io/@0u1u3zEAQAO0iYWVAStEvw/rJM9ws3Kbg https://hackmd.io/@0u1u3zEAQAO0iYWVAStEvw/H1Q8XTMSbe
[deleted]
Re: Solid 2.0 RC: The Big <Reveal>
#56Earlier quoted context omitted.
I prefer the former version. It sounds like a human.
I like my wording for `miss` better but I like the AI ending much better. This was just in a small two sentence response. I find over the course of an article the impact is much greater.
It is! But not in the direction you think!
Re: Solid 2.0 RC: The Big <Reveal>
#57This is excellent. Async being first class is definitely a paradigm shift compared to other frameworks. Vue has been trying to outdo Solid by the introduction of Vapour mode but now Solid has the upper hand once again.
(I see a lot of people complaining about AI use in writing the announcement. What they forget is, when you spend time actually writing and debugging code, these kind things that can be outsourced to LLMs should be. The important stuff is elsewhere and that's what matters. Not a blog post. Its purpose is to tell the users what to expect and the post does that well.)
Re: Solid 2.0 RC: The Big <Reveal>
#58This is excellent. Async being first class is definitely a paradigm shift compared to other frameworks. Vue has been trying to outdo Solid by the introduction of Vapour mode but now Solid has the upper hand once again. (I see a lot of people complaining about AI use in writing the announcement. What they forget is, when you spend time actually writing and debugging code, these kind things that can be outsourced to LL…
> I see a lot of people complaining about AI use in writing the announcement. What they forget is, when you spend time actually writing and debugging code, these kind things that can be outsourced to LLMs should be.
the way you do something is the way you do everything. AI slop in one place of your work makes people think there's AI slop in other places too.
Re: Solid 2.0 RC: The Big <Reveal>
#59I am a big fan of Signals. It’s the best state-management concept I've come across (also my team-mates). We even use it outside of the frontend space, e.g. in long running instances / services or complicated numpy calculations.
One of the core characteristics why it's so easy to reason about, is that the reactivity is indeed synchronous. We know most of the time, what every signal set() does when we constraint ourselves Effects not allowing to set other Signals.
Integrating async as first class citizen into the core is indeed interesting. I wonder how it impacts the ergonomics and state reasoning in the end.
Need to test it out.
Re: Solid 2.0 RC: The Big <Reveal>
#60> That's the whole data-fetching story
urgh