5 ms·
It's a myth that developers follow trends because they're cool. The reason one picks up a new JavaScript technology is because it is a better and smarter way o
by andrewstuart 9y ago
It's a myth that developers follow trends because they're cool.
The reason one picks up a new JavaScript technology is because it is a better and smarter way of working.
Wave after wave of innovation is bringing better and smarter ways of doing things.
There seems to be some sort of vague idea that JavaScript programmers are following new libraries and frameworks like there is a Solid Gold Hit Parade of JavaScript and they all jump onto the number #1, and next month there is a new #1 so everybody changes to that simply because it is the new #1. That would be stupid.
I use ReactJS because it is a great way to program and gives and application an excellent and functional structure. I use ES2015 and ES7 because they make JavaScript very much more powerful than ES5. If something radically better comes along then damn right I'll switch to it if I can, because "better" means smarter, easier, faster, more powerful - some combination of those to a greater or lesser extent.
The JavaScript community desperately needs a fresh wave of innovation - but this wave must be about simplification - ideally the almost complete removal of all the pain associated with configuration of JavaScript build tools, which right now is excruciatingly and unnecessarily complex and painful - create-react-app has started this process and sets the standard for other tools moving ahead - the right amount of configuration is zero.
It is necessary to use a bunch of painful JavaScript configuration and build tools in order to get your stuff to run. Waves of better, simpler and smarter build tools overrun the previous generation because they have found simpler and easier and more powerful ways to work.
Lets just drop the idea that JavaScript programmers are a bunch of airheads who follow the latest trends whilst they pull on their flared pants and fancy hairstyles.
- alanfranzoni 9y agoI hope that, at least, the new technology is better than the old one. But I have some objections: - why can't old libraries/frameworks/things evolve, instead of forcing a breaking change? In many other languages evolution seems to preferred to revolution; in JS, evolution seems to be the norm. - Is that "better and smarter way of working" THAT MUCH BETTER AND SMARTER? When working JS, it seems that a complete overhaul of an application (or of an ecosystem) is required every very few years. Ultimately, software development should lead to business value; does the improvement in generated business value justify the costs associated with such a tech twirl?
- andrewstuart 9y ago>> Is that "better and smarter way of working" THAT MUCH BETTER AND SMARTER? Absolutely yes. ReactJS is an application architecture that is a complete rethink of how to structure client side applications, and it is an architecture that is being applied outside JS and the browser because it is so much better. The fundamental concept of one way data flow from parent to child through the application requires a start from scratch approach, and would be severely compromised were it to be implemented as an "additional" evolution of some existing application framework such as AngularJS. Yes - that much better and smarter. ES2015/ES7 are radically better languages that make hugely important changes to JavaScript. Yes - that much better and smarter. Transpilers make it possible to run ES2015/ES7 even on browsers that support only ES5 - that is amazing - yes - that much better and smarter. Build tools such as minifiers and packers and uglifiers perform magic to shrink and optimise code for a range of benefits including end users performance - Yes - that much better and smarter than sending a chunk of raw JS to the browser. In short, yes, JavaScript is experiencing a continuous wave of really major and significant improvements that justify ditching the previous generation entirely. I will say however that breaking changes give me the shits abut for the most part I am willing to endure them - I simply must assume that the changes are for the better because I don't have time to really understand every single change in every library that goes into my application - no JavaScript developer does - nor indeed does any Python developer try to understand every change to all the Python libs that they use.
- Peaker 9y agoIf you're willing to use transpilers, why stick to JS at all, when you have a wealth of languages available? Scala, Purescript, Haskell, Elm, ...
- _ar7 9y agoBecause JavaScript 1. By far, has the largest ecosystem. 2. If you use a linter, a typechecker (TS or flow), and transpile your code (TS or babel or both), JavaScript is actually a pretty nice language to work in. Sure it's a chore to set up all the initial tooling, and learn the ins and outs. However, once you're past that, it's usually not worth it to switch.
- gkya 9y agoI'm sorry but no, that's not a myth at all, and innovations aren't coming in waves. It's mostly a mistaken perception of the sheer volume of action in the JS sphere, most of which is not innovation at all.
- mattmanser 9y agoMy feeling with the ever growing list of fotm js frameworks that are now firmly dead and buried in the ground is this: 10 ShinyNewJSFramework = 1 20 Use framework 30 Do conference speech about how much better it is than JQuery 40 Hit problem X 50 Find ShinyNewJSFramework is nigh impossible to debug 60 Eventually come to loathe framework because of problem X 70 ShinyNewJSFramework += 1 80 GOTO 20
- ojr 9y agoWith React, Redux, Babel, Webpack, I would say there are a lot of innovations coming in through there, and the plugin system is being moved from angular, jquery, gulp to these, if you're writing old javascript to target ES5 compliant browsers more power to you, targeting the next version ES6 increased in volume a lot just recently the version is literally called ES2015
- ehnto 9y agoThe long view of the innovation in React is that it is a tool enabling a change in pattern from "separating concerns of the view layer" to "modular components that get fed data" which is definitely a shift in the way we have previously worked with the frontend and I find very cool. It was also specified in the Web Components spec that is set to become a browser native technology, so React and friends will hopefully be replaced by native components and maybe we can all start focusing our efforts on building standard libraries of re-usable code that will be easily portable, and we can all forget the JS Gold Rush ever happened.
- ousta 9y agoYeah Clearly NODE.JS was not picked because it's cool but because of its single threaded poor performance (talking about the cool years of node.js)
- ojr 9y agothe cool years of node are just beginning with AWS Lambda and other cloud services that help node.js scale easier
- tobltobs 9y agoWait, maybe I am dumb, but why do you need AWS Lambda to scale Node.js better? You use something like Lambda which is build to handle one request per instance to scale something which is single threaded anyway?
- fenwick67 9y agoSay I have an endpoint that has to parse a giant JSON object, which can take 100ms to parse... if that locks the thread it can block another request. With lambda I would just make one lambda function for each route and routes won't block each other.
- ralusek 9y agoCompared to Python or Ruby, NodeJS has phenomenal performance. The single threaded argument is also flat out wrong, given that you have clustering or web workers to take advantage of every core. It's also completely misleading even within a single core, as non-blocking nature of JS will accomplish on a single core what otherwise behaves as threading would.
- awjr 9y agoMy journey has been JQuery -> Angular -> React with background noise of Node.js I've specifically tried to avoid Choo/Vue/Whatever until there has been real traction in the job market and the community behind that framework. BUT the move from each 'framework' to the next has been a revelation in how to do things better. I feel comfortable now that React is delivering an ecosystem that is going from strength to strength and has brought a maturity to the front-end javascript ecosystem that was missing. Huge props to the community for that.
- RonanTheGrey 9y agoYep definitely, either way React is here to stay and it is in large part not due to Facebook, but to the maturity of the community that has supported it. I'm consistently impressed by their level of professionalism.