Congrats on the release! Nice to see transitions API go away, though I am not entirely convinced of the async model. It's capability is impressive, yet I do not like hiding what values are async, and throwing to await like React has never seemed a good solution.
Solid 2.0 RC: The Big
61–64 of 64 posts
Re: Solid 2.0 RC: The Big <Reveal>
#62Earlier quoted context omitted.
Why do you need several human/ai iteration rounds and dozens of reviewers for a blog post?
Because it's important. You don't want to read my raw writing. Try to read my HackMD and you see what you'd get. It's always taken me a lot of work to release my medium and dev.to articles. Grammarly working hard, and multiple human editors. It scales with how many people I think will read it. A release announcement is important. It needs to be clear and it needs to convey the most information in a very short span. Y…
Try writing the tweet announcement thread first
- meander freely and use the character limit to help you truncate
- split into one tweet per point, with one code snippet screenshot + quick explainer
- either bullets like this or 2-3 sentences each
Then your article becomes a slight expansion of the thread, where you can adjust language to make it flow better instead of starting with fluff and trying to carve it into something solid
(I think of it like mobile-first design applied to writing)
If the reason you don't like meandering or bad grammar is because you associate it with low quality/low effort writing, then the same can be said about standard LLM output. You may have gone through many iterations to land at this specific AI generated article, which stands up to your level of scrutiny over the content, but to anyone who doesn't scrutinize it just comes off like any other AI generated article.
Re: Solid 2.0 RC: The Big <Reveal>
#63As I see it, this is a whole new level of DX. One simple unified API for all fetching and reactivity problems. I'm not sure if I'm overestimating this or others underestimating or not understanding how significantly this simplifies data and state management. Congrats to Ryan and the team.
Re: Solid 2.0 RC: The Big <Reveal>
#64Earlier 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
I probably wasn’t clear with my experience. I was trying to get Claude to present my ideas, with a lot of steering and refinement, but it always seemed to be plagued by Claudisms. Even after getting rid of most, it took me rewriting all the prose to get something which people felt comfortable reading.
The published post reminded my of where I got to after several rounds of review and cleanup.