3 ms·
The anti JavaScript ranting is tedious and redundant, however he points out that virtually no React Native code uses Flow, etc., so it's an unused solution. The
by Tloewald 10y ago
The anti JavaScript ranting is tedious and redundant, however he points out that virtually no React Native code uses Flow, etc., so it's an unused solution. The point about React having hundreds of dependencies is also well taken.
While I'm at it, I find the graphs towards the end claiming, for example, that using Xamarin (or Appcelerator) is more productive than React Native, or implying Swift is barely shy of perfectly safe to stretch credulity.
Finally, Javascript's "slow" state of development is a feature as well as a weakness, just as Swift's rapid pace of development is both a weakness and a feature. React itself progresses at a breakneck pace.
- pluma 10y agoI actually find it ludicrous the author is complaining about JS's development as a language being too slow. Just the other day I presented ES2015/2016 and the upcoming changes scheduled for 2017 to a room full of JavaScript developers and the general feedback was that JS was changing too quickly. The reason ES2015 was so huge and so delayed was actually that ES5 was pretty much the lowest common denominator everyone was able to agree on after the proposals for ES4 went up in flames. ES5 is necessarily incremental and ES2015's delay was mostly caused by the repercussions of ES4's failure -- ES4 failed because it valued innovation over backwards compatibility. I mean TC39 has announced that they will make a new release every year, batching whatever proposals are stable at that point. How can anyone call that particularly "slow" with a straight face?