News for hackers. Stuff that matters.
Re:Why I wouldn’t use Rails for a new company by LoSboccacc on Thursday September 17, 2015 @06:19PM (#10236439)
Because you have to maintain the app against known vulnerabilities. And in even a single year previous version of out app had multiple gems with vulnerabilities having to do a major version upgrade and I had to scrap the whole thing because older gems with fixes where unavailable or didn't build on modern rail/os

The whole ecosystem is frankly a mess, you need to stay bleeding edge all the time to have a chance to long term maintenance and suffer any capricious api update each of your dependency might have because staying on old release and relying on backports is not worth it.

I'm not paid to clean other people libraries. If the idea of open source is that, then no thanks. Core business is not maintenance and costs like those do kill startups.

Re:Why I wouldn’t use Rails for a new company by deedubaya on Thursday September 17, 2015 @06:38PM (#10236515)
Those aren't rails specific issues.

If you want to run on old software that you don't have to upgrade or maintain, you are going to pay for someone else to do it.

If you want your cake and to eat it too, you're unrealistic.

Re:Why I wouldn’t use Rails for a new company by mszyndel on Thursday September 17, 2015 @06:33PM (#10236496)
> you need to stay bleeding edge all the time to have a chance to long term maintenance

yeah, github is a perfect example or that, right? </irony>

Re:Why I wouldn’t use Rails for a new company by scott_karana on Thursday September 17, 2015 @06:25PM (#10236460)
If all your old gems had vulnerabilities, what makes you think bleeding edge ones didn't?

Spoiler: the difference is, the new ones' bugs just aren't widely known yet.