4,058 karma · joined September 12, 2018
No, they're arguing on the grounds that the tools are detrimental to the overwhelming majority in a way that also ends up being detrimental to the disciplined minority!
I'm not sure I agree, but either way you aren't properly engaging their actual argument.
I suspect it's a combination of factors, one of them being that US cash has absolutely awful usability compared to the Euro.
The rule of law is one of the greatest achievements of western society and a major reason for the west's global dominance.
True, it was always imperfect due to the realpolitik of power. But that doesn't change the fact that the very idea of rule of law is in opposition to rule of power.
A well functioning legal system would throw out everything in those contracts on that basis alone.
There are so many ideas that sound good on paper but are bad in practice, and that happen to be convenient for the goals of unscrupulous powerful people.
The notion that society as a whole will at some point stop falling for such ideas seems very optimistic to me.
You mean the book that has a 40(?)-page chapter in which characters you never hear from before or afterwards describe what's happening in their home lands didn't go into the day-to-day? :)
Lord of the Rings (the book) is obsessed with this kind of detail to the point that many people find it difficult to read.
As a high status person, you have an outsized influence on culture whether you like it or not, and an environment in which this kind of question can be asked ultimately leads to better outcomes.
There's a long history in computer architecture of cores and accelerators that don't have a cache but instead rely on explicitly programmed local scratchpads. They are universally more difficult to program than general purpose CPUs because of that.
A deeply technical one, yes, but that's not what drives their decision making.
Thinking that two finger zooming style scaling is the goal is probably the result of misguided design-centric thinking instead of user-centric thinking.
That said, I'm also a bit surprised to see somebody discuss modular inverses without mentioning the extended euclidean algorithm, which is a more elementary solution.
The one thing that's really objectionable in that section is the last part about people who attack or flame without apparent reason. Such people should be called out by other community members in the same way ESR describes for newcomers in the first part of the section.
Autocomplete is a total focus destroyer for me when it comes to text, e.g. when writing a design document. When I'm editing code, it sometimes trips me up (hitting tab to indent but end up accepting a suggestion instead), but without destroying my focus.
I believe your reported experience, but mine (and presumably many others') is different.
For objects that don't have that property, you're just exchanging one kind of badness in the design for a different but ultimately equivalent badness.
C++ constructors can't return values. If construction is fallible, the only way to communicate the error is via C++ exceptions. If you're in a code base that embraces exceptions, that's fine. But (C++) exceptions kind of suck, so many code bases don't, and then you have to find some alternatives.
Over the years, I've increasingly adopted a pattern where the constructor is private in this case and the object construction can be done with static methods - which is a bit more like Rust, actually.