3 ms·
After using Akka and Scala I cringe at the thought of going back to use Java, even for simple dimple projects. As one commenter already put it, so much of Java
by jjm 16y ago
After using Akka and Scala I cringe at the thought of going back to use Java, even for simple dimple projects.
As one commenter already put it, so much of Java frameworks are overly engineered. Which begs the question as to why do so many implementations at so many corp situations I've been in have developers under engineering usage...
I take it business probably sees over engineered goods as "less work" for developers to code. This perhaps allows the hiring of "lesser qualified" engineers...hm...
- SoftwareMaven 16y agoThe excuse I've heard is it "let's people who are specialists do the 'hard' stuff." you know, like reading a configuration file... There are some cases this makes sense for (scientific computing, machine learning, etc), but I think nirvana in the community is being able to write an app via XML configuration files.
- EdiX 16y agoI find it ironic that programmers that would be otherwise extremely averse to dynamic typing are willing to write so much code in the form of a dynamically typed XML mess that is interpreted at runtime
- SoftwareMaven 16y agoAnd how afraid people are to type "new XXX()" in their code. A dependency is a dependency, and I'd rather have it in the source code, myself, than in some configuration file held outside the source. In fact, it seems downright dangerous, because it encourages changing implementation directly on a production system rather than forcing changes through a change-management process.