4 ms·

I'm a .NET developer (which means ASP.NET MVC back-end; razor views) and currently the front-end is just Bootstrap with custom javascript for interactions. I've

by NKCSS 10y ago

I'm a .NET developer (which means ASP.NET MVC back-end; razor views) and currently the front-end is just Bootstrap with custom javascript for interactions. I've written components to allow easy paged table data (which is usualy the only thing that is universally repeated; e.g. list data, have server-side paging/sorting and formatting functions). I want to use typescript for new development en eslint, but still haven't decided on the templating/component system. Leaning towards Vue but enterprise-wise, it seems smarter to pick Angular or React, where Angular seems to be the safest choice, but form all I've read, React seems more flexible (which is also the problem, since you can mix/match so many different pieces). I wished there was just 1 thing that was clearly better; would make my life so much easier :)

themihai 10y ago
Pick what works best or what you like most. Any JS framework becomes obsolete in a few years anyway and JS itself may become obsolete too(i.e. in favour of wasm). The most important thing is to ship it on time. Been there done that!
Pigo 10y ago
I came from an MVC background, where we created hybrids putting Angular or Knockout in the views. But lately I've been doing light-weight Angular solutions now with Webpack talking to Web API. Anyways, Angular 2 is more of a fair comparison to React, since your building components in both of them. The biggest difference between them seems to be that Angular puts js into the html, and React puts html into the js. So it really just depends on which development experience you'd prefer. The Angular team has a lot of sibling projects like Angular Material that I like using, but I'd like to experience more with React.
douche 10y ago
If you're used to doing Razor views, then moving to Angular 1 is a pretty straight-forward transition. That's what we've been slowly doing with one of our projects that was a colossal spaghetti mess of jQuery layered on top of Razor views.

by NKCSS 10y ago

themihai 10y ago

Pick what works best or what you like most. Any JS framework becomes obsolete in a few years anyway and JS itself may become obsolete too(i.e. in favour of wasm). The most important thing is to ship it on time. Been there done that!

Pigo 10y ago

I came from an MVC background, where we created hybrids putting Angular or Knockout in the views. But lately I've been doing light-weight Angular solutions now with Webpack talking to Web API. Anyways, Angular 2 is more of a fair comparison to React, since your building components in both of them. The biggest difference between them seems to be that Angular puts js into the html, and React puts html into the js. So it really just depends on which development experience you'd prefer. The Angular team has a lot of sibling projects like Angular Material that I like using, but I'd like to experience more with React.

douche 10y ago

If you're used to doing Razor views, then moving to Angular 1 is a pretty straight-forward transition. That's what we've been slowly doing with one of our projects that was a colossal spaghetti mess of jQuery layered on top of Razor views.