3 ms·
Spring 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
by watwut 4y ago
Spring 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.
- lmm 4y agoNot just serialization. I'm talking about things like the drag and drop graphical flowchart thing that WebSphere has (or had), which behind the scenes is an editor for XML files that instantiate a bunch of EJB. With Spring you don't get the graphical builder part but people were still pushing the idea that you would edit the XML files rather than your application code and this would be better. I know those are second- or third-party frameworks, but WebSphere was the flagship JavaEE implementation and I swear this was the stuff Sun was hyping up as examples of what Java would let you do.
- spacemanmatt 4y agoOk, now you are talking about success that Sun and/or Java community did deliver on. I loved composing object maps with application.xml when I was a Spring user. That was a full head+shoulders above hand-coding constructors and calling setters. And yes, it was a clean interface for a GUI but I never went there. To be sure, that is configuration, though.