3 ms·
I have to agree. Our stack is currently Node.js. After all the abstractions that we've added to make it work for us, it's basically Django now. We could have sa
by SaltyBackendGuy 8y ago
I have to agree. Our stack is currently Node.js. After all the abstractions that we've added to make it work for us, it's basically Django now. We could have saved a lot of time just going with Django first. (Or Rails if that's your flavor)
- rbanffy 8y agoI had the same experience building up from Flask. By the time we finished, we had a more or less complete clone of Django, built with a unique combination of various tools that more or less worked together.
- michaelbuckbee 8y agoThis is what inevitably happens to me as well. This past week I wrote what was literally a single file ruby script to do some automated QA testing for a website migration, since that day I've been requested to: - make it a web app so the team can run tests - add some charts - keep it secure - umpteen new semi related features Would have been easier to just start at "rails new".