r/webdev • • Jul 09 '16

6 Best JavaScript Frameworks to Learn In 2016

http://www.discoversdk.com/blog/6-best-javascript-frameworks-to-learn-in-2016?
0 Upvotes

10 comments sorted by

7

u/ternarysolo Jul 09 '16

I wish these articles comparing frameworks would show some small code samples. As a programmer, perhaps the most important thing for me when choosing a framework, is what does it look like?

Sorry to be a cranky twat, but here are some other issues I have with the article.

  • React is not "an MVC (Model-View-Controller) type framework". React is only the view layer. Yes, you can use make MVC apps with React, but you will be (should be) embedding React as the V layer.

  • (Referring to React) "which enables you to use it from node.js as a client-side framework". I think you mean to say that you can render .jsx templates to html using node on the server and send that to the browser?

These are some more nitpicky issues (sorry): I feel like the author is just slightly misinformed about a couple of things. Like the importance of OSS as a feature for a JavaScript framework (they all are in the article). Similarly, the importance of the M** paradigm that frameworks use. It doesn't necessarily affect the quality of a framework. I would argue that no one really likes MVC or MVVM or MVTPL, it's just a paradigm used to solve a problem. Maybe a good analogy is saying "If you like heapsorts, you will love this algorithm.", other algorithms have their place and use cases.

1

u/bootleg_pants Jul 13 '16 edited Jul 13 '16

I don't think that's nitpicky. 'Similar to AngularJS, React is also an MVC (Model-View-Controller) type framework, however, it focuses entirely on the View components'. By definition, an MVC framework requires the M and C components

Likewise, I don't exactly appreciate that the intro makes it seem that the entire article is for beginners, yet would be a little less useful for newbies because it doesn't mention how quickly tutorials become useless for some of these frameworks, or even mention, and I can't count how many 'beginner' tutorials I've come across that don't mention to include babel, babel-core, babel-preset, webpack, etc and all the things that are required to actually get the code in the tutorial up and running.

On a side note, all of the pronouns in this article assume that the developer is a 'he'. It's 2016, how is this still a thing?

0

u/TheCallMeRalph Jul 09 '16

Hey Ternarysolo you can find samples under the code samples

1

u/ternarysolo Jul 09 '16

It doesn't seem like there are examples of any of the frameworks you mention?

Plus, I mean inline examples. For example, I am interested in how easy list rendering is:

<!-- VueJS -->
<li v-for="m of messages">{{ $index }} - {{ m }}</li>
<!-- React -->
this.state.messages.map((v,k) => <li>{ k } - { v }</li>);

4

u/mattaugamer expert Jul 10 '16 edited Jul 11 '16

People seem to be enjoying this article well enough, but it seems like it's... well... completely inaccurate and useless. I'm not expert, but I know this stuff well enough for a whole bunch of stuff to jump out at me.

Why is no one calling this out?! I'm ignoring the general buzzword-salad and overall feeling of being cribbed from wikipedia and other online sources by someone with little knowledge and possibly ESL.

Angular

It supports the MVC (Model–view–controller) design paradigm which supports standard two-way data binding.

Supports, sure, but to my understanding Angular 1 is an MVVM framework in most usages, not to mention two-way data binding is generally agreed to be a bad idea and most modern frameworks - including Angular 2 - omit it. I wouldn't be selling it as a feature.

In case you are not familiar with MVC, then know that it just means that your data is updated on both the front-end (i.e. user-interface side) and back-end (i.e. coding or server side) whenever it detects some changes in the engine.

That's not what MVC is. That's not what MVC is at all. What the fuck?!

MVC drastically reduces the time and efforts needed for building complex applications, as you need to focus on one area at a time

Not really. It is just a pattern that keeps things more maintainable. It doesn't "reduce time and effort" at all. It just keeps things neat.

(because DOM programming interface synchronizes the view and the model).

That's... am I misunderstanding or is this kind of gibberish? Like... in context.

Angular 2.0 has recently been released,

The previous paragraph talks about Angular looking like Typescript (which sounds like BS to me, but I don't know enough Typescript to really criticise it) and then it jumps to Angular 2 without even mentioning that this genuinely DOES use Typescript?!

powerful MVC framework with a strong and modern infrastructure

Lol.

React

Similar to AngularJS, React is also an MVC (Model-View-Controller) type framework

It's almost impossible for this to be more wrong. Even if conceding AngularJS as an MVC framework (debateable) React is far better described as purely a single layer, more likely the ModelView layer of an MVVM based structure.

so you get extremely fast rendering of the UI, which enables you to use it from node.js as a client-side framework.

This is a sort of woeful mis-stating of Universal Javascript in React.

If you have seen and like Facebook and Instagram’s interfaces, then you will love React.

Wot. Enjoying a service or interface has no bearing on the developer experience.

Ember - my preferred framework so I found the most issues here

It uses Model–view–viewmodel (MVVM) design pattern,

It absolutely 100% does not. This is simply not true. Ember uses a rather strict MVC pattern.

Its modern routing and model engine supports RESTful APIs, so you are ensured that you are using the latest technology.

The router has nothing to do with RESTful APIs, and the model engine (Ember Data) supports a range of things, it's an abstraction away from specific implementations. REST is hardly "the latest technology".

In 2015, it was named the best JavaScript Framework

By who? This is meaningless.

I would personally highly recommended this JavaScript Framework to those who don't necessarily need great flexibility or a large infrastructure

What does this mean? Ember is at its best in a large project.

VueJS

Like Ember, it uses the Model–view–viewmodel (MVVM) design paradigm

Ugh

BackboneJS

It has the RESTful JSON interface

I feel like you just copied that out of Wikipedia without really understanding it.

with the support of MVC (Model–view–controller) design paradigm

But if you'd copied the next few words you'd have seen that Backbone is MVP, not MVC, it uses a Presenter.

(that updates the front-end and back-end automatically).

Good god no it does not

2

u/CloseDdog full-stack-ish Jul 09 '16

Has anyone actually used Adonisjs? As a fan of Laravel it does interest me, but I haven't really heard any experiences of people using it.

2

u/ffxsam full-stack, serverless Jul 10 '16 edited Jul 10 '16

I’d remove Backbone (really??) and replace it with Meteor

3

u/mattaugamer expert Jul 10 '16

Backbone I'd agree with, it's showing its age badly. But I love Ember, and can't recommend it highly enough. That said, Meteor is pretty great, but Phoenix is not a Javascript framework, not sure why you think that fits.

1

u/ffxsam full-stack, serverless Jul 10 '16

Oops. Late night redditing. Fixed

1

u/lilred181 Jul 09 '16

I have deployed an application using VueJS and it's modular design was quite nice, only pulling in the packages I need was pretty nifty (ajax, routing, etc)