elomatreb, do you think an ifelse would truly be better? I thought they were interchangeable for the most part and it was a matter of preference. Also, when you say "refactor the ranges into clearly named methods" can you give me an example?
I think I understand what you mean, but this only needs to happen once, normally you break things out into methods to write less code (by not re-writing the same functions over and over through your code) but in this case it's going to actually add code and spread it out more, seems counter-intuative
I skip rails altogether, seems like unless you're building a very basic DB based site, it's not as useful as it first appeared.
I write my backend in ruby and have a frontend guy, then just communicate between the two
I can create a site like twitter or netflix and host database information all day with it, but if I want a site with a roulette wheel on one page and something else on the next, seems to get pretty difficult from there
easy for the front end guy, easy for the backend guy, and your own custom language between the two of you for your socket reads/writes