3 ms·
# You’re not building atop an open-source framework # You’re writing your own framework upon which to build # You’re not using an ORM layer # You’re writing
by run4yourlives 18y ago
# You’re not building atop an open-source framework
# You’re writing your own framework upon which to build
# You’re not using an ORM layer
# You’re writing your own ORM layer
I'm glad DHH and the boys over at django did it wrong, to be honest.
- senorprogrammer 18y agoAs am I, since I use Rails every day. However the number of DHHs and Ezras in the world vs. the number of us regular ol' web developers is quite small. There's a reason the rest of us should take advantage of the labours of the few rather than attempting to duplicate them.
- run4yourlives 18y agoDHH, JKM, and AH were a "regular ol' developers" until after they built rails and django. They're smart cookies, and but so are many web devs. While I agree that we should benefit from their labours, if there are times when we are confronted with the problems they had, we should be as bold as they were.
- briancooley 18y agoAnyone who should be as bold wouldn't heed that advice anyway.
- senorprogrammer 18y agoCetainly, and if you're setting out to build a framework then by all means build a framework. Or if you're setting out to improve a library then by all means, improve the library. But if you're setting to build a web app chances are it's folly to build your own "framework" and ORM and libraries first (note for the absolutists in the crowd: that is purposely _not_ an absolute statement; we can all come up with suitably contrarian one-off edge cases).