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.)
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".
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.
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
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.
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.
Yeah, you're not missing anything, it's all grammatically correct, I was just saying I don't think Aff is the precedent. However, "this function" is implicitly the subject (ish) of literally all statements in imperative programming, so it should just be "affect" (verb). I would hazard that that incorrect mood is part of the original issue.
You’re missing that this function doesn’t do anything itself, it’s marking x as affected. So if you fetch something imperatively, you say “this.fetch(x)” but if you are just recording the fetch you say “this.fetches(x)”. It feels correct as-is to me.
The comments here seems more intent on nitpicking correct grammar than they do discussing the technical aspects of this major release of Solid. Kinda sad what’s become of this place.
I assume “refresh” refreshes thing. Affects marks thing as affected.
If refresh was instead marking thing as refreshed, it would be “refreshes(thing)”
They’re different for a reason. I can only assume. Because that comment is unreadable slop.
ok??? I'm literally just trying to resolve a misunderstanding for everyone's benefit?
Sorry that wasn’t directed at you but rather the whole comments section, which is the result of having bad site policies for so many months. Technical discussion on this site has taken a huge hit and this thread (of which I’m inexplicably participating) is just a tiny symptom of that. That’s not on you.
"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…
Why is it lost to the slop just cause they care about making it work well with AI? Are you saying they’re also developing it with AI or is this must about the feature in the article? I don’t think it’s realistic to expect developers not to care about supporting AI coding in their tools. It just seems to me like you can still choose to write it by hand. It’s an amazing framework with amazing ergonomics, written for humans.
That being said if there’s some proof of AI slop in the solid codebase I understand your complaint but I hadn’t seen it.
Could you please link to an example of this? I'm trying to evaluate it a little myself as I'm really trying to find a way forward without losing my mind. I'm trying so hard but it's becoming increasingly unsustainable to avoid every project that uses AI and as much as I hate it (AI but particularly vibecoding) I think I'm just going to have to use my own judgement on a case by case basis as to whether it's used 'responsibly' (as much as that is possible with a technology that is so ethically challenged; but at least in the technical sense) which I guess I did before anyway.
I've had a brief surface-level look at some of the signals source code and it seems like mostly fairly reasonable inline API documentation. Did I miss anything? I might be trying a little too hard to convince myself I don't need to go back to the drawing board yet again.
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
Agreed. For some reason Ryan has had quite a strange relationship with LLMs. I used to enjoy his writing a lot but he somehow became convinced that his writing was bad. I remember him talking about this quite a lot on streams a while back (maybe about a year). He tried posting some LLM-written/edited articles which just read as total slop. I would every single day of the week rather read a grammatically bad article from someone so technically competent as Ryan than to perceive him through some LLM filter which smooths out the content, both its qualitative peaks and valleys.
Similarly I'm surprised this is the direction his development has gone too. He was hesitant and slow to AI-adoption for quite a while. I wasn't expecting a swing over to the other side due to that.
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.
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.)
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".
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.
So like thunks?
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....?
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.
I have a work in progress signals lib split out from Solid 1, but I'm not aiming for 1:1 compatibility.
I haven't looked at how they're using this term, but PureScript has an
Afftype for describing async effects; maybe that's the precedent?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.
I must be missing something because that linked doc is the correct use of the verb “affects.” The subject is implicitly “this function.”
Yeah, you're not missing anything, it's all grammatically correct, I was just saying I don't think
Affis the precedent. However, "this function" is implicitly the subject (ish) of literally all statements in imperative programming, so it should just be "affect" (verb). I would hazard that that incorrect mood is part of the original issue.You’re missing that this function doesn’t do anything itself, it’s marking x as affected. So if you fetch something imperatively, you say “this.fetch(x)” but if you are just recording the fetch you say “this.fetches(x)”. It feels correct as-is to me.
The comments here seems more intent on nitpicking correct grammar than they do discussing the technical aspects of this major release of Solid. Kinda sad what’s become of this place.
Yeah but look at the example, it's not going
subject.verbs(object)Indicative followed by imperative. It's inconsistent, that's all.
ok??? I'm literally just trying to resolve a misunderstanding for everyone's benefit?
I assume “refresh” refreshes thing. Affects marks thing as affected.
If refresh was instead marking thing as refreshed, it would be “refreshes(thing)”
They’re different for a reason. I can only assume. Because that comment is unreadable slop.
Sorry that wasn’t directed at you but rather the whole comments section, which is the result of having bad site policies for so many months. Technical discussion on this site has taken a huge hit and this thread (of which I’m inexplicably participating) is just a tiny symptom of that. That’s not on 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…
Why is it lost to the slop just cause they care about making it work well with AI? Are you saying they’re also developing it with AI or is this must about the feature in the article? I don’t think it’s realistic to expect developers not to care about supporting AI coding in their tools. It just seems to me like you can still choose to write it by hand. It’s an amazing framework with amazing ergonomics, written for humans.
That being said if there’s some proof of AI slop in the solid codebase I understand your complaint but I hadn’t seen it.
No, I'm referring to what I found when I opened the signals code to read it.
Ryan is using Cursor to write it and there is about 10 lines of low value slop comments on top of each and every method
Could you please link to an example of this? I'm trying to evaluate it a little myself as I'm really trying to find a way forward without losing my mind. I'm trying so hard but it's becoming increasingly unsustainable to avoid every project that uses AI and as much as I hate it (AI but particularly vibecoding) I think I'm just going to have to use my own judgement on a case by case basis as to whether it's used 'responsibly' (as much as that is possible with a technology that is so ethically challenged; but at least in the technical sense) which I guess I did before anyway.
I've had a brief surface-level look at some of the signals source code and it seems like mostly fairly reasonable inline API documentation. Did I miss anything? I might be trying a little too hard to convince myself I don't need to go back to the drawing board yet again.
Fair enough then, I haven’t checked it out myself but I think that’s a fair reason if that’s a deal breaker for you obviously
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:
Agreed. For some reason Ryan has had quite a strange relationship with LLMs. I used to enjoy his writing a lot but he somehow became convinced that his writing was bad. I remember him talking about this quite a lot on streams a while back (maybe about a year). He tried posting some LLM-written/edited articles which just read as total slop. I would every single day of the week rather read a grammatically bad article from someone so technically competent as Ryan than to perceive him through some LLM filter which smooths out the content, both its qualitative peaks and valleys.
Similarly I'm surprised this is the direction his development has gone too. He was hesitant and slow to AI-adoption for quite a while. I wasn't expecting a swing over to the other side due to that.
Do you know if there is there a justification for it being quadruple the size? Genuinely curious, just hoping it's deliberate.
No clue. 🤷🏽♀️
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.