2 ms·
I reject that it's specific to "our generation". The people who made the monumental balls of complexity that Java is known for certainly aren't part of "my gene
by mort96 5y ago
I reject that it's specific to "our generation". The people who made the monumental balls of complexity that Java is known for certainly aren't part of "my generation" at least. And we have contemporaries who embrace simplicity in significant and impactful ways.
- theflyinghorse 5y agoJava and Java ecosystem are an interesting case. Looking back over the last 15 or so years of Java most orgs went through massively over complicated setups like EJB containers to slightly better spring (GWT probably deserves a mention), to much better spring boot, and now to smaller, saner frameworks such as javeline or micronaut. The language itself is leagues and bounds ahead of what it once was in java 7 and before. And of course, the all consuming drive to use every conceivable design pattern is not in style any longer. Generation has nothing to do with it, but trends have everything to do with complexity and constant change.
- cryptos 5y agoThe new hipster shit of overcomplexity is putting every code snippet into a micro service, or just skip microservice and deploy everything as AWS lambda functions. Hype-driven development is a tradition.
- pjmlp 5y agoThose people will make monumental balls of complexity regardless of the technology, that is what enteprise architecture is all about. Every generation has a couple of people earning their bread as enterprise architect.
- saurik 5y agoI did a lot of development with Java in those days and virtually every Java package that mattered was a library, not a framework, and if anything the reason everything was so complex was because it was so configurable and pluggable, making it easy to use that with this and a little of something else without having to decide on a "framework".