2 ms·
> Meanwhile, the shitty tech is winning. According to this author, bad code and bad tools and bad frameworks are reigning supreme over real engineering. Why? T
by com2kid 5y ago
> Meanwhile, the shitty tech is winning. According to this author, bad code and bad tools and bad frameworks are reigning supreme over real engineering. Why?
The funny thing is, 20 years ago the same arguments were being made.
"Windows MFC is a nightmare to write against!"
"X11 is terrible, why are we using it?"
"Everything we write is built on so many abstractions developers don't know what they are doing."
"VB6 is dumbing down development"
"Developers writing in Java don't understand what is really going on."
"Java is too slow!"
OK the last one was true. UIs in Java were obscenely memory intensive relative to computers back when Java was first introduced.
But yeah, more things change, the more the complaints stay the same.
- tuatoru 5y agoAll of them are still true, except for the last one (for nearly all use cases).
- stillkicking 5y agoJava got its slow reputation mainly because any early encounter with a Java applet would proudly display the Java logo and then cause your computer and disk to thrash for 30 seconds. Then Java developers heard this, confused it for "Java executes slowly" and so they never fixed it, until Java applets just became obsolete.
- com2kid 5y agoEclipse didn't help Java's reputation any. "Amazing new IDE has just come out! Good luck running it!" Also local Swing apps were memory hogs compared for the time. 20MB was a lot on a machine that had 256 or 512MB in total.