Re:VMware Acquires Carbon Black for $2.1B and Pivotal for $2.7B
by mustardo on Friday August 23, 2019 @03:48AM
(#20775343)
Been a happy user of dropwizard, what spring boot was "inspired" by, hookup guice and no spring magic classpath scanning to be seen
https://www.dropwizard.io/1.3.14/docs/getting-started.html#g...
Re:VMware Acquires Carbon Black for $2.1B and Pivotal for $2.7B
by jacques_chester on Friday August 23, 2019 @10:34AM
(#20778038)
I've heard two stories about the origins of Spring Boot, one of which included Ruby on Rails. I don't remember the other being Dropwizard, so I guess now I've heard three stories, only two of them from Spring contributors.
"Magic classpath scanning", also known as "classpath scanning", comes with leveled POMs, which is a massive sanity-preserver.
Re:VMware Acquires Carbon Black for $2.1B and Pivotal for $2.7B
by readme3 on Friday August 23, 2019 @01:07AM
(#20774657)
Could not agree more. I think , spring boot + spring cloud is extremely popular in the services (should i say microservices world).
Not to say , there is a changing world. Frameworks like Quarkus , Micronaut , Javalin are changing these status quos (Reactive + Cloud native + First class Kubernetes / FaaS support + Being lean). What remains to be seen though is how is Spring able to adapt and change to these. I dont know how Webflux stands up to these , but sure is interesting times ahead!
Re:VMware Acquires Carbon Black for $2.1B and Pivotal for $2.7B
by mavelikara on Friday August 23, 2019 @02:50AM
(#20775059)
Rails, from what I remember, has a strong my-way-or-the-highway attitude. It has many strengths, but deviating from the happy path isn't it's strength. It's creator claimed it was Omakase. [1]
Re:VMware Acquires Carbon Black for $2.1B and Pivotal for $2.7B
by wpietri on Friday August 23, 2019 @02:52PM
(#20781157)
I guess I mean the phrase a little differently here. Rails does have a particular envelope that they support, but it is also pretty open to extensions. More importantly, if you do something slightly different, you do not end up having to debug reams of dubious, poorly tested code just to figure out how to get your nominally reasonable change to work. I spent a huge amount of time trying to figure out whether the change I really needed to make was in some XML file, some class annotation, or some custom code.
But in my experience it's still an enterprise-grade Frankenstein's Monster, and the developer experience is pretty bad compared with other frameworks I've used. If I was doing something on the happy path, it mostly worked. But the moment I tried to do something slightly different than they expected, I was 20 frames deep into Spring stack traces trying to puzzle out poorly written Spring code. I've done a lot of Java, so I could eventually emerge triumphant. But it was a giant time suck. Looking back on the project, we estimated we could have done it in half the time using something like Rails or Flask.