The SPA Dilemma

#1

Post by todotask » Mon, Oct 31, 2022, 2:50 PM UTC

Before we enter 2023. We have React, Vue, Angular, Svelte, Solid.js and so on.

What will you choose for your productions and side projects?

Re: The SPA Dilemma

#2

Post by zach_garwood » Mon, Oct 31, 2022, 3:27 PM UTC

I'm going to try an end run around the dilemma and try htmx: https://htmx.org/

Re: The SPA Dilemma

#3

Post by patatino » Mon, Oct 31, 2022, 3:48 PM UTC

I use react, because that's what I'm best at, and I also use it in my day job. Also most jobs in react, so it makes sense for my cv too.

Re: The SPA Dilemma

#4

Post by matthewwolfe » Mon, Oct 31, 2022, 4:02 PM UTC

I use React at work for all our projects. We have yet to run into a situation where react has failed us. I’m sure many people can say the same about the other options. That is a clear indication that it doesn’t really matter which you pick. It should be based on team familiarity and then just comes down to personal preference.

Personally I think React/Vue/angular are the safe bets, in that order due to popularity

Re: The SPA Dilemma

#5

Post by andrei_says_ » Mon, Oct 31, 2022, 4:03 PM UTC

Rails, Turbo, and StimulusJS. SPA experience with 10% of the complexity and effort of using a FE framework.

Re: The SPA Dilemma

#6

Post by Raed667 » Mon, Oct 31, 2022, 4:04 PM UTC

Use the right tool for the right project:

- info-dump / static website: sever-side render everything, add JavaScript when needed

- app for specialized users: SPA probably (they're ok waiting for js to load if they're making money using the app)

- store-front / marketplace: A full stack framework like Next/Remix etc

Re: The SPA Dilemma

#7

Post by xenon_ind » Mon, Oct 31, 2022, 4:05 PM UTC

I started last year , use angular at job and for side project

Re: The SPA Dilemma

#8

Post by _448 » Mon, Oct 31, 2022, 4:30 PM UTC

I am an outlier here but I will say Wt, a C++ web toolkit. It is like developing a desktop application, server-side rendered, works even if JavaScript is disabled on client side, and includes lots of features. The final web app too feels like a desktop app even though it is not an SPA. Some of the things it can do is shown here: https://www.webtoolkit.eu/widgets

The whole https://www.webtoolkit.eu website is written in Wt.

Re: The SPA Dilemma

#9

Post by dinkleberg » Mon, Oct 31, 2022, 4:33 PM UTC

I’m going to continue to use react for pretty much everything. The beauty is you can use a consistent approach for building pages, along with a massive community. But unlike the React of 2016, you have many options for how to serve it. Single page app? Server rendered? Statically generated? Some combination? You can even build mobile and desktop apps with it (w/ react native).

There are many challenges with react. But once you become accustomed to it and it is your default way of working, it just makes sense to keep using it. It keeps getting improved and the ecosystem keeps evolving.

Re: The SPA Dilemma

#10

Post by alnico » Mon, Oct 31, 2022, 4:40 PM UTC

I use something that many people don't know about or aren't talking/posting about: JsRender/JsViews. https://www.jsviews.com

JsRender can be used client-side and server-side using Nodejs for rendering templates. JsViews adds observability (one-way or two-way) to JsRender on the frontend and requires jQuery (I like jQuery, it's overhead is minor ;-).

JsViews is intuitive, modular and extremely flexible and self-documenting in my opinion. JsViews does not include a router as there are so many different ways of doing routing and depends on your needs. The concept and syntax of converters is really cool too.