←back to thread

74 points holmofyHu | 1 comments | | HN request time: 0s | source
Show context
ffsm8 ◴[] No.41276279[source]
this new project, spring-rs is a wrapper for various other projects, gluing them together. (and thats totally fine!)

But naming it after the Spring Framework might be slightly exaggerating its ambition.

Even its homepage uses marketing thats not really on point for Spring i think?

i.e. Lightweight: The core code of spring-rs does not exceed 5,000 lines

I dont think anyone can honestly call Spring with its 8 million Lines of Java Code ... lightweight?

replies(5): >>41276354 #>>41276588 #>>41277190 #>>41277291 #>>41277513 #
karmakaze ◴[] No.41277190[source]
This is like the renaming to JavaScript to ride the coattails of Java.

I suppose Spring is still a popular, widely known framework. Other than desired popularity, there's no resemblance and is antithetical. Anything I see associating with Spring, I would assume to be outdated and inefficient.

replies(1): >>41278735 #
randmeerkat ◴[] No.41278735[source]
> I suppose Spring is still a popular, widely known framework. Other than desired popularity, there's no resemblance and is antithetical. Anything I see associating with Spring, I would assume to be outdated and inefficient.

Spring is a battle tested, robust, optimized framework, that has scaled the largest brands in the world. It is literally what fortune five hundred companies trust their fortunes with. Spring is far from being outdated or inefficient, and will likely continue to dominate the market for years if not decades to come.

replies(3): >>41278817 #>>41278977 #>>41282654 #
signal11 ◴[] No.41282654{3}[source]
> 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.

replies(2): >>41282885 #>>41286744 #
1. randmeerkat ◴[] No.41286744{4}[source]
> 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.