3 ms·
Scaffolding gets wrong when it tries to write non-obvious code instead of automating writing obvious repetitive boilerplate one. I think things like those http
by drdaeman 13y ago
Scaffolding gets wrong when it tries to write non-obvious code instead of automating writing obvious repetitive boilerplate one.
I think things like those https://github.com/rayokota/generator-angular-scotty/blob/master/app/templates/src/_Main.hs https://github.com/rayokota/generator-angular-scotty/blob/ma... should be put into a well-documented library for others to export and use. This is a straightforward approach to make things one writes available for everybody else.
And then, I guess, scaffolding with no-brainer one-liners like `put "..." $ updateModel ...` is fine by me.
- chongli 13y agowrite non-obvious code instead of automating writing obvious repetitive boilerplate one. That's fine and all but Haskell's a powerful enough language to abstract away most boilerplate. What little remains can be taken care of with the TemplateHaskell extension. For a nice example of a library in Haskell that requires almost no boilerplate at all, check out XMonad. All of what you'd expect to be boilerplate is packed into a variable called defaultConfig.