3 ms·
I was hoping to see some examples here. My understanding on why Rails is falling a bit out of favor is that it presumes a webserver? You can get a lot of mile
by taeric 3y ago
I was hoping to see some examples here.
My understanding on why Rails is falling a bit out of favor is that it presumes a webserver? You can get a lot of mileage with a static asset based frontend.
- mindaslab 3y agoOOP tends to fail when we cross 0.4 million lines of code.
- taeric 3y agoFeels like a non-sequitur? Most "react" code doesn't go for OO stuff. Does it? I suppose the same problem largely lands for "components." Especially as you get related components?
- clivestaples 3y agoI think you're right. But for projects needing a database, I can't use anything but Rails. I tried Remix/Next because I like them but it was just taking me too long. Maybe I'm at the point in my life where I can't learn as quickly as I used to or something, but I don't understand how Rails is not getting _more_ popular with HTMX (and Hotwire).
- traverseda 3y agoWhat projects are people working on that don't need a database?
- winrid 3y agoBoth Rails and Django. Everything else feels pretty unproductive with a relational DB. Rust with sqlx is pretty nice and you get a very typesafe system but very slow to write.
- taeric 3y agoFor single person projects, this makes a ton of sense. As you start wanting to divorce the iteration of one from the other, things do start to look a little different. And if you have the constraint of "no webserver," many static site strategies come into play.