Earlier quoted context omitted.
> You get ORM, a web framework, dependency injection, messaging But you can get all that stuff without Spring, too. And Spring adds another layer in between you and the ORM, the web framework and the messaging framework - a layer that's heavily reflection-based and makes a ton of undocumented assumptions about how things are set up and throws cryptic error messages when those assumptions are violated.
You certainly can, but it is like a mechanic buying sets of tools from many manufacturers. The Spring framework modules share a consistency of conventions and documentation that is itself valuable. Like any opinionated framework, it's going to make assumptions that can cause headaches, but it's mature enough that most issues I run into are a Stack Overflow away.
AngularJS support is ending, and developers can migrate to Angular
51–54 of 54 posts
Re: AngularJS support is ending, and developers can migrate to Angular
#52Aren't these too different to just "migrate"? Isn't it going to be more of a rewrite?
The initial rollout of angular 2 vs angularJS was a confusing shit show (and will bite anyone getting into angular brand new as they hit constant google results for one angular when they want the other), but the upgradability is a case study in how to do it right in my opinion. They really made it accessible for anyone to move an app over.
Re: AngularJS support is ending, and developers can migrate to Angular
#53Earlier quoted context omitted.
I’ve seen gwt. It smells bad, but it seems supported still. Can you elaborate on your comment so I have conversation points next time I deal with that team?
Google hived off support to an open source foundation about a decade ago. It wasn’t well supported even before that for several years (I remember at one point they went through and closed all the open issues as Assumed Stale). They also loved to pivot best practices every year and stop developing the code that supported last year’s best practices.
Re: AngularJS support is ending, and developers can migrate to Angular
#54I was asked to use angular in a java job. I was going crazy with all the files you need to have for a small project. It's like all the horrible sides of OOP and abstraction, but on steroids.
At first glance it seems "complete", but once you start building there's just so many insane edge cases that don't work well or have bugs. I also think that "integrating" RxJS was a mistake, while I get it and it's nice, it's imho too low level of an abstraction if you have many people that don't necessarily want to learn all the details (easy to shoot yourself in the foot with it), too different from anything else in JS, and too poorly integrated into angular.
And also the verbosity of everything.. was too much for me.