4 ms·
I've always felt that having "private" fields by default (thereby suggesing it is the right way to code), making all code live inside classes, and thinking ever
by boterock 7y ago
I've always felt that having "private" fields by default (thereby suggesing it is the right way to code), making all code live inside classes, and thinking everything as an object, are dogmatic assumptions that make you write a lot of boilerplate as you move forward (getters/setters, constructors, etc...)
If you could write your functions out of any class, you get 3 lines an an indent level less, which I think reduces the cognitive load. you could change your private fields to be by convention instead of forced just by prefixing m_varName or whatever...
I dislike java because I feel the language somehow doesn't trust the developer to know well the system he is coding. It is like handing a blunt knife to a chef expecting he doesn't know how to handle it, making his work annoying, but if he has to work for more time, he can bill more hours right?