3,244 karma · joined May 25, 2016
[ my public key: https://keybase.io/mnd999; my proof: https://keybase.io/mnd999/sigs/y8rJFojIoyLaUCl_FLMH47zHcg3axaMybUVsSLevTGs ]
It’s amazing how many people when presented with a list of policies will vote one way, but when presented with a list of names and parties will vote the other.
I liked the ones in the article. Dark, unsurprisingly.
Please stop with the tribal generalisations. There are more than two points of view in the world.
They’ve forgotten Goodhart’s law, and as such they’ve create a metric everyone is trying to game which ends up being counterproductive and unfair to everyone. Let’s not forget it’s equally unfair to promote someone before they are ready and then stack rank them against more experienced colleagues as it is not to promote someone who is ready.
Unless you’re were an early employee, in which case you’re probably going for co-founder roles anyway, that’s if you haven’t retired already.
Your point is valid though, there are hundreds of other companies involved in this standard, many of them will make fantastic devices and there’s no reason to ignore them all because of one bad vendor.
It’s perfectly possible to build such chips with other designs and instruction sets, for example x86_64 or risc-v, in the same way it’s pretty common to build cheaper slower ARM processors. Plenty of folks at Intel and AMD are doing that right now.
GitHub ripping off everyone’s code to build copilot has caused a small (not as big as it should have been imho) exodus of open source projects to Gitlab and others.
I still don’t see how it’s a good idea to import unknown code with unknown licenses into your project, but apparently if copilot does it it’s okay.