Bill Gates on Windows Usability (2003)

#1

Post by tosh » Fri, Oct 25, 2019, 6:28 PM UTC

Bill Gates on Windows Usability (2003)
twitter.com

Re: Bill Gates on Windows Usability (2003)

#2

Post by omnifischer » Fri, Oct 25, 2019, 7:15 PM UTC

Last line... at the end:

I reboot every night.

Re: Bill Gates on Windows Usability (2003)

#3

Post by tiredwired » Fri, Oct 25, 2019, 7:16 PM UTC

2004

Re: Bill Gates on Windows Usability (2003)

#4

Post by orangepanda » Fri, Oct 25, 2019, 7:25 PM UTC

tiredwired wrote: post #3

2004

Yet more relevant than ever

Re: Bill Gates on Windows Usability (2003)

#5

Post by Hamuko » Fri, Oct 25, 2019, 7:25 PM UTC

>So they told me that using the download page to download something was not something they anticipated.

Quote for the ages.

Re: Bill Gates on Windows Usability (2003)

#6

Post by contravariant » Fri, Oct 25, 2019, 7:28 PM UTC

Huh, that's the first time I've encountered a 451 (Unavailable For Legal Reasons) in the wild.

Re: Bill Gates on Windows Usability (2003)

#7

Post by mttjj » Fri, Oct 25, 2019, 7:28 PM UTC

The Twitter screengrab is only showing part of the PDF. Be sure to click the link in the tweet for the full email chain.

Re: Bill Gates on Windows Usability (2003)

#8

Post by Hamuko » Fri, Oct 25, 2019, 7:30 PM UTC

mttjj wrote: post #7

The Twitter screengrab is only showing part of the PDF. Be sure to click the link in the tweet for the full email chain.

451 Unavailable For Legal Reasons: Sorry, this content is not available in your region.

Re: Bill Gates on Windows Usability (2003)

#9

Post by mttjj » Fri, Oct 25, 2019, 7:31 PM UTC

Hamuko wrote: post #8

mttjj wrote: post #7

The Twitter screengrab is only showing part of the PDF. Be sure to click the link in the tweet for the full email chain.

451 Unavailable For Legal Reasons: Sorry, this content is not available in your region.

I'm still able to download the PDF. (USA here)

Re: Bill Gates on Windows Usability (2003)

#10

Post by jokoon » Fri, Oct 25, 2019, 7:47 PM UTC

Recently I installed specific parts of MSVC, since I'm using SFML and for now they only deliver binaries for 2017. After all I might not have needed to use 2017 or a particular SDK, since there seem to be ABI compatibility now, but I discovered that too late.

So I used this vs intaller, and I discovered that the vs dev prompt did not set appropriate folder to use cl.exe and lib.exe because it might only do it for the latest SDK or toolset thing. I still managed to do what I wanted, but this is another one of those details.

I still enjoy using C++ though, but it seems way better than the old days, I think... Although I have to admit MSVC sometimes crash and restart on machines that don't have enough RAM (6GB). I wonder how Clion compares to MSVC... I hope clion will be cheaper in the future.