7 ms·
i hear you - then let me ask you: what would make Java frameworks better (not the language) ? Not just for existing developers, but also people who are new to
by sandGorgon 4y ago
i hear you - then let me ask you: what would make Java frameworks better (not the language) ?
Not just for existing developers, but also people who are new to the language and are doing the old golang vs java eval.
- stickfigure 4y agoHere's what I generally use when doing greenfield development in Java: https://github.com/gwizard/gwizard https://github.com/gwizard/gwizard I wrote it, so feel free to consider me biased. That said, "wrote" is a strong word, it just glues some other projects together with Guice. Not much actual code there. Which may be the answer to your question - if you asked me what's wrong with other frameworks, "too much code" is a decent answer.
- sandGorgon 4y agothis is so so cool! thank you for sharing this. I have been wondering something - wiring different components together and building "up" something. versus take Spring Boot and create a DSL/Lombok-like layer on top which abstracts out the "too much code" and unpleasantness. Like a Nextjs that builds on top of Reactjs. Why the first and not the second ?
- stickfigure 4y agoI'll give you my complaint with Spring: It tries to hide the libraries underneath and offer the "Spring way". But it's always a leaky abstraction, so you end up having to learn both (for example) Hibernate and how Spring interacts with Hibernate. Instead of avoiding a learning curve it just adds a second one. I greet your suggestion to add another layer of abstraction on top with great skepticism.
- sandGorgon 4y agofair point! let me give it a shot.