4 ms·
I feel this. The other day I decided to just use Rails for one of these personal projects that I’ve been over-engineering for a while and it’s making progress.
by brightball 4y ago
I feel this. The other day I decided to just use Rails for one of these personal projects that I’ve been over-engineering for a while and it’s making progress.
Completely forgot how fast Rails makes everything. Based on the experience I’m probably going to force myself to just use Rails for any personal stuff now and figure if any of them actually take off I’ll rebuild if I need to.
- Ziggy_Zaggy 4y agoThis. Find a tech (NOT the fotm shenanigans) that will help you get a product up and running. Then you can always go back and swap out parts as needed. Try not to be influenced by the "omg, that tech is SOOO old!!!" crowd.
- deleted 4y ago[deleted]
- svnpenn 4y agothis is the exact opposite of the point the comment you replied to is making. Rails is not simple. we are talking about SIMPLE, like CGI. Rails is a classic example of a slow bloated framework.
- brightball 4y agoRails makes a lot of very complicated things, very simple. Doing what I'm trying to do with CGI would be a huge headache by comparison. When I said "how fast rails makes things" I meant from a standpoint of productivity.
- qbasic_forever 4y agoRails will be significantly faster than a CGI script that spawns a whole new process, starts up your script interpreter, etc. with every single web request.