An Opinionated Guide to Modern Java Development, Part 1

#1

Post by pron » Thu, May 01, 2014, 3:26 PM UTC

An Opinionated Guide to Modern Java Development, Part 1
blog.paralleluniverse.co

Re: An Opinionated Guide to Modern Java Development, Part 1

#2

Post by netcraft » Thu, May 01, 2014, 3:46 PM UTC

What about dependency injection in modern java - is Guice or spring still the de facto standard?

Re: An Opinionated Guide to Modern Java Development, Part 1

#3

Post by exabrial » Thu, May 01, 2014, 3:56 PM UTC

netcraft wrote: post #2

What about dependency injection in modern java - is Guice or spring still the de facto standard?

I agree... can't live without Dependency Injection (one of the reasons I refuse to move off of Java). I've been using CDI and TomEE for small simple stuff (it just works).

Can't stand Spring Framework anymore. It set out to replace the bloatware of Java EE 1.5 but it ended up becoming what it was meant to replace.

Re: An Opinionated Guide to Modern Java Development, Part 1

#4

Post by veeti » Thu, May 01, 2014, 3:59 PM UTC

netcraft wrote: post #2

What about dependency injection in modern java - is Guice or spring still the de facto standard?

I only do Java on Android, but Dagger (https://square.github.io/dagger/) might be a nice lightweight alternative.

Re: An Opinionated Guide to Modern Java Development, Part 1

#5

Post by pron » Thu, May 01, 2014, 3:59 PM UTC

netcraft wrote: post #2

What about dependency injection in modern java - is Guice or spring still the de facto standard?

I'll address that in part 3. Basically jsr330 is a good standard, and it's implemented by Guice, Dagger and Spring

Re: An Opinionated Guide to Modern Java Development, Part 1

#6

Post by bsaul » Thu, May 01, 2014, 4:00 PM UTC

I'm back to java after having an unsatisfying experience 2 years ago with Spring MVC, (this time i use the "play framework"), and it seems to confirm my intuition that the language itself is really just fine. The problem lies more in bloated frameworks and corporate culture where everything needs to be standardized, regulated, and the purpose of a mandatory non-free training session.

Add to that the fact that every single topic is covered by at least 3 or 4 libraries, and you get a more complete view of the situation.

Re: An Opinionated Guide to Modern Java Development, Part 1

#7

Post by jmgtan » Thu, May 01, 2014, 4:02 PM UTC

exabrial wrote: post #3

netcraft wrote: post #2

What about dependency injection in modern java - is Guice or spring still the de facto standard?

I agree... can't live without Dependency Injection (one of the reasons I refuse to move off of Java). I've been using CDI and TomEE for small simple stuff (it just works). Can't stand Spring Framework anymore. It set out to replace the bloatware of Java EE 1.5 but it ended up becoming what it was meant to replace.

You should give the latest version a try. Spring implemented JavaConfig, which allows you to avoid XML altogether. Coupled with the ComponentScan annotation, it can't get any simpler.

Re: An Opinionated Guide to Modern Java Development, Part 1

#8

Post by monkmartinez » Thu, May 01, 2014, 4:04 PM UTC

I have come full circle in a way. I started learning Java in school and built a few, small things for Android and the desktop. Then I was "all like;" I am going to learn the hotness which was(is?) Node. Node is what it is and I didn't really care for it. Then I moved on to Python and I really like it. Python is awesome for many, many things but GUI applications are not one of them. I have since returned to some Android development and I am diving into a CRUD web app in Java. Simple stuff, but it needs to be fast.

Looking forward to part 2 and more!

Re: An Opinionated Guide to Modern Java Development, Part 1

#9

Post by bsaul » Thu, May 01, 2014, 4:04 PM UTC

exabrial wrote: post #3

netcraft wrote: post #2

What about dependency injection in modern java - is Guice or spring still the de facto standard?

I agree... can't live without Dependency Injection (one of the reasons I refuse to move off of Java). I've been using CDI and TomEE for small simple stuff (it just works). Can't stand Spring Framework anymore. It set out to replace the bloatware of Java EE 1.5 but it ended up becoming what it was meant to replace.

Genuinely curious : i've been playing with dependency injection, and really never got to understand the true use of it.

I mean, what's the point of being able to replace an implementation outside the source code itself ? You'd still have to extensively test the thing and recompile it...

Is there more to it than just being able to replace a class by its mock up, for unit testing ?

Re: An Opinionated Guide to Modern Java Development, Part 1

#10

Post by ryanobjc » Thu, May 01, 2014, 4:08 PM UTC

A lot of people love to hate on Java, but it's a surprisingly dynamic language and there is a ton of great testing, networking, and many other libraries available.

One of the things I appreciate about Java is the ability to take large teams and just have their stuff work together, without having unhuman discipline around super subtle rules (eg: C++)

Also, IntelliJ is a must have!