3 ms·
> The distinction is that you're making a crappy general purpose framework, but you're making a really good problem specific framework that exactly fits the thi
by matwood 10y ago
> The distinction is that you're making a crappy general purpose framework, but you're making a really good problem specific framework that exactly fits the thing you're building.
But are you really? I'm not against rolling my own framework, but there needs to be very specifics reasons. The are so many reasons why using a popular framework is a good thing, that there have to be some very good reasons to roll my own.
> Your thing is only for You to do Your Thing, so it can be much lighter and to the point.
Unfortunately every time I have seen this reasoning used, it falls apart after starting. Rarely is software static, and instead it continues to grow. The custom framework may be lighter and to the point when you start and 6 months from now it is a bad copy of a common framework you could have just used off the shelf.