3 ms·
Same here, as a security consultant reading Golang is always a pleasure. I'm pretty sure that the strongest codebases I've seen were in Golang just because of h
by baby 8y ago
Same here, as a security consultant reading Golang is always a pleasure. I'm pretty sure that the strongest codebases I've seen were in Golang just because of how easy it is for everyone to read the code and actually spend time looking for logic bugs instead of trying to understand what is happening.
Developers love to be able to write their magical code and their clever abstractions and often forget that their code is paying the price by becoming less clear and less readable. From a security perspective that's a huge loss.
I know that people with the right security mindset will do the right thing, and have more code where it improves clarity, or have slower code when it makes it easier to understand what is being done. But unfortunately that's a tiny minority of developers.
- zoul 8y agoDevelopers love to be able to write their magical code and their clever abstractions and often forget that their code is paying the price by becoming less clear and less readable. Are you saying that it has to be that way with generics? Because I would disagree with that. Cautiously applied, generics can make your code more clear, more readable and, most importantly, more type safe – and not just because of containers, see Swift’s key paths for an example.
- baby 8y agoYes it will be this way for MOST usages with a minor subsets of codebases which will benefit from them.
- vmchale 8y ago> Developers love to be able to write their magical code and their clever abstractions and often forget that their code is paying the price by becoming less clear and less readable. Clearly, that justifies the fact that you can't sort an array of doubles and an array of floats with the same function.
- baby 8y agoDoes it not? That’s the entire point of my comment. Some stuff are going to be painful but overall the lack of generics is a blessing.