francesco-strazzullo
commented
6 years ago For the first point, you can read the discussion in this closed issue #5.
"Having clear opportunities and constraints of each framework it will be easier make the right choice, also it will be clear when you don't need a framework"
Apart from the syntax error, "it will be easier to make the right choice", I try to explain better what we mean. This phrase is connected to #21, in order to choose a good tool you should understand clearly what opportunities and constraints they have and how well these opportunities are adaptable to your context.
"Frameworkless means, however, don't assume that in the software I'm writing I can afford to delegate this responsibility and depends on other (library for example) to solve a specific problem. Or worse: don't reinvent the wheel and bind hand and foot to a whole framework even if I don't really need"
The point here is that you should remember that writing a software without a framework it's possible. Sometimes devs use the "usual" framework also if they don't really need that. The focus here is on "delegation". If I decide that I want to delegate the solution of a problem to a framework/library, I sacrifice control because I depend on that library. What we are trying to state here is to think about the loss of control when choosing a tool.
"But it means taking a conscious decision about if we want to get help to do our own job from tools already exist and in what way"
Here what we mean is that we don't say that we need to write without frameworks every single time but you should decide in you need help for that project and how to use that tool.
@GeoDoo It's more clear now? How can we write this in a better way?
GeoDoo
The syntax above does not convey a clear message. I cannot understand exactly what you are saying.
Lastly, in the section What Frameworkless Movement IS NOT, the last two arguments are about what it DOES mean, so it is kinda confusing too. Maybe they should move to the purpose section??
:)