A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
Discussing AI software development, and showing off what we're building.
Movie and TV enthusiasm, criticism and everything in-between.
A general discussion space for the Forem community. If it doesn't have a home elsewhere, it belongs here
Memes and software development shitposting
Web design, graphic design and everything in-between
A community of golfers and golfing enthusiasts
Your central hub for all things security. From ethical hacking and CTFs to GRC and career development, for beginners and pros alike
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
A place for parents to the share the joys, challenges, and wisdom that come from raising kids. We're here for them and for each other.
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
I’ve been working on a system built with Java Spring for the past 2 years
Stick to what you know. Use Java Spring.
I say this as someone who does not like to touch Java and uses Rails for a living.
The no.1 thing that will kill your project is not language/framework slowness, but messing around with tools instead of shipping software.
Hi Hrishi,
This is a side project that I work on my free time. So, I have the time to choose, try and learn the most adequate language for my project. :)
But yeah, you are right, if a project need to be shipped in a short time, I would rather use Java Spring to avoid messing around with tools !
Thanks for your reply !
Ah I see. If you want to explore, then go wild! I'd say try Node as well as Rails.
Basically you recommend the "when you have a hammer everything looks like a nail". Not a good approach for professionals.
Anyway Java can do web services, but shouldn't.
Or maybe because both Spring and RoR are swiss knifes, not hammers. Both perfectly valid for the task.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I’ve been working on a system built with Java Spring for the past 2 years
Stick to what you know. Use Java Spring.
I say this as someone who does not like to touch Java and uses Rails for a living.
The no.1 thing that will kill your project is not language/framework slowness, but messing around with tools instead of shipping software.
Hi Hrishi,
This is a side project that I work on my free time. So, I have the time to choose, try and learn the most adequate language for my project. :)
But yeah, you are right, if a project need to be shipped in a short time, I would rather use Java Spring to avoid messing around with tools !
Thanks for your reply !
Ah I see. If you want to explore, then go wild! I'd say try Node as well as Rails.
Basically you recommend the "when you have a hammer everything looks like a nail". Not a good approach for professionals.
Anyway Java can do web services, but shouldn't.
Or maybe because both Spring and RoR are swiss knifes, not hammers. Both perfectly valid for the task.