My son is having a wonderful time teasing me about Invisible Woman's recent marriage on #MarvelRivals
I picked up her wedding dress skin to prove that inside my heart is not breaking. #friendstatus#imgoingbacktocod
@eurogamer If for no other reason but public safety—keep the ads on the anime cartoon porn. Feels super irresponsible to not have any surveillance on that demographic.
A Brief History of https://t.co/kppfMDnE2Y! Nothing official, just the conjecture as I recall it:
Microsoft’s first internal webserver, circa 1988, was a Compaq 386 sitting in the HR copy room with a note on it to “Never Turn Off!!!”
The first public site, about 1990, was run on a Northgate 486 scavenged from a build lab. It was used as a test bed for network changes, like the Winsock implementation.
At one point, the site was hosted on a laptop – until “Craig” took his laptop on vacation and then chaos ensued! So ownership transferred to “Mark”, with it becoming a managed service.
In 1995 we see the first “Death Star” website, as pictured here. It had initially been running on an EMWAC server, but shortly after the time of this screenshot, it was running IIS 0.9.
Reports vary on the hardware – some say a Compaq 386, whereas others claim it was Compaq ProLiant under "Henry’s" desk in Building 2. Either way, it was migrated to a proper Dell rack mount server at this time, but it was still hosted informally.
In the late 90s, hosting evolved from the makeshift “under a desk” arrangement to being hosted by ITG, Microsoft’s Internal Technology Group, in Building 11. Mark and his team set up the official site, including WWW, FTP, and even Gopher servers.
Apparently, this setup used 3 Compaq 386 servers – at a cost of about $50K.
https://t.co/kppfMDnE2Y is now part of Microsoft’s global cloud ecosystem (i.e., Azure). It’s served by a massively distributed, load-balanced network of high-performance servers across multiple data centers and regions. Precise numbers are not public.
Enjoy this random trivia? Repost and follow!
I believe in developing team conventions and formalizing them. I don't assume 100% of the team's stylistic preferences will be my own; I'm certain they will not. Semantic holy wars are silly and unproductive.
That said.. dangling commas are dumb. Wanna fight?#javascript#eslint
Silas and I both started @GodofWar Ragnarok last night. We carted a second TV and a beanbag into the living room. Seemed more logical than yelling back and forth from separate rooms. Christmas break is best.
@tesseralis I used it recently, and it had been a while. It's great when it is the right tool for the job. It's also annoying to use when REST would have sufficed.
@nixcraft Do they know how much memory is being wasted by those Chrome processes?! This person lied about being a "Developer" and, therefore, we do not trust. ;)
@jason_grundy It's definitely a tradeoff. The agility of working at a small shop is awesome. Having the resources of a large organization also has its perks.