6 ms·
Which ones did it deliver on? Faster than C? No. A memory-safe language that you can write OSes and drivers in? No. Pleasant cross-platform GUIs? No. Easy code
by lmm 4y ago
Which ones did it deliver on? Faster than C? No. A memory-safe language that you can write OSes and drivers in? No. Pleasant cross-platform GUIs? No. Easy code reuse? No. Low code development by using XML? No. Not needing generics? No. Checked exceptions being a good idea? No. More understandable code by using classes instead of lambdas? Hell no.
Java more or less got "write once, run anywhere" working, I'll give them that (although I still see programs that e.g. use a hardcoded path separator, they're the exception rather than the rule). But it's hard to see anything that it really delivered on in terms of working better than e.g. OCaml.
- watwut 4y agoWhile Java is actually fast now and fairly often faster then C, it was not original promiss at all. > Easy code reuse? Yes, as proven by rally large ecosystem of libraries and frameworks. All of that is literally code reuse. > Low code development by using XML? No. This was NOT original promiss at all. Again, these were first attempt at creating larger frameworks. > Not needing generics? No. Checked exceptions being a good idea? No. What are you talking about here? And yes both generics and checked exceptions have their use and dont make creating or maintennance of software hard at all.
- lmm 4y ago> While Java is actually fast now and fairly often faster then C, it was not original promiss at all. It was absolutely something that was claimed at the time. Java's JIT, good as it is, has not lived up to the hype, to the point that newer languages (and even newer versions of Java itself) are moving away from it. > This was NOT original promiss at all. Again, these were first attempt at creating larger frameworks. It was absolutely something that was advertised by Spring and by Java EE, and didn't pan out. > What are you talking about here? And yes both generics and checked exceptions have their use and dont make creating or maintennance of software hard at all. The original Java claimed that a feature like C++ templating was not needed, which proved to be false. Checked exceptions are widely regarded as a failure; no major new language (even on the JVM) uses them.
- spacemanmatt 4y ago> by Spring and by Java EE Spring is definitely a 3rd-party library builder, and I'm unaware of promises like that from Java EE. Can you help me understand what informs your view on that? It seems like they delivered a bunch of stuff that made it easy to consume XML for all kinds of questionable as well as reasonable purposes, but it was Spring not Java trying to turn XML into a scripting language.
- lmm 4y agoMy view is based on my experience of being a developer in those days and seeing what was being hyped at JavaOne or sent out in talks from Sun. It wasn't just Spring (indeed Spring got its start as a lighter-weight alternative to JEE), there was a whole lot of marketing tying Java and XML together, and as far as I can see the heart of it was this idea that you could use XML configuration to string together reusable Java components instead of writing code.
- spacemanmatt 4y agoI can sympathize to some extent. Don't believe the hype, next time. But also don't dismiss the success.
- lmm 4y agoThe lesson I took from it is that marketing matters more than technical merit. Don't get me wrong, Java is fine, there are far worse languages out there. But at the same time very little of the USPs it was supposed to have really panned out.
- watwut 4y agoSpring is framework, it is not part of language itself. It is part of ecosystem around java. Neither spring nor Java EE promised to be low code. It used xml for configuration, but not because it would somehow aimed to be low code. Generics are nowhere near to being similar to C++ templating. Also, I never understood hate of checked exceptions that invariably comes from people who dont use Java. They don't bother much and have their place. There was no major hype about Java being faster then C or C++ in its origin. They quite explicitly talked about sacrificing speed for other properties. Java however got faster in later developments.
- kaba0 4y ago> A memory-safe language that you can write OSes and drivers in? No. Why couldn’t you? There was always an escape hatch API that let’s you manage that few direct pointer accesses mandated by hardware - otherwise the rest could very well be written in a managed language (as shown by research done by Microsoft for example)
- lmm 4y agoRight, that's exactly the kind of thing that Java's promoters said. But it doesn't seem to have panned out; I don't think I've ever seen a driver written in Java (even though I have seen certain kinds of drivers written in Python).
- kaba0 4y agoA driver doesn’t exist in a vacuum, they are attached to OSs, and all prominent OS today is written in C. Python does have better FFI with C than java, but I really don’t see how that would prove anything contrary to Java.
- lmm 4y agoWhatever the reasons are, the fact remains that it's an example of Java not living up to its early hype.
- spacemanmatt 4y agoI don't remember any claims that people would write general-purpose OS drivers in Java. I do remember the claim that many app-level drivers would migrate from native wrappers to pure Java. And that happened.
- goto11 4y ago> Easy code reuse? No. It is hard to argue against the Java ecosystem of libraries.
- spacemanmatt 4y ago> a hardcoded path separator I use forward-slash (/) on Windows and OSX/Linux, and the JVM/libraries do the right thing all day. Please enjoy.
- lmm 4y agoGood for you. I still can't build a project that I want to build on Windows, because its build system tries to calculate a relative path by breaking the current working path on '/' characters.
- erik_seaberg 4y agoNo language or platform is going to force me to use stdlib properly and prevent me from doing something badly the hard way.
- lmm 4y agoSomething that the people hyping Java in its early days would've done well to remember.
- spacemanmatt 4y agoBroadly speaking, the Java argument was to make it easy to do the right thing, not making it impossible to do the wrong thing. Especially when the interface to a filesystem depends on parsing structure from a string.
- spacemanmatt 4y agoYou sound like a coder. Fix it. That's not Java's fault after all these years and available solutions.