Live data from Hacker News

2017 JavaScript Rising Stars

risingstars.js.org

41–50 of 101 posts

Re: 2017 JavaScript Rising Stars

#41
post #30

Earlier quoted context omitted.

No language that "compiles to javascript" really creates new language primitives - it would have to rewrite the interpreter to do that. What it does do - simulating new language features in javascript - could theoretically be done with a framework as well.

No, you wouldn't get the required compile time checks. (Transpile time checks in exact)

A compiler takes input in one language and converts it to another language. That the web community has a fundamental misunderstanding of this and created a derivative word with the same meaning is unfortunate. That it is now being used in misguided pedantic arguments reflects poorly on our community.

Re: 2017 JavaScript Rising Stars

#42

Why is Polymer left out of frameworks top 10? It has 18k stars and should be No. 3... https://github.com/polymer/polymer https://risingstars.js.org/2017/en/#section-framework

First of all, that is "stars added in that year", not "stars total".

Secondly, shouldn't the fact that that would have made Polymer #3 given you some thought?

Polymer has ~19k stars total.

React has ~85k stars total.

Vue has ~80k stars total.

AngularJS (v1) has ~58k stars total.

Angular (v2+) has ~32k stars total.

Ember has ~18.6k stars total.

Preact has ~17k stars total.

So Polymer is behind React, Vue, AngularJS and Angular on total stars, having just surpassed Ember. Placing it 3rd in the rising stars list would have placed it before Angular.

I'd think "Polymer is more popular than Angular" would have been pretty newsworthy.

Re: 2017 JavaScript Rising Stars

#43
post #34

Hmm, this feels very misleading. What is the correlation between Github stars and real world usage? This is not statistics, it's just 1 variable.. It almost feels like Vue.js is going to take over React just because it received more Github stars? I use React already for years, never gave it a star on Github, and I think many with me.

Stars are pretty useless for what they wanted to measure. Real-world data paints a different picture http://www.npmtrends.com/angular-vs-react-vs-vue-vs-@angular...

Even searching Github for 'import React from 'react' and 'import Vue from 'vue' results in similar percentages. Roughly 7-8 million projects in Github on React, under a million on Vue.

Despite the hype, Vue has been mostly a flat over the last 2 years with a slight upward bend, but only to the point where it begins to catch up with the old Angular 1.x.

Re: 2017 JavaScript Rising Stars

#44
post #3

The article mentions that Ava differs from Jest because of its focus on speed. Just figured I'd mention we are in the process of migrating from Ava to Jest, and we gained a 5x speedup in running our entire suite.

I never understood the Ava speed claim. Always was much slower than either Mocha or Jest.

Re: 2017 JavaScript Rising Stars

#45
post #31

From the Vue.js information page on that site, 'The concept of single-file component that includes template, logic and styles in a single file .vue file is really nice.' NO IT IS NOT!

Instead of shouting, could you give some pro’s and cons you have encountered using Vue single file components?

Re: 2017 JavaScript Rising Stars

#46

It’s a bit unfortunate that Elm will always be left out of lists like this. Yes it’s a different language that compiles to JavaScript, but unlike other languages that do this, Elm exists solely to excel at front-end web development. Ironically, that Redux and React equivalents are some of the “batteries included” in Elm can make it harder to pitch because at first it seems like you’d have to add that stuff in.

They included purescript (compilers), so why not elm, which has orders of magnitude more users?

Re: 2017 JavaScript Rising Stars

#47
post #17

First I'd heard of dva [1] (#6 in the frameworks section), interesting that it eases use of redux-saga as well as the usual abstractions over redux. redux-saga has been something I've avoided after initial evaluation (I also avoid redux unless absolutely necessary), but might take a second look with this. Hope the project gets some more English translations! https://github.com/dvajs/dva/issues/1#issuecomment-33433418…

Ditto with Ant Design (#14 on most popular projects) where most of their community is Chinese: https://github.com/ant-design/ant-design/issues. Their UI framework is the most comprehensive I have seen.

I am sure english will remain the dominant language for a while but I wonder if it makes sense to start learning new (human) languages just to open up the number of communities you can learn from?

Re: 2017 JavaScript Rising Stars

#48
Super anecdotal / off topic but still fun. In 2014 I emailed with a guy who worked at Google to take over control of a domain he wasn’t using. All was well and he gave me access. I checked his Github project. Some tiny SPA framework with three examples and a handful of github stars. Looked nice. Fast forward three years.

Over 2017 me and my (former) small dev team embraced Vue.js, built a non trivial checkout flow and visited the first Vue.js Conf Poland. I’m neck deep in Vue for other projects.

That guy in 2014 was of course Evan You, creator of Vue.js, and I guess I bought the domain for one one of the candidate names for Vue.

Re: 2017 JavaScript Rising Stars

#49
post #30

Earlier quoted context omitted.

Because a framework can't bring new language primitives, such as types?

No language that "compiles to javascript" really creates new language primitives - it would have to rewrite the interpreter to do that. What it does do - simulating new language features in javascript - could theoretically be done with a framework as well.

You don't know what you're talking about.

Re: 2017 JavaScript Rising Stars

#50

It’s a bit unfortunate that Elm will always be left out of lists like this. Yes it’s a different language that compiles to JavaScript, but unlike other languages that do this, Elm exists solely to excel at front-end web development. Ironically, that Redux and React equivalents are some of the “batteries included” in Elm can make it harder to pitch because at first it seems like you’d have to add that stuff in.

If I recall correctly, the state-of-JS survey did not even have an "Other: ____" field for the Flavors category [1]. Which means that people going to the survey had no way to even mention alternative languages.

The set of languages on state-of-JS is therefore artificially constrained to what the creators of the survey think deserves a place there, rather than the actual community thinks.

[1] https://stateofjs.com/2017/flavors/results

Post reply on HN