21–30 of 41 posts
Killer feature: you can use every symfony component in your own app without the framework if you want (console, http router, service container, templating, etc.)
I'd say rails because the nodejs + PHP codebases I've seen aged poorly, but the rails one are still clean. The problem with node is that things move too fast. What was beautiful in JS 4 years ago now looks like legacy mainframe fortran. Laravel (a popular php framework) is nice at one point in time, but even 0.x.0 migrations will break you application and force you to work for hours...
Same answer as the many years before: Rails, Django, or .NET. Anything else and you're making serious tradeoffs on mindshare, features, or something else. Of those 3, I know Rails has good realtime support via ActionCable.
I like Rails, but calling ActionCable good realtime support is being a bit generous, no? I was under the impression that scaling ActionCable beyond 1k/users per server was pretty difficult.
As a bonus it has a good community and is in my opinion a pleasure to work with. I've released a couple production projects using it and am currently building my third. Ive also found from my own experience and watching a new team pick it up that the learning curve is fairly small.
Same answer as the many years before: Rails, Django, or .NET. Anything else and you're making serious tradeoffs on mindshare, features, or something else. Of those 3, I know Rails has good realtime support via ActionCable.
I like Rails, but calling ActionCable good realtime support is being a bit generous, no? I was under the impression that scaling ActionCable beyond 1k/users per server was pretty difficult.
Disclaimer: I work for skygear (it's a opensource project)