Re:JavaScript Fatigue or My History with Web Development
by gkya on Tuesday June 27, 2017 @05:40AM
(#14643676)
I'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.
[ Parent
| on HN ]
Re:JavaScript Fatigue or My History with Web Development
by mattmanser on Tuesday June 27, 2017 @06:16AM
(#14643851)
My 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
Re:JavaScript Fatigue or My History with Web Development
by lovemenot on Tuesday June 27, 2017 @08:02AM
(#14644543)
This subroutine also describes 3.5B years of evolution. Nearly all ancestors of extant creatures are dead and buried too.
Re:JavaScript Fatigue or My History with Web Development
by x220 on Wednesday June 28, 2017 @12:29AM
(#14651685)
Yes, but evolution is stupid and slow. I don't want to wait 1 billion years for JavaScript to be developer-friendly.
Re:JavaScript Fatigue or My History with Web Development
by ojr on Tuesday June 27, 2017 @06:45AM
(#14644037)
With 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
Re:JavaScript Fatigue or My History with Web Development
by ehnto on Tuesday June 27, 2017 @09:11AM
(#14645014)
The 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.
Re:JavaScript Fatigue or My History with Web Development
by RonanTheGrey on Tuesday June 27, 2017 @03:13PM
(#14648348)
This is honestly the direction I see us going. Angular has also created a component concept nearly identical to React, the only difference is implementation details. It's a natural way to go, because it decreases cognitive load.
I am intrigued and ponder the idea of there being "JS Standard Libs" and wonder which ones will initially get picked for the honor. I don't think it will be React or Angular but definitely "something" like them, even if it is a version of Web Components.
That'll also mark a huge change in performance and download metrics, because if your browser already has your framework built in, your delivered code base is suddenly a fraction of what it was. And then there will be more opportunities there, too - dynamically providing the framework where needed in a separate code split, vs. a browser that does not need it.
We're just at the beginning, really. Browsers stalled for 15 years and have shifted into a period of innovation again.