4 ms·
Yes, Java was a whole product, and that was a great thing. Also: helpful error messages. But was your choice to learn Java somehow related to it being popular
by hyperpallium 8y ago
Yes, Java was a whole product, and that was a great thing. Also: helpful error messages.
But was your choice to learn Java somehow related to it being popular in industry?
More so in the past, portability - meaning not being locked-in to a specific vendor who could then screw you - was a big deal in industry. Today, there's much less heterogeneity (x86, ARM and...?).
Part of Oracle's pitch for their database was that they ported it to different machines, so users weren't locked in (even if they didn't actually use it on different machines).
- tapanjk 8y ago> But was your choice to learn Java somehow related to it being popular in industry? Yes, but only partly. I had evaluated becoming one of Java, C++, or Oracle programmer (I know the last one is not the same thing, but was a career option nonetheless).
- taneq 8y agoIronically, portability was one of the main drawcards (well, that and being able to embed it in web pages) when I first learned it, but I quickly found that a Java application was far less portable, in reality, than an i386 Windows executable. That one friend with a Mac might be able to run it but nobody else could without downloading 65MB of JRE.
- hyperpallium 8y ago"write once, debug everywhere"