Solid 2.0

13 points by bio 7 hours ago on lobsters | 12 comments

natkr | 4 hours ago

Solid 1 was pretty much my go-to example of what a web (front-end) framework should look like, so it's really sad to lose it to the slop machines too. (Even if it's been a long term coming.)

I guess at this point I'm pretty much resigned to the idea that any big new web app project would have to start with yak-shaving some form of Solid 1 clone.

…at least it's fun to go back to squeezing everything into the server-rendered box in the meantime. (And dealing with vanilla JS where it's not too bad.)

conartist6 | 4 hours ago

Same reaction.

I recently forked the Solid 1 signals library and read through all the code in it. When I took a look at the changes to signals in Solid 2, I was immediately hit with a massive heap of rotting trash comments.

It makes me sad and angry because there's probably enough good ideas there that I'll have to implement them, but if I want a long-term-maintenance-quality implementation it seems like I'll have to write it myself.

My favorite bit is that into their effects code they put a bunch of logic about "affects". Public Service Announcement: "an affect" (the noun usage) is basically "putting on airs", like pretending to have a lisp or a southern accent. Its noun form is not related to cause and effect as is the verb "to affect". The noun form of that verb is "effect".

conartist6 | 4 hours ago

It'd be kinda like if they wrote a codebase about tasks and introduced a new type of object called "tesk" that is obviously just a misspelling of "task" but which nevertheleess is used everywhere as if was really a separate conceptual entity.

nemin | 3 hours ago

So like thunks?

alloyed | 17 minutes ago

having both "effect" and "affect" as important but entirely separate concepts seems especially mean to anybody who wants to discuss their code in person, potentially with people with vowel shifted accents

did they say effect, or did they say affect....?

oneirine | 2 hours ago

My favorite bit is that into their effects code they put a bunch of logic about "affects".

I haven't looked at how they're using this term, but PureScript has an Aff type for describing async effects; maybe that's the precedent?

tentacloids | an hour ago

The docs for that use "effect" (noun) quite generously. I'd guess it's a portmanteau of async + effects.

What I see of affects in solid docs makes me think it's the cutesy declarative "fluent" verbiage popular in test frameworks. There's also ample mention of effect elsewhere.

kaspar | 2 hours ago

I thought Solid 1 signals are very much tied into Solid itself. I am excited about Solid 2 because it's a separate package there. You split out a signals lib from Solid 1?

Agree with sibling comments that affect is probably short for async effect.

conartist6 | 2 hours ago

I have a work in progress signals lib split out from Solid 1, but I'm not aiming for 1:1 compatibility.

"But, we aren't writing the code anymore!" We hear you.

People really say this?

I'm so sad. I clicked this article expecting something fun and exciting about a framework I've been hoping to use in a future project, and instead I've discovered that I'm going to have to find something else. I don't think I really enjoy being a developer anymore…

liberty | 2 hours ago

I initially thought this was Tim Berners-Lee's Solid. Disappointing that it's another Web framework, especially one that's repositioning itself to be used by LLMs.

I’m glad to see the unbearable slop prose of previous communication is now just annoyingly corrected prose. Genuinely a huge improvement.

If you're sensitive to bundle sizes (which you almost certainly aren't), a heads up: the Solid 2 bundles are much bigger. My counter component bundle test is:

 4.8 KiB (brotli'd) in Solid v1.9.18
20.3 KiB (brotli'd) in Solid v2.0.0