2 ms·
I see. So, sort of like a sculptural "chip away everything that's not an elephant" kind of approach. That makes some sense. I think the "custom generated code
by erikpukinskis 15y ago
I see. So, sort of like a sculptural "chip away everything that's not an elephant" kind of approach. That makes some sense.
I think the "custom generated code to mee your precise needs" category is exactly where I think scaffold writers are just lazy library writers. If there's a way to parameterize the scaffold experience, there's a way to create a parameterized library that "scaffolds" your code without generating a bunch of boilerplate.
On the last point: I think that makes a lot of sense, especially if you're working for clients. They want to end up with a complete, hackable site that doesn't have some weird dependency on a meta library. (like a library with meta-forms, meta-models, etc)
I guess I'm biased because I work on one big piece of software, so that kind of duplication would be heresy.
That said, if you tried to write a unified framework that let you build sites like that without a bunch of generated scaffold... you might end up building the next Rails! Isn't that where Rails came from?