Site seems to be down for me.
Perhaps the server experienced javascript fatigue and quit.
The Deep Roots of JavaScript Fatigue
11–20 of 189 posts
Re: The Deep Roots of JavaScript Fatigue
#12What isn't being said, and is painfully obvious to me, is that almost everything the article talks about wouldn't be happening if a. Browsers had a decent UI capability, and b. Javascript wasn't a piece.
And to what end? What website have I gone to that just knocked my socks off because they used framework X or library Y. None. And one year from now they'll toss it out for whatever else catches their short attention spans.
So much wasted effort.
Re: The Deep Roots of JavaScript Fatigue
#13well javascript is evolving at a fast pace. Wheat still grow on a seasonal base. Tourism is still yearly based. A car will last you years. telco CPE are lasting for years. Bank terminals are for years. Robots in factories last decades. Peacemakers are intended to last ages. Users do not really like to have their interface changed without any reasons to do simple tasks. Browser ecosystem is just running amok in terms…
When was the last time an existing application stopped working because of new JS features?
Well, read the source of jquery. You will see fixes for "old new features" of FF that broke applications in the past.
Given the way mozilla teams are still working I guess it can still happen.
EDIT and add the memory leaks and the change of performance that happens from time to time in new releases.
Re: The Deep Roots of JavaScript Fatigue
#14I thought the article started strong and skipped around serious issues so it could focus on a pretty nice history of JS, but the conclusion was horrible. > Babel has worked it’s way into the standard Javascript toolchain, and now most builders include it as a first-class plugin Which version of Babel, 5? or 6? Because there's a lot of incompatibility issues right there and I think it is just as symptomatic of the typ…
No, I lived the C-explosion of 30 years ago and it was absolutely nothing like what I see these days.
It utterly nuts how we are expected a learn a full-stack like Mongo/Angular/Backbone and then 6 months later is like NO we need AWS/React/Redux now!
It's my oldman opinion that IT has become too much like fashion and not enough like engineering, but that's what oldmen think so who cares.
Re: The Deep Roots of JavaScript Fatigue
#15Since the huge influx of new JavaScript developers happened we've entered a Wild West of development. Almost any combination of code is a great choice right now. It will settle down but open source stacks last only as long as their supporters. If you want to avoid all of the churn in JavaScript stacks then just write straight JavaScript, ES5 or if you want to just support bleeding edge browsers ES6. Then rely on a tr…
Or jQuery. That also has proved itself to be reliable.
Re: The Deep Roots of JavaScript Fatigue
#16Since the huge influx of new JavaScript developers happened we've entered a Wild West of development. Almost any combination of code is a great choice right now. It will settle down but open source stacks last only as long as their supporters. If you want to avoid all of the churn in JavaScript stacks then just write straight JavaScript, ES5 or if you want to just support bleeding edge browsers ES6. Then rely on a tr…
Or jQuery. That also has proved itself to be reliable.
Let the jQuery revival begin.
Re: The Deep Roots of JavaScript Fatigue
#17We are simply going through a Cambrian explosion in the JavaScript ecosystem.
Today there is huge demand for the ability to develop desktop standard applications inside the browser. At some point in the last few years we hit a tipping point where the potential to do this was unleashed. I am not sure exactly what the technology was that tipped us over, maybe a combination of several. Was it fast JavaScript performance, AJAX, client side frameworks or NodeJS? Whatever the cause the dam has broken.
In a few years the winners will emerge. But it is impossible to know if the current leaders are going to win or if another champion will appear tomorrow.
I intend to enjoy the ride and look forward to the improved productivity and capability of web apps that results from the chaos.
Re: The Deep Roots of JavaScript Fatigue
#18I was taking a shower, and this question popped into my head: What is harder to master nowadays? C++/STL/Boost or the Javascript ecosystem?
I don't know the answer.
Re: The Deep Roots of JavaScript Fatigue
#19I was taking a shower, and this question popped into my head: What is harder to master nowadays? C++/STL/Boost or the Javascript ecosystem? I don't know the answer.
As a C++ developer completely ignorant of everything going on in webdev, except that 'something.js is always the new hotness', neither do I.
I've basically ignored the boom in the web ecosystem for 10 years and have even less interest in getting in to it than 10 years ago.
Re: The Deep Roots of JavaScript Fatigue
#20I was taking a shower, and this question popped into my head: What is harder to master nowadays? C++/STL/Boost or the Javascript ecosystem? I don't know the answer.
As a C++ developer completely ignorant of everything going on in webdev, except that 'something.js is always the new hotness', neither do I. I've basically ignored the boom in the web ecosystem for 10 years and have even less interest in getting in to it than 10 years ago.
Hear, hear. I wrote gui applications fifteen+ years ago in MFC and the ATL. Front-end programming was boring then and it's boring now. I can't believe people are wasting so much time re-figuring this stuff out.