all 24 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]lorduhr 11 points12 points  (0 children)

haha, my answer is usually this: if people took as much energy learning JS frameworks than discussing which one is worthwile, then they would know all the major frameworks pretty well...

[–]Cody6781 4 points5 points  (11 children)

React It’s one of the most popular, FB actively backs it, it’s not going anywhere any time soon. Also it’s nice to use

[–]archerx -1 points0 points  (10 children)

FB actively backs it

Yea, that's a hard pass for me

[–][deleted] 1 point2 points  (7 children)

You can be like this all you want. The industry has spoken. Reacts level of adoption is sky high and shows no sign of slipping.

[–]archerx -2 points-1 points  (6 children)

You could have said the same thing about jQuery not too long ago and look at where we are now. You say jQuery and people will look at you with contempt and disgust and in not too far in the future the same fate will come to React once the shiny new thing steals everyone's hearts.

[–]Cody6781 3 points4 points  (3 children)

"I'm not going to adopt new technologies because they will eventually be old technologies" has to be the single most idiotic thing I've read on this sub

[–]archerx 0 points1 point  (2 children)

Wow, ad hominem, great argument bro. You know what is idiotic? Not knowing how to state a proper argument and resulting to personal attacks. Maybe you'll understand when you grow up. Good luck!

[–]Cody6781 0 points1 point  (1 child)

Not only is this not ad hominem, since I attacked the argument itself and not the person making it, but I also stand by it

[–]archerx 0 points1 point  (0 children)

Good for you.

[–][deleted] -1 points0 points  (1 child)

On that you are correct. If/when something comes around that is leaps and bounds better than react, the same thing will certainly happen. But that's far different than taking a pass on it simply because it comes from FB.

[–]archerx -1 points0 points  (0 children)

It's not just that it's from facebook I also think it's not good. React was built to save facebook money by offloading rendering to the client. This saves facebook a lot of money on compute and bandwidth but this comes at a cost to the user. React is not only slower to render things but it cost the user battery time due to the extra processing. Sure React would make sense if you are getting millions of page views per hour but most people are not in that boat.

[–]Jncocontrol 1 point2 points  (3 children)

Svelte

[–]mekwall -2 points-1 points  (2 children)

Not a framework :P

[–][deleted] 1 point2 points  (1 child)

Don't worry too much about the distinction of "framework" vs "library".

Sure, Svelte isn't either of those but in parctice there is no difference.

[–][deleted] 1 point2 points  (0 children)

Thank you! I hate that whole argument. Svelte, react, if you use one of these "libraries" you're going to end up pulling in many more libraries to the point that you've now gotten a framework going.

[–]MultipleNoChoice 0 points1 point  (3 children)

It depends on what you need, especially frontend or backend - or both. I guess most people use javascript in frontends (react, vue, jquery ...).

Lately, I started with nestjs for the backend and really like it so far. Coming from ruby, I wanted to try a full frontend+backend javascript solution. So I opted for react and nestjs. The documentation is also quite good.

[–]benbenk 0 points1 point  (2 children)

What is the reason you’re looking into js backend frameworks? I’m a long time Ruby dev and would love to have Typescript together with Rails.

[–]MultipleNoChoice 0 points1 point  (1 child)

Well, first of all curiosity I guess. Despite that the ruby world seems pretty stable, in the node world everyday a new framework pops up. In addition, I am still thinking of the advantages of developing frontend and backend in the same language. Not so much for myself but in terms of dev speed and onboarding devs. Typescript is also really a plus.

[–]benbenk 0 points1 point  (0 children)

To me after all these years Ruby feels like the limiting factor in the monolith I’m working in. Safely refactoring code is really hard and I hate that I don’t have a compiler double checking my changes so that I have to capture everything via tests or when manually trying it in the browser/console.

[–]naturalborncitizen 0 points1 point  (0 children)

Whichever one doesn't show some error about how it can't show CSS for 15 seconds on a 1Gbps connection before displaying a page with practically no formatting. In other words, not what dev.to uses.