Never heard of Wireguard, so I went to their website and for a half second. I thought I cracked the screen on my new phone, because of their freaking background image....
But, it looks interesting. I'll have to check it out more.
British Aerospace delivered an anti-radiation / air-defense suppression missile called ALARM in 1990: it is capable of flying up to 40,000 feet, deploying a parachute and then waiting for the target radar to come online as it floats down.
At that time, it initiates a secondary boost motor and attacks.
We didn’t used to call this a suicide drone; we called it a loitering munition.
I no longer use any of Google's services and neither does my employer for this reason.
We did have one application running on their cloud, but decided to move it to aws because we just can't trust them to keep anything around. Every year we had to rebuild some part of our app, because they replaced or completely removed some feature we were using. It got old and we were done with it...
Companies push their own apps for control. They are very limited on the types of metrics and tracking that can be done through the browser. By pushing their own apps they become limited only by the operating system itself.
I would agree that advertisement has done a lot of damage. However, there have been a lot of really awesome things that could not have happened without it. Like YouTubers for example, so many people are able to make a living making content they love and people love to watch. I say that as many of them are now having to turn to things like patreon because advertisement is now hurting them...
"I really need to get this deployed to production. I'll remove the warning debugging flag and build it... AH MAN look at all these unused import error!! Screw it! I don't have time to fix them all. I'll just add it bad and fix it later"
That is a valid position, but imo at odds with the implicit position of Go's creators. Arguably, the Mommy regime of Go's compiler is very much reflective of Go's creators' appraisal of the software maturity of its intended users.
Regarding the point in general, the notion of "broken windows" is applicable.
It's the problem of "he knows what he's doing" vs "I know what I'm doing".
In the old unix days, tools were built under the assumption that "he knows what he's doing", meaning that if you typed "rm -r /" you probably had a good reason to do so. We've since learned that just blindly trusting potentially fat fingers is probably not the best approach, and so the more dangerous of those tools have been modified to require you to add additional flags to do the most dangerous things.
It was the same in C, where the compiler blindly did exactly as told until we realized that software developers have fat fingers too. Unfortunately, they got it backwards, issuing warnings that by default don't halt compilation ("he knows what he's doing"), which led users and managers to believe that warnings aren't serious enough to deal with.
What they SHOULD have done is made those warnings halt compilation by default, and only allow compilation to continue if the user had invoked an additional opt-in ("I know what I'm doing") flag.
There's also the issue of inconsistent warnings across compilers and the subtleties of UB in C that contributed to the warnings problem, but we don't have that in Go.
People often say this sort of thing about the constraints imposed by various systems. It's a bit of a rhetorical party trick, though, designed to avoid engaging with the design rationale of the constraints by appealing to the operator's vanity.
> Go's creators' appraisal of the software maturity of its intended users.
More like immaturity:
“The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt.”
"I really need to get this deployed to production. I'll
build it... AH MAN look at all these compilation errors and failing tests!! Screw it! I don't have time to fix them all. I'll just remove them and fix it later."
I was still working in the security field (MSSP SOC) when Coinhive came out. It quickly because one of the prominent "threats" we had to deal with. All of our clients wanted any site that had Coinhive on it, whether or not the site owners added it or criminals did, blocked. It was view by nearly everyone in cyber security, including AV companies, as malware. It got a bad reputation because many sites didn't allow you to opt-in, and many didn't even tell you they were running it.
But, it looks interesting. I'll have to check it out more.