4 ms·
> but you're making a really good problem specific framework that exactly fits the thing you're building. Except when you don't. A lot of people, when they rea
by Cthulhu_ 10y ago
> but you're making a really good problem specific framework that exactly fits the thing you're building.
Except when you don't. A lot of people, when they realize they're building a framework, start over-engineering (YAGNI). Another issue is that they, for example, build a template renderer but miss a lot of edge cases, opening their application up for script injection and other such nasty things.
Ten or so years ago, PHP had the same disease - people thinking they're hot shit, building their own frameworks, writing wrong tutorials on how to e.g. connect to a database because they thought they knew how that worked. This resulted in a huge amount of SQL injection issues, millions if not billions of hacked accounts, and billions in damages.
TL;DR don't write your own framework, please.
- geebee 10y agoId agree, but add my own plea: please dont write an spa if you dont need one. Yes I left that a bit ambiguous, but it is harder to manage and work witha rails and ember app than a reg'lear ol rails app. Thats cool if are genuinely getting something out of it. "Ember experiece" on your resume doesnt count. Except that it does, bummed, but i do understand.
- deleted 10y ago[deleted]
- dreistdreist 10y agoPHP did not have a useful package manager back then. It has now. Custom solution built on top of stable components > general purpose framework