1,578 karma · joined December 5, 2013
$ rustup component add rustfmt
error: toolchain 'stable-x86_64-pc-windows-msvc' does not contain component 'rustfmt' for target 'x86_64-pc-windows-msvc'
I looked for how to uninstall rust, and found that "the book" says that the command 'rustup self uninstall' will uninstall both rust and rustup. So I figured, what the heck, I'll start from scratch. I ran this command, uninstalling everything. Then I re-downloaded rustup-init.exe, and then ran it, reinstalling rust. I even then did 'rustup self update' and 'rustup update' for good measure.I still get the same error when trying to install rustfmt. What else is there to do if completely uninstalling and reinstalling doesn't work?
I think the problem is that Apple themselves want to reinvent and innovate the heck out of everything all the time, so they're making it harder than it needs to be. New Mac Mini? Easy: spec bump the current form factor. New Mac Pro? Easy: put the latest and greatest CPU/GPU in the old cheese-grater enclosure. But no, Apple needs to contantly make everything smaller/thinner/lighter/quieter, so they redesign the enclosure and reengineer the internals from scratch. While they're busy doing this, they continue to sell the old unimproved products for years.
Yes, Apple, we know you can innovate. But you say that for every "yes" there are a thousand "nos". Have you considered saying "no" to a complete reinvention of your hardware when your current offerings are so out-of-date? Your customers would be happy with a spec bump of the current form factors.
> That keeps track of play counts on both devices, lets me make smart playlists and playlist folders, and syncs music, contacts, and calendars all over USB without any cloud services prying into my personal data.
I use the latest version of iTunes and an iPhone with the latest iOS on it, and still use them in exactly the same way you describe. Like you, I prefer to have complete control over my own data, without passing it through third-party cloud services. So far, Apple has not taken away the ability to do this, despite their heavy marketing push for iCloud. (I literally have never used iCloud at all for anything, ever.)
Wait, what? Phone numbers could always include letters. Many businesses get phone numbers that include or consist of words relevant to their business, to make them memorable. And I've known people whose personal number happens to contain a word or words, so they give the letter version out because it's easy to remember. If a phone number field doesn't include simple logic to map letters into the proper numbers, that's just lazy programming.
I would have the opposite problem; if a Hacker News item was titled "Fred Lang Has Died", my first thought would be: "I didn't even know there was a programming language called Fred. It must have died from obscurity." :-)
So either I got a different layout for 14,758, or it's not impossible. And obviously, I've also never encountered a level with endless water. Is it possible that the procedural generation is not identical across all devices?
In which case, switching to webextension support exclusively is premature at this point, don't you think? It would have been better to wait until the API was robust enough to allow 99.99% of legacy extensions to be ported.
Also, the links under Implementations all result in a 404 page.
> There shouldn't be loads of them that start with an "A", or loads that end with ten "X"s, or anything like that.
This leads me to further doubt about the author's grasp of hexadecimal.
Shouldn't those version numbers be 2018.3 and 2018.9? Have we learned nothing from the Y2K bug?
> These accusations would come up even though they (all being computer science majors) know it's possible (although unlikely) for these events to happen. They just don't trust the black box.
I am reminded of the approach that GamesByEmail.com used to address this criticism: http://www.gamesbyemail.com/News/DiceOMatic