|
|
|
|
|
|
by nitsky
1956 days ago
|
|
|
> All the issues with JavaScript are trivial If the problems with JavaScript are trivial, why are the solutions such as webpack, babel, and typescript so complicated. Many companies have whole teams of people dedicated to maintaining solutions these problems. > and new features and frameworks are available to overcome most issues. Producing JavaScript apps that are both fast to run and easy to maintain does not feel like a problem that has been solved yet. |
|
|
Because building user-facing clients that run on a bunch of moving-target user machines instead of one big server has fundamental differences and challenges that afflicts all client development, no matter which language you're using nor the platform you're targeting, nor have centralized proprietary platforms that work on a single line of phones (Android, iOS) fared much better than the opposite, disjointed, organic approach of volunteers (the web).
Why? Because it's hard, and hard for everyone.
> Producing JavaScript apps that are both fast to run and easy to maintain does not feel like a problem that has been solved yet.
You say that like you think anyone has solved it. How to build UIs in a world of constantly changing consumer tech is still an open question because it's hard, and it will always be. Apple is still straddling spaghetti code KVO systems from the 70s, and their new-fangled SwiftUI platform is still so buggy that the last three places I held an iOS contract with were clinging to UIKit.