2 ms·
It's primarly a matter of taste, but I suppose that if you use only libraries instead of a framework: you will end up copy/pasting the same boilerplate to tie e
by 1337shadow 6y ago
It's primarly a matter of taste, but I suppose that if you use only libraries instead of a framework: you will end up copy/pasting the same boilerplate to tie each library from one another over every project.
You could make a library that standardizes a library format and take care of that boilerplate, then you can focus on what makes your project different, but that's not very different from a framework is it ?
- mtzet 6y agoI find that this type of duplication is incidental: I happen to need to do the same thing, but if one project has special requirements the other projects don’t need to change. Hence the boilerplate is fine and doesn’t need to be dragged into a library.