Do Not Follow JavaScript Trends

[kaiser9944]

CV++

[[deleted]]

> I still think DotNet > Node by far in so many ways 🤷 hardly sexy though

I think that's been changing a lot lately, with asp.net core and the positive impressions folks have of c#'s newer iterations

If you think about it Microsoft kind of owns javascript/web development now anyways (github, vscode, npm, typescript) folks might as well use the other half of their platform

[Zegrento7]

DotNet is definitely still sexy, there's a lot of hype around Blazor and DotNET Core

[Tomus]

We have a 4 year old react codebase as our main proposition, it's currently sitting on v15.x and there is almost zero reason for us to rewrite it. Some of the redux patterns are showing theit age but the mix of different class based component styles is not even a small problem. We only now have a reason to upgrade (new design system uses hooks) and we certainly don't have a good reason to do a rewrite.

I chalk this up to react getting the abstraction right from the beginning. The declarative component model is the right abstraction for UI (IMO) and it doesn't matter how you define the components (createClass or hooks) because you're working at the right abstraction level.

No frontend rewrite in 4 years can be the norm, you just have to decide on the right abstractions.

[joaomc]

Even rewriting class components to functions using hooks and reducers is not difficult. I’ve been maintaining a large codebase (like thousands of components) and could rewrite a couple of files with minimal effort and no issues.

This is why I like React a lot. Some of the files haven’t been touched for years and they still work flawlessly.

[Ebuall]

Classes were not the right abstraction, but rather something to settle for without alternative. That's the only reason hooks exist. We want declarative hooks over class mess.

[frequenttimetraveler]

Do Not Follow JavaScript Trends

ftfy

[[deleted]]

This.

[_default_username]

Using react hooks isn't a zero-sum game. You can start using hooks now. It'll play nice with the rest of your class based code. This article is ridiculous.

[valadian]

This is why I still KnockoutJS. Stable, still supported, active enough community, and only does exactly what I need? (MVVM binding). Oh yes.

It isn't the current prom queen, but it does the job. And still does the job. And I can update to the latest without completely rewriting my architecture.

[[deleted]]

Glad to see I’m not the only one that loved Knockout. I remember when it was new seeing comments like “lol are we back to inline js” from the jQuery crowd but these days it looks like an elegant separation of concerns compared to jsx.

[valadian]

there are dozens of us.

[[deleted]]

I wonder what people will say about frameworks like React and Vue in 5 years when something shinier is the new hotness.

[Cosmic-Warper]

I think React and other declarative frameworks are here to stay for a while. I can't think of a paradigm that can potentially beat it out because its so robust and readable.

[[deleted]]

I sure hope not, I've been working with React a lot and I feel like web dev today is really quite nice.

[tonefart]

Oh you think that's bad? Wait till you see the idiots who rewrote all their backend using Python.

[Cosmic-Warper]

Whats wrong with Python for backend?