3 ms·

As a person who "Began" really learning rails this spring (only for 1 project, to help be the other end of the frontend/backend communications), it's definitely

by gte910h 15y ago

As a person who "Began" really learning rails this spring (only for 1 project, to help be the other end of the frontend/backend communications), it's definitely getting into non-newbie friendly territory to start using it. It's starting to have the problem of "YOU MUST UNDERSTAND ALL OF THIS" before you can deploy anything useful issue. (I don't mean all of rails, but you do need to understand a very large number of topics before you can do a real app these days). It's making other lighter weight ruby based web frameworks look appealing even at this point (as they'd still work on heroku for the most part).

jamesbritt 15y ago
There are a number of Rack-based frameworks out there, upwards of around 2 dozen, you can look at. I'm partial to Ramaze. Many of these frameworks do not come with assorted bells and whistles to handle certain tasks. You'll have to write them yourself. What this means in practice is that your learning curve involves getting more proficient with Ruby rather than getting proficient with a tool-specific API. Long-term, that leaves you better off.
- gte910h 15y ago
  I think Sinatra is one I've had tossed at me a few times as well. Do you have an opinion on that? Honestly speaking, programming language proficiency isn't really the issue anymore, Rails has a HUGE "We do it this way cause that's the way we do it" level of stuff in it to learn that isn't enforced by a complier, etc. That's the rough stuff, especially if you do 1-2 projects a year in it, its so different by the time you return. Looking at Ramaze, it reminds me of web.py
  - jamesbritt 15y ago
    I think Sinatra is one I've had tossed at me a few times as well. Do you have an opinion on that? It's not for me. It's clever, and makes certain kinds of apps easier for some people, but it doesn't buy me anything over either a straight-up Rack app or a Ramaze app.

by gte910h 15y ago

jamesbritt 15y ago

There are a number of Rack-based frameworks out there, upwards of around 2 dozen, you can look at. I'm partial to Ramaze. Many of these frameworks do not come with assorted bells and whistles to handle certain tasks. You'll have to write them yourself. What this means in practice is that your learning curve involves getting more proficient with Ruby rather than getting proficient with a tool-specific API. Long-term, that leaves you better off.

gte910h 15y ago
I think Sinatra is one I've had tossed at me a few times as well. Do you have an opinion on that? Honestly speaking, programming language proficiency isn't really the issue anymore, Rails has a HUGE "We do it this way cause that's the way we do it" level of stuff in it to learn that isn't enforced by a complier, etc. That's the rough stuff, especially if you do 1-2 projects a year in it, its so different by the time you return. Looking at Ramaze, it reminds me of web.py
- jamesbritt 15y ago
  I think Sinatra is one I've had tossed at me a few times as well. Do you have an opinion on that? It's not for me. It's clever, and makes certain kinds of apps easier for some people, but it doesn't buy me anything over either a straight-up Rack app or a Ramaze app.