5 ms·
well 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 las
by julie1 11y ago
well 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 of speed diversity and complexity.
At the end, when we code it is for a business value. And for businesses web technologies are mostly expenses that grows faster and increase faster than economical growth. At one point this is condemning software business value in times of recession when people need to cut on costs to survive.
JS fast pace == a lot of manpower to keep application just up to date. It is a continuous growing bleed in the budget.
It is not the fatigue of the coder or sysadmins one should fear. But the fatigue of the business customers bored to pay for diminishing returns. Individual customers may still follow. But losing business customers will happen first.
Plus like it or not, updating browsers is not always as easy as you think it is. We all know of these legacy application that requires to keep a certain browser, and of new application requiring different one and the complexity of handling all these browsers. I used to have 6 browsers to code and test.
This is killing the business of coding and there is no "magic library" that will change the seasonality of the activity and the need for companies to keep their costs in control.
Industry out of IT requires for boring stable LTS technologies. The opposite of the offer of modern IT.
When offer does not meet demands ... company fail.
If ever USA or Europa, India, China announce a recession in 2016 or 2017 there will be blood in the IT.
It is all about costs and prices and making benefits at the end.
- woah 11y agoWhen was the last time an existing application stopped working because of new JS features?
- julie1 11y agoWell, 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.
- z3t4 11y agoThe problem now a days is phones. Their browsers work very different from desktop browsers.
- julie1 11y agoAnd set top box that may have another version of JS. Or the "javascript" used in Qt ... or any new appliance/software that wants to provide a common accessible language for their "events" and choose a JS that is patched to support stuff like hardware functions. I have been using these kinds of FrankeinJS in the past.
- LoSboccacc 11y agoWhen explorer 10 started reporting in js the availability of the firefox xml parser object but then it was not compatible and all code parsing xml suddenly broke for no reason, which is not javascript per se but it isn't like the language exists in a vacuum Or if you want language proper at some point node allowed keywords to be used as properies.