Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DHH answers: What makes Rails a framework worth learning in 2017?

quora.com

Post reply on HN
Print view View original

131–135 of 135 posts

Re: DHH answers: What makes Rails a framework worth learning in 2017?

#131

Post by throwanem »

deedubaya wrote: post #124
throwanem wrote: post #60

Earlier quoted context omitted.

Until a new point release comes out and everyone forgets about the one you're running. Then you get to find out how much of your code you'll need to rewrite so it'll run with the Rails chefs' wild new menu. And there's no point even trying with an app written for an earlier major version. Just give up now, because the whole ocean's been boiled and recondensed since then, and now occupies but few of the basins it once…

> Until a new point release comes out and everyone forgets about the one you're running This is definitely a pain you'll feel with rails, and any other combination of software pieces which you bring together. For what it's worth, within the last month, I've touched rails 3.2, 4.0, 4.1, 5.0, and 5.0.1 apps which are running in production. It's possible to maintain these apps on old releases, but the idea of never upgr…

It's worse in Rails because of the rate of change and the near-total lack of interest in backwards compatibility. Granted that the change in question often improves Rails' performance or stability, but that so much scope seems to go on existing for such improvements is in itself concerning, and the larger question, of whether it would be wiser to instead invest in a less volatile and more stable platform, remains valid.

Re: DHH answers: What makes Rails a framework worth learning in 2017?

#132

Post by bitwize »

kazinator wrote: post #128
bitwize wrote: post #110

Earlier quoted context omitted.

I've seen worse. A system that would load chunks of code out of MySQL and eval them in place. Magic variables with magic meanings... shudder

Sounds like the coder was might have been imitating the idea of SQL stored procedures.

Actually he was imitating Lotus Notes...

Re: DHH answers: What makes Rails a framework worth learning in 2017?

#133

Post by KurtMueller »

ooqr wrote: post #44
meesterdude wrote: post #4

This reinforces what I see a lot too - people creating yet another XYZ, but rarely I see someone go and create an integrated solution to streamline development processes or make things easier or clearer. There are a lot of vocal people who make it seem like you should be doing everything in Go or Angular or what have you, but I want nothing to do with either, and do not have problems that those are meant to solve. I…

I am a rails dev. I inherited a legacy application. The biggest problem with Ruby/Rails is that anything Ruby will allow, someone will do. Ruby is the language I learned data structures and algorithms in, built my first significant projects in. It has a generous wealth of helpful builtins. But it makes me long for strictness, static typing, a language where not just anything can completely modify any other.

I feel that ways as well... and I'm loving F# for being easy to write and read and yet giving me algebraic data types which allow me to better to model the domain I'm working in and for forcing me to explicitly demarcate what's mutable and what's not.

You should check out Scott Wlaschin's talk, Domain Modeling with F# if you get the chance. https://vimeo.com/97507575

Re: DHH answers: What makes Rails a framework worth learning in 2017?

#134

Post by Can_Not »

astrodust wrote: post #72
throwanem wrote: post #51

Earlier quoted context omitted.

Rails is omakase. Node is a grocery and a kitchen supply store. Approaching either as if it's the other is a sure recipe for regret.

Node is like walking into a Home Depot when you want a house. Technically you can build one out of the bits they can provide, but it's a ton of work. The thing is Node could offer the Rails out-of-the-box experience through a package that provided sane defaults. There's nothing preventing people from doing this but cultural resistance.

Adonis might be Rails-enough for you. https://adonisjs.com/

Re: DHH answers: What makes Rails a framework worth learning in 2017?

#135

Post by headcanon »

bigtunacan wrote: post #42
headcanon wrote: post #23

Earlier quoted context omitted.

> As to why... it's anyone's guess. I think its because recreating rails in javascript just doesn't make sense in the current ecosystem. Either you are rewriting stuff like express from scratch (and why are you doing that?), or you're building on top of those modules and adding configuration conventions and scripts, in which case, congratulations, you've just written Sails. When Rails first got started, ruby didn't h…

Personally I think Sails is pretty cool in it's own right. As far as websockets go I feel like that is one area where Sails makes things dead simple and I've not been amazed by the overcomplicated Rails 5 implementation of websockets. That said, I don't see Sails gaining a ton of traction even though it's been around for quite some time yet, and with it's security settings and beta status I don't feel great about bui…

I certainly like sails, and can't levy too much criticism against it (except its ORM left quite a bit to be desired, although I haven't looked at it recently). I'm only asserting that it will never be Rails, partially because of how and when each respective framework came to be.
Post reply on HN