3 ms·

> It is literally what fortune five hundred companies trust their fortunes with You’re overstating what “trust their fortunes with” means to a corporation. A f

> It is literally what fortune five hundred companies trust their fortunes with You’re overstating what “trust their fortunes with” means to a corporation. A framework is just technical detail. Often it’s tech debt if the framework is no longer fashionable. As has happened with J2EE. Also: robust, heh. Spring has plenty of footguns and bugs. If you’ve deployed Spring anywhere, we should count the number of CVEs in production for your code. And optimised? No. God no. For devs new to the industry seeing this: a framework isn’t a runtime and isn’t a language. Learn how to write decent code without the training wheels of a framework. Then when it’s warranted, use a framework when it fits your needs. But don’t get into a situation where you’re totally dependent on the framework. > likely dominate the market They said that about J2EE as well. Didn’t work out so well. Again, knowing good programming technique > knowing a framework and better for career growth. Specifically for Spring, its new owners Broadcom will probably look to making money off it. It’s already begun in a sense, a bunch of Fortune 500s are realising that Spring 5.x goes end of life in August 2024 (yes, this month) so it’s now time to pay Broadcom for sec fixes or upgrade to Spring 6. It doesn’t mean Spring is dead but its proponents will have to work just a bit harder to justify the cost.

karmakaze 2y ago
Wait isn't Spring Framework all under "Apache License 2.0", so anyone could fork it and use it? Why wouldn't there be a group other than Broadcom contributing updates and providing support?
- signal11 2y ago
  You can absolutely try. There are companies which provide support for out of support frameworks like Angular 1. In reality there’s not enough Spring committers who don’t work for Broadcom for it to happen widely. (Also Broadcom has other options, eg follow Elastic and Cockroach Labs and change license.) If you’re a senior dev, you need to be commercially astute — like finance folk can read balance sheets, you should be able to glean commercial implications from a project’s commit history. PS. I’m a big fan of ensuring engineers get paid. If you actively choose to use Spring, buy a darn support contract and support its development. Given how many of you are on Spring 5.x or earlier even now, you’ll have to do so anyway if you want sec fixes. It’s a bit late to be looking for options in the short to medium term.
randmeerkat 2y ago
> For devs new to the industry seeing this: a framework isn’t a runtime and isn’t a language. Learn how to write decent code without the training wheels of a framework. Then when it’s warranted, use a framework when it fits your needs. But don’t get into a situation where you’re totally dependent on the framework. For devs new to the industry seeing this: Master Spring, Java, and the JVM, then coast and have fun, while counting your ever growing bank account. Don’t get caught in the vicious cycle of endless hype, “up and coming” languages, microservices, or K8s. Fads, like skinny jeans and man buns, will eventually just disappear back into the void that they came from, but at the end of the day, you’ll have a great career, work life balance, and no problem finding a job. You’re welcome.

karmakaze 2y ago

Wait isn't Spring Framework all under "Apache License 2.0", so anyone could fork it and use it? Why wouldn't there be a group other than Broadcom contributing updates and providing support?

signal11 2y ago
You can absolutely try. There are companies which provide support for out of support frameworks like Angular 1. In reality there’s not enough Spring committers who don’t work for Broadcom for it to happen widely. (Also Broadcom has other options, eg follow Elastic and Cockroach Labs and change license.) If you’re a senior dev, you need to be commercially astute — like finance folk can read balance sheets, you should be able to glean commercial implications from a project’s commit history. PS. I’m a big fan of ensuring engineers get paid. If you actively choose to use Spring, buy a darn support contract and support its development. Given how many of you are on Spring 5.x or earlier even now, you’ll have to do so anyway if you want sec fixes. It’s a bit late to be looking for options in the short to medium term.

randmeerkat 2y ago

> For devs new to the industry seeing this: a framework isn’t a runtime and isn’t a language. Learn how to write decent code without the training wheels of a framework. Then when it’s warranted, use a framework when it fits your needs. But don’t get into a situation where you’re totally dependent on the framework. For devs new to the industry seeing this: Master Spring, Java, and the JVM, then coast and have fun, while counting your ever growing bank account. Don’t get caught in the vicious cycle of endless hype, “up and coming” languages, microservices, or K8s. Fads, like skinny jeans and man buns, will eventually just disappear back into the void that they came from, but at the end of the day, you’ll have a great career, work life balance, and no problem finding a job. You’re welcome.