3 ms·
It's easy to forget that most people are just starting out (by definition; most people quit or stop), most people just want to make something, and for that, the
by jtth 9y ago
It's easy to forget that most people are just starting out (by definition; most people quit or stop), most people just want to make something, and for that, there's nothing better than rails. I'm in this boat. I just want this thing I thought of and designed to be real, and now after doing Hardtl's tutorial and reading/coding for two days, my thing's basic MVP is real. I've never really done a web app before except for some experiments in Clojure. But I'm not programming it in clojure, a language I like better than Ruby and know a lot better than Ruby, because there's no opinionated framework, there are no models, there's nothing even close to rails and activemodel and all that. I just want to make the thing. That's what most infant-sized things are: babies. And to make the baby you make it in rails and deploy it on heroku. If it sticks, remake it in something else if it really does have scaling problems. But most things don't succeed, and if they do, they probably won't succeed at the scale where it matters at all that they were written in rails. (This is a statistical argument.)
- erokar 9y agoCompletely agree. I've tried Java/Spring, Python/Django/Flask, JS/Express/Meteor, Ruby/Rails/Sinatra and Elixir/Phoenix. The only thing I've seen that might rival Rails in productivity is Meteor, but that is relevant mostly if you absolutely need an SPA or some kind of realtime support. Apart from that Rails is the most productive framework, and it's perfect for a solo developer or a small team -- and that goes for both novice and experienced developers. I'm currently looking into Elixir/Phoenix –– and I think it has the potential to become as productive as Rails, but so far the ecosystem is much smaller.
- jtth 9y agoYeah. Perhaps this is a good metric of ecosystem and developer productivity, and would make for a good extensive blog post: how long does it take to implement users, with password resets and security and everything being just so? With rails, it's, what, an early afternoon with devise and some associated gems? What else has that? Again, not perfect, not tailored, but most people don't wear tailored clothes, and don't need tailored clothes, either. I'll be happy if I get one paying user in a few months when I'm ready to show this thing off. (Edit: I just watched a meteor tutorial doing exactly this and now I feel a pull to remake everything. Jeez.)