I think I saw this early on, but then forgot about it. Stumbled upon it today, and it actually looks like a cool project. Have anyone any experience of using it for a real or just a toy project?

you are viewing a single comment's thread
view the rest of the comments

[–] snaggen 3 points 7 months ago (1 children)

What I feel looks interesting with "on rails" is that you get things like database management built in, like setup, upgrades aso. Of course, this also means that it might be difficult to jump off the rails if you need that. And even if I feel like I'm not the target audience, since I prefer to pick and choose smaller libraries, I'm watching this with interest since Ruby on Rails seems to be quite popular.

[–] natecox 6 points 7 months ago (1 children)

Rails is great for starting an app, you can get something to a functional MVP state in a ridiculously small amount of time. We used to do rapid prototyping where we could be shipping it to the client in like 2-4 weeks. I haven’t found anything that comes close to this elsewhere.

But you’re right that the big trade off is jumping off is effectively impossible, because Rails is your app. Most criticism that I see (and feel is valid) is that unless you’re willing to do a whole rewrite you will be on Rails forever. I think this is a more reasonable trade off than I see represented online; “long terms Rails is a nightmare” comes up a lot and I don’t think it’s that bad.

I personally like that we’re seeing options for both strategies here popping up. More options is good for us as devs.

[–] [email protected] 1 points 7 months ago

As a non-Rails-developer running some apps based on it long-term the most annoying thing about Rails when trying to debug an issue in a code-base that isn't yours is all the auto-magic stuff where the usual way to find the function called doesn't work because it is magically auto-generated in the background somewhere out of strings concatenated together.