Satya Nadella just fixed Microsoft’s biggest problem

Post by mrob » Fri, Jul 15, 2016, 2:53 PM UTC

throwanem wrote: post #39

labrador wrote: post #2

Use my bookmarklet to hide that horrible image of Balmer sticking his tongue out javascript:(function (){var x = document.getElementsByTagName("img");for (i = 0; i < x.length; i++){x[i].setAttribute("src","");}}());

Here's one you can use to delete arbitrary elements from a page by clicking on them. It's handy in this age of unfortunate design decisions. javascript:for(var%20i=0;%20i

Post by douche » Fri, Jul 15, 2016, 2:54 PM UTC

drinchev wrote: post #6

I was a Windows user for a long time. 5 years ago I switched to OS X, because I think it's closer to the deployment environment I use as a dev. However what OS X did ( when they killed the old one - MacOS 9 and rewrote the whole thing on UNIX based kernel ) was the single greatest move, which I think pays off even these days. This is what I hope should happen with Windows. They should decide on POSIX kernel and compl…

Post by youdontknowtho » Fri, Jul 15, 2016, 3:03 PM UTC

zimbatm wrote: post #59

hacknat wrote: post #32

>At Microsoft, those resources are so disconnected from engineering that they seem to rely on whitepapers and customers to learn about their own products. This is so true. My company was being courted by Azure folks so we got some premium access and it was always laughable and frustrating how much more I knew about their cloud architecture than they did. I remember finally being able to talk to the head of network en…

Azure is the worst. I think their strategy is to throw money at addon providers (and other customers) until something sticks. The issue is that their API is so horrible that unless you use .NET and use their official client libraries it's way too much work. I remember one time we published our addon on production and it had a different behavior than staging...

Post by bbctol » Fri, Jul 15, 2016, 3:06 PM UTC

lego6245 wrote: post #70

cptskippy wrote: post #57

Earlier quoted context omitted.

One of the problems Microsoft has that others don't is brand confusion. They like to ride on their own coat tails so distinct and unique products that are completely unrelated are often called the same thing. What do you call Microsoft's personal email client? Outlook. What do you call Microsoft's web based personal email service? Outlook. What do you call Microsoft's enterprise email client? Outlook. What do you cal…

Well, technically speaking the web based ones are called Outlook Web Access. And I don't feel there is confusion. How is it different with Microsoft that Outlook is Outlook, from how with Google Apps Gmail is Gmail? Just like with Outlook there are enterprise versions of Gmail too. Is it feature parity?

Post by youdontknowtho » Fri, Jul 15, 2016, 3:07 PM UTC

hacknat wrote: post #32

>At Microsoft, those resources are so disconnected from engineering that they seem to rely on whitepapers and customers to learn about their own products. This is so true. My company was being courted by Azure folks so we got some premium access and it was always laughable and frustrating how much more I knew about their cloud architecture than they did. I remember finally being able to talk to the head of network en…