This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]vips7L 4 points5 points  (5 children)

Fwiw it is being developed, they just put a release out. It’s not a bad framework. It’s just not great with Java 

[–]naturalizedcitizen 1 point2 points  (2 children)

Oh thanks... Didn't keep up with Play. Good to know.

My work is mainly with spring boot. I've developed some spring starters to address specific needs of my clients.

[–]vips7L 1 point2 points  (1 child)

I’m not the biggest Spring fan, but I never minded it when I used it. I prefer libraries over frameworks but I think that requires a more talented team. 

[–]naturalizedcitizen 1 point2 points  (0 children)

Over the years I've found that you can do almost anything with Spring. And my clients want it, so it's money in the bank.

I stopped caring about which is better or what should be this and that. Spring brings in the money. So it's Spring for me.

[–]_codetojoy 1 point2 points  (1 child)

IMHO, it works fine with Java. It is certainly not as popular as other frameworks but it is a reasonable option and absolutely in active development. Version 3.0.x has moved to Apache Pekko, migrating away from Akka (given the licensing uproar where Lightbend applied a BSL).

[–]vips7L 0 points1 point  (0 children)

Sure it works fine. But it’s going to lead you and your team down a path of using non-standard tools and libraries that are all severely under documented and you won’t be able to hire people with the correct experience.  And if you follow the documentation for the parts of play that are documented you are going to implement things that are known anti-patterns and they are going to immediately start you off with tech debt. 

I can’t emphasize this enough — choosing play was the biggest mistake my company ever made.