Josh Collins-Worth

Hi Mateo, nice to see the project is still alive and evolving. I personally tried it about a year ago, and I found it really good for designing simple web pages with reusable and customisable components. But the content management system was the issue for me, I was hoping there would be a way to just drop markdown files in a folder for it to generate articles or blog posts following a template like a regular SSG.
We even talked about it briefly, and I then forked the primo repo and started implementing a custom method to convert the database entries into a files / folder structure, which was going alright but the reverse operation seemed tricky to implement and I ended up going down another road, building my own custom markdown SSG inspired by this guide : https://joshcollinsworth.com/blog/build-static-sveltekit-markdown-blog
Anyway, my use case is probably not the one you are targeting, but I still think it would be a dope product if everything worked the same but instead of writing the project into a database it would be a dynamic files / folder structure that could be edited and versioned like a regular sveltekit project. Basically it would be a svelte-based SSG framework with a components library and a dedicated UI to complement the regular text editor.
Just dropping this in case someone reads it and wants to build it, keep up the good work.

TFA links to https://joshcollinsworth.com/blog/tailwind-is-smart-steering, which is about Tailwind, but makes multiple distinctions and points that could just as well apply to LLMs, e.g.:

> Builders value getting the work done as quickly and efficiently as possible. They are making something—likely something with parts beyond the frontend—and are often eager to see it through to completion. This means Builders may prize that initial execution over other long-term factors.

> Crafters are more likely to value long-term factors like ease of maintainability, legibility, and accessibility, and may not consider the project finished until those have also been accounted for.

> In my view, the more you optimize for building quickly, the more you optimize for homogeneity.

You should read this article, it was quite good, even if you do continue to use React after. It's good to understand the alternatives, even if you never use them.

https://joshcollinsworth.com/blog/self-fulfilling-prophecy-of-react

It's been a few months since I read it, but I recall the main thing I took away from this was: React isn't necessarily the best choice, other frameworks provide better performance, development experience and tooling that should also be considered

Of course these are just opinions. Everyone should consider all the facts and come to their own conclusions about what they use and don't use.

Companies will continue to use React of course. But I'm not sure if I would use vanilla React for anything I have complete control of.