3 ms·
where a bunch of devs who've done exactly one project in one framework sit down and figure out what their Dream System would look like, and end up reinventing e
by statictype 16y ago
where a bunch of devs who've done exactly one project in one framework sit down and figure out what their Dream System would look like, and end up reinventing either Classic ASP or Cold Fusion, but in a comically terrible way.
We have our own webframework that grew over time and I don't feel bad about it. It's custom-built for our apps and so, it does exactly what we need and abstracts away the exact feature set we need. It's not more powerful than any existing framework and is certainly not for everyone but it suites our needs perfectly.
I don't see writing custom frameworks or templating systems as any different from writing a DSL.
- jasonkester 16y agoWe have our own webframework that grew over time and I don't feel bad about it. Nor should you. You invested some time and put together something that exactly fits your needs. Chances are you're moving faster on it than some random new team using Rails, because you're so familiar with it and starting a new project involves simply copying large chunks out of a half dozen previous jobs and taping them together. The key is that you didn't try to build your thing out into a platform and release it as open source.