• by ttymck on 4/21/2022, 12:16:28 PM

    I use alpine, but I see it as a "callback manager". It updates html when I update a JS variable. All the Javascript within my alpine "components" is vanilla. So far the clunkiest thing I've had to do was routing (query param syncing; inter-page routing is still delegated to the browser).

  • by coolhoody on 4/21/2022, 2:22:55 AM

    I default to Vanilla, would agree to Svelte under pressure. But most start with React. The logic likely being — at least I'll find a job if this fails. Can't blame, makes sense.

    There are some exceptions — e.g. Pieter Levels (RemoteOk, NomadList) who sticks to Vanilla for everything. But it's rather rare.

  • by teekay on 4/21/2022, 6:39:45 AM

    We default to server-side rendering, plain HTML+CSS and vanilla JS when needed for most of the business apps we make. Why over-complicate the stack and increase maintenance costs when 90% of it all is a plain old CRUD? I do see a use case for React / SPAs, just not in what we typically do.

  • by schwartzworld on 4/21/2022, 10:46:48 AM

    I don't use react on side projects because I use it at work all day and I like focusing on new problems. When it's just me, and the project is a few hundred lines of code, that's fine. I'd probably still use it for anything I wanted collaboration on though.

  • by tomcam on 4/21/2022, 2:40:54 AM

    Yes, I’m using it and have for the past couple years. Admittedly I have created a CSS framework, because I have strict backwards compatibility requirements