Death is not unexpected on whether it will happen, but when. Everyone dies, but you might be going to work one day and you die because of a moron burning a red light, or you might ne the healthiest person and get an incurable cancer, or people die from random hearth attack.
- Posts
- 0
- Comments
- 178
- Joined
- 2 yr. ago
- Posts
- 0
- Comments
- 178
- Joined
- 2 yr. ago
- JumpDeleted
Permanently Deleted
- JumpDeleted
Permanently Deleted
- JumpDeleted
Permanently Deleted
As a casual js user (I build some static sites for fun and personal use), I am under the impression that JavaScript "sucks" mostly because some things really make it look like JavaScript was invented as a quick scripting tool rather than the backbone of the WWW.
I'll bring an example that maybe helps me learning someting. Why in javasctipt "1" == 1? I know the === operator exists, but why isn't the default behaviour the safer one? Especially when the mantra is "don't trust the user".
Like, I get, I am a strongly-typed guy, but I see why weakly-type languges exists, but this feel frankly moronic, and all the answers I've seen are " because that's how it is". That's just copium.
Also when I tried to compile a single Cordova app to play around I needed some 5GB of npm modules that totalled ~200k files! Is that how modern app development is like?
Also, the particular webpage OP linked might be a little extreme, but modern software does suck ass, and is not user-friendly nor efficient. Just look at mobile communication apps, like Teams. The user experience is terrible, the UI is unrespive, the battery drain is crazy and it takes 800MB of space. Is this because it's an electron app, or because it's made by incompetent programmers? I don't know, but we made incredible hardware improvements in personal computing, new software should be even more efficient and use them better, not get more and more bloaty to have the same experience on older and newer hardware