Hacker News Reader

Comment by NKCSS | Hacker News Reader

Nice backstory :)

Now if only I was able to pick wich framework to use in the future (still can't decide between React, Angular or Vue)...

View on HN

Pick any of them at random. Once you've got the hang of one of them, it will be easy (if necessary) to pick up another. Anyway, Angular and React will probably have been replaced by another generation within 5 years, so focus on the underlying skills and less on the syntax of a given framework.

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 :)

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!

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.

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.

For me it depends on what kind of project:

Vue - when I want to build something quickly.

Angular - when I want to build something bigger but don't have a lot of time and just want something that comes with all batteries included.

React - when I have time and can dedicate myself to the project. I still find all the boilerplate, tooling and research on what choices to make and modules to use bothersome but worth it in the end.

> I still find all the boilerplate, tooling and research on what choices to make and modules to use bothersome

Try create-react-app. It's supported by Facebook and makes all of those boilerplate decisions for you. And once you have a reason to change any of those decisions, you of course can.

Currently I found peace of mind with react+redux. Once you find a stable and well configured boilerplate (Redux slingshot for me), it's smooth sailing.

Alternatively go without a framework. It's actually not that difficult at all anymore. I'm actually writing up a small series about effectively creating web applications without a framework to show it can be done with decent looking code.

Pick react

React isn't a framework.

While this is technically true, it kind of misses the point doesn't it?

You would choose React over other 'frameworks' (like Angular). Plus, the React ecosystem is definitely 'a framework'.

Reply on news.ycombinator.com