4 ms·
That is one reason to choose a framework instead of building from scratch, so you don't have to make decisions like "Where do I put Y". The most import value a
by ehnto 5y ago
That is one reason to choose a framework instead of building from scratch, so you don't have to make decisions like "Where do I put Y". The most import value a framework provides isn't in the way it functions, but that it is a collection of idioms, decisions and conventions that everyone has to use.
It also means I don't have to worry about where Dev X put thing Y, because I know where to look for it already.
That's what software patterns are good for as well, a shared set of idioms so you don't have to invent new approaches. I think that's important in a professional environment but less so in a personal one. For personal projects I just do whatever is fun.
- zzbzq 5y agoBut the whole problem is frameworks always decide against code colocation, and also they don't tell you what to do with all the functions that don't fit their directory scheme. People who don't use a framework will naturally tend toward fewer subdirectories and code colocation just because, e.g., there's no reason to elevate the importance of a models/views/controllers pattern.