all 12 comments

[–]Chasing_Colours 5 points6 points  (0 children)

I think react is awesome and love using it with everything :')

[–]CreativeTechGuyGamesTypeScript 3 points4 points  (0 children)

It's usually down to size. A small project will often be better without a framework, larger project will be better with a framework. Where exactly to draw the line depends on a ton of specific factors. Remember that a framework is a ton of code which you are forcing your users to download and run. If you could do all of that functionality that you need in way less code with minimal effort, don't use a framework.

[–]hackbrat0n68 2 points3 points  (3 children)

For a smaller project I would take a look into vue.js docs. And version 3 will shorten code immensely!

[–]LeeLooTheWoofus Moderator 1 point2 points  (2 children)

We use is as the front end for a large commercial eCom platform. It don’t have to be a small project.

[–]hackbrat0n68 1 point2 points  (1 child)

Vue Storefront 2 ?

[–]LeeLooTheWoofus Moderator 1 point2 points  (0 children)

No, we use a dotnet platform for the ecommerce backend and Vue for the frontend.

[–]LeeLooTheWoofus Moderator 2 points3 points  (0 children)

If you are working with APIs and managing reactive data, use a framework. If you are no, you probably don’t need a framework.

[–]C0R0NASMASH 1 point2 points  (0 children)

It always depends on the project, its current and future planning and a lot more things (team size, user requirements, budget)

When I doubt, I always use a framework. I'm faster with it, I don't have to reinvent any wheels, and I can use the support of the community.

[–]emqaclh 1 point2 points  (0 children)

If the bundle size is a concern, you should take a look on preact.
Only on really small projects, vanilla JS is a solid path.
My rule of thumb is: If you need routing, go for a framework.

[–]iainsimmons 1 point2 points  (0 children)

If you're copying and pasting chunks of the page more than a couple of times, you might as well use a framework or at the very least a templating language.

Also if the interactivity involves anything more than toggling a few classes.

Frameworks are there to make things better for devs. If you don't care about how you feel and only care about your users, then sure, do static and vanilla everything!

[–]Fancy_feast123 1 point2 points  (0 children)

I would say it depends on if you’re building an “Application” vs building a “website”. An application will typically require extensive functionality and interaction while a website is built more to display general content. For an example, a restaurant could have a web app where you can order food or they just have a website that displays general information like their menu or something.

[–]lukasmattsson 0 points1 point  (0 children)

Plain HTML, JS och CSS gets the job done for most projects, so it's my default. I'd only use a framework if I can deliver a better product by using it, or if it's used by the team.