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

Ruby Web Dev The Other Way

rwdtow.stdout.in

Post reply on HN
Print view View original

61–65 of 65 posts

Re: Ruby Web Dev The Other Way

#61

Post by qwertyuiop924 »

twblalock wrote: post #46
qwertyuiop924 wrote: post #40

Earlier quoted context omitted.

Okay, YES, Rails had docs, but that's the attitude I see: use this, do this, put your code here, we know best. The docs do not ENCOURAGE understanding of how Rails works, or why it is the way it is.

Read the code, then. The docs are for people who want to get stuff up and running. The code itself is what you should read when you want to understand how anything really works.

I shouldn't have to read the code to be able to basically reason about what my app is doing. I don't necessarily want to know EVERYTHING, but I want to know the basics of what's going on.

Re: Ruby Web Dev The Other Way

#62

Post by qwertyuiop924 »

rimantas wrote: post #54
qwertyuiop924 wrote: post #34

The first few sentences of this article sold me. Because it describes to me exactly why I hate Rails, and Ember, and any other framework with a similar model. I hate Rails because Rails is Magic. And not the good (well, as good as magic can be), 0x5f3759df kind of magic either. The kind of magic where you're given some functions to call, and some places to put your code, and if you ask why, you are told that you don'…

There is no magic in Rails if you at least give some effort to understand how things work. But everyone is free to invent their own incomplete and flawed versions which has benefit that you know the magic behind your framework. Alas, no one else does.

Yes, they do. And the difference is that it takes FAR more work to understand what Rails is doing than, say, Flask. Part of it is that Rails hides things from you. Part of it is that Rails is simply more complex. all of it makes it harder to reason about Rails.

Re: Ruby Web Dev The Other Way

#63

Post by duai »

rimantas wrote: post #53
soumyaray wrote: post #48

Earlier quoted context omitted.

I didn't like the magic of Rails either, but didn't grok Python :( I'm much happier using Ruby + Sinatra + Sequel/ROM + dry-rb I do admit that Rails devs develop considerably faster than me. But I get a feeling the majority of them can't make much more than a single machine monolith. Rails has a way of narrowing many people's technical curiosities. But it probably behooves both sides to learn more about each other.

> Rails has a way of narrowing many people's technical > curiosities. That's, let's say, very odd statement. Especially keeping in mind how many frameworks in other languages were inspired by RoR.

Well, yeah. People move to other languages and then build a RoR-inspired framework, instead of trying other alternatives.

Re: Ruby Web Dev The Other Way

#64

Post by MrBra »

Independently from people preference in working with this or the Rails approach, what is nice noticing is how the Ruby community is putting a lot of effort in creating alternatives to Rails.

Re: Ruby Web Dev The Other Way

#65

Post by heidar »

iJackUA wrote: post #31
acangiano wrote: post #4

Yes, you shouldn't do Ruby development on Windows if at all possible. But is there any reason why OS X is not mentioned in the Linux section? It is after all what many Ruby developers use.

Linux is mentioned because it is a common server OS and Linux knowledge is the most helpful for web dev. OSX do not add any extra value to this aspect of knowledge (despite I do use OSX as desktop OS).

It does if you use FreeBSD for your servers.
Post reply on HN