3 ms·
The code for the server is different from the code for the frontend, even if they're in the same language. You're trying to do vastly different things. Front en
by toasterlovin 8y ago
The code for the server is different from the code for the frontend, even if they're in the same language. You're trying to do vastly different things. Front end is about user interface. Server is about controlling access to and storing data. IMO, you should use the best tool for each. Rails has been encapsulating the best practices around server side web apps for 15 years. The ecosystem is unbelievably mature and productive, regardless of whether you want to do a traditional server rendered app, or a JSON API for a JS, iOS, or Android client.
- vram22 8y ago>Rails has been encapsulating the best practices around server side web apps for 15 years. Not to be pedantic, but I worked on Rails projects in 2006 and 2007, and had probably heard of it just a bit before that. This was during the initial Web 2 boom. I would not have thought that Rails was created much earlier than that, since I usually keep some track of at least major tech developments (although could be wrong, of course - I could have missed reading about it when it was created, or only first read about it after it became a bit popular). So anyway, I googled, and the Wikipedia article for Rails says: >Initial release: 13 December 2005; 12 years ago[1] Haven't used it lately, but I do keep reading that it is very mature and productive, as you say.
- toasterlovin 8y agoAh, sorry. I was thinking 2003 instead of 2005. But anyway. A long time.