5 ms·
From the link: > I was looking at Padrino recently and rather like it. It's a young framework, nowhere near as mature, but has an interesting architectural "va
by adelevie 16y ago
From the link:
> I was looking at Padrino recently and rather like it. It's a young
framework, nowhere near as mature, but has an interesting architectural
"value prop"... and at least so far I haven't gotten any STFUs from the
development team. :)
The client shouldn't care how the core team treats his/her developer. The client should only care about the product. While an insult from a core member may hurt feelings, it doesn't make ActiveRecord any less useful.
- jamesbritt 16y ago"The client should only care about the product. While an insult from a core member may hurt feelings, it doesn't make ActiveRecord any less useful." Maybe. But you know that every lib and app has bugs, so when you start looking at tools you take into account how reliable it is now, and what happens down the line as bugs or issues are uncovered. If the project members seem to have a shitty attitude about users' concerns, you should have second thoughts. Realistically you want to look at the big picture and be a bit pragmatic about these things. People should by now know what to expect from various Ruby cliques, decide if it's worth the annoyance, and act accordingly. Overall, stuff gets done in Rails, even if not on the schedule people might want. However, people should also look at the dozen or so other Ruby Web frameworks and see if their communities might not be more the kind they want to be a part of. The Nitro, and now Ramaze, community, was and is a big reason for my interest. The people and the code rocks.