3 ms·
I think JS has this problem because of constantly high inflow of new developers who easily get on new boats. They cannot differentiate between old and new tools
by wruza 9y ago
I think JS has this problem because of constantly high inflow of new developers who easily get on new boats. They cannot differentiate between old and new tools (except for hype and cv-driveness), and new tools don't kill their productivity as much. Personally I never made it into frontend because learning basics makes me sick of html/css/js trinity, and learning advanced tools is a neverending war. Advanced js programmers feel that and try to create more tools, shorting the circuit.
(Otoh, programming has changed since our youth time. Back then we programmed for one local, now we do it for thousand remotes. Latency penalties turned upside down literally, storage is faster than SIMM, ui is slower than FDD.)
Since web 1.98a* we stopped to look at program as a whole and separated it into frontend and backend. That was a key point that allowed so much divergence and frustration. It may sound crazy, but we need new, more low-level browser (don't even call it browser, it is a network layer) that could seamlessly connect single heterogenous app on two network endpoints, since no one really cares about underlying protocols anymore. Leave www rot in browser and make internet apps great again. All good tools from '95 are still here.
* you cannot call something 2.0 until it has at most 2-3 generic and mature ways to do everything.
- flukus 9y ago> It may sound crazy, but we need new, more low-level browser (don't even call it browser, it is a network layer) that could seamlessly connect single heterogenous app on two network endpoints XWindows (https://en.wikipedia.org/wiki/X_Window_System https://en.wikipedia.org/wiki/X_Window_System)?
- digi_owl 9y agoEverything old is new again... https://en.wikipedia.org/wiki/Time-sharing#Time-sharing_business https://en.wikipedia.org/wiki/Time-sharing#Time-sharing_busi...
- icebraining 9y agoWhy do we need new stuff? What's wrong with the existing ways of connecting processes over the network?
- verinus 9y agothe effort required to write boilerplate code over and over again with no standard way I would guess...
- model_m_warrior 9y agoI've written JS every day for nearly 10 years now. I do not have an answer.
- timrichard 9y agoWhy do we even need to connect processes over a network? What's wrong with dumb terminals?