3 ms·
While 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
by watwut 4y ago
While 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.
- lmm 4y ago> 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. They were advertising the same thing that modern low-code proponents are: the idea that you'd be able to change your application's behaviour by changing a configuration file, and that this would be superior to editing code. That was definitely part of the Java marketing. > Generics are nowhere near to being similar to C++ templating. Lol what. They use the same syntax and provide (not all of, but most of) the same functionality. > 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. I do use Java, I still hate them. They're very cumbersome, and again, the bottom line is: twenty years on no other language wants them, not even the likes of Kotlin. > There was no major hype about Java being faster then C or C++ in its origin. There absolutely was. The Java JIT was hugely hyped at the time, and there were even benchmarks showing it outperforming C on particular problems.
- watwut 4y agoThat is not what low code is.
- spacemanmatt 4y agoI think they might be conflating "programming by convention" which was what facilitated a lot of serialization schemes and other tooling that leaned in to the whole bean concept with lowcode.