31–40 of 51 posts
Makes sense. I think this will be huge for them. Especially if administration is easier than openstack.
Earlier quoted context omitted.
Not quite... when I run into an issue with my Linux machine, I can trace the code all the way down to the kernel. When I run into a problem with my Windows machine, I have to resort to random searches and hoping that someone else has seen it.
> I can trace the code all the way down to the kernel. Maybe you can but do you? This requires not only figuring out how to compile your ENTIRE stack but also doing it AND figuring out how to debug each piece (since generic debugging tools are not the best). I understand there may be major issues that require this level of insanity but the rarity is so incredibly high and so few have enough domain knowledge to do it…
Earlier quoted context omitted.
Not quite... when I run into an issue with my Linux machine, I can trace the code all the way down to the kernel. When I run into a problem with my Windows machine, I have to resort to random searches and hoping that someone else has seen it.
> I can trace the code all the way down to the kernel. Maybe you can but do you? This requires not only figuring out how to compile your ENTIRE stack but also doing it AND figuring out how to debug each piece (since generic debugging tools are not the best). I understand there may be major issues that require this level of insanity but the rarity is so incredibly high and so few have enough domain knowledge to do it…
Earlier quoted context omitted.
> I can trace the code all the way down to the kernel. Maybe you can but do you? This requires not only figuring out how to compile your ENTIRE stack but also doing it AND figuring out how to debug each piece (since generic debugging tools are not the best). I understand there may be major issues that require this level of insanity but the rarity is so incredibly high and so few have enough domain knowledge to do it…
There's a level of understanding and debugging possible from reading the source without compiling/debugging that's not possible with access only to binaries. I'm a .NET/Windows developer mostly, and I've found myself consulting the .NET library reference source dozens of times over the past year. This has been useful, despite the fact I've never compiled it. Five years ago I would never have thought my work would req…
I certainly agree with you but the claims of tracing the flow of execution down to the kernel? That's extreme in my opinion. Obviously there are times that's useful but for the majority of developers I can't imagine that's even as frequent as a rare occurrence. At least in my personal experience I only know maybe 2 people in my past experience who could actually do this. I just don't think the majority of developers know how to step outside of a few frameworks or languages.
At least Microsoft released the debug symbols for .Net back in 2012 so you've been able to at least trace through your framework's source for a while now :)
Can anybody explain me in layman terms what this means? I understand that Azure is Microsoft's Cloud Platform that provides services through which you can deploy your application on cloud. Does this mean that you can run Azure on your own datacenter like Microsoft is doing currently?
I'm a product manager with Microsoft. With the Azure Stack, you can deploy your applications on your on-premises (private) cloud, just like you would do in Azure - you're essentially retargeting the app. Our ultimate goal is to empower maximum application agility. To enable the same deployment experience, Microsoft is bringing the same Azure portal, user experience framework, and underlying IaaS/PaaS APIs and service…
This has the definite advantage of limiting fear of being 'locked in' in deploying into Microsoft's Azure cloud - you can always run your application on your own Azure fabric. So does this also open up the opportunity for alternate Azure hosting providers to enter the market?
It also opens up the possibility of private-cloud versions of Microsoft's cloud offerings. Office365 runs on Azure fabric; can Microsoft now package that up as something you can deploy into your own Azure datacenter?
These kinds of developments can't make VMware happy. I have not understood why VMware never made a big iaas play when it had the chance to compete before others became established and established mindshare. I only guess they didn't want to compete against themselves, which is understandable but shortsighted.
I work on vCloud Air (VMware's IaaS offering) and this is just a guess (since I wasn't here at the time) but I imagine it wasn't about "competing against themselves."
It's easy to sit here in 2015 and say getting into IaaS early should have been obvious but that's ignoring the reality of what IT departments were saying they wanted. In 2008 88% of IT buyers preferred on-premise deployment, by 2014 that had declined to 13%[1].
FWIW early access to vCloud Hybrid Service (the original name of vCloud Air) was available in June 2013[2] and obviously something like this isn't put together overnight.
[1] http://www.softwareadvice.com/buyerview/deployment-preferenc...
[2] http://www.vmware.com/company/news/releases/vmw-vcloud-hybri...
Earlier quoted context omitted.
Not quite... when I run into an issue with my Linux machine, I can trace the code all the way down to the kernel. When I run into a problem with my Windows machine, I have to resort to random searches and hoping that someone else has seen it.
What percentage of Linux users do you think have the capability or the desire to spend their time tracing calls through various libraries and kernel source? When I run into a problem on my Linux machine, I typically have to do a lot of searching. More searching than I must do with Windows, because while there is generally only one Windows (at least relative to Linux), there are hundreds of Linuxes, distros and versio…
A minority, to be sure. But ultimately I am worried about the ability possessed by myself, my team, and potential hires. Not that of the average Linux user not working on the problems I am working on.
The argument for how the ability to do this is beneficial is not predicated on general users being able to do it, but the people administrating the services in question being able to do it.
If you have the ability to do so, it's possible in Linux (or the other open source OS). It's simply not possible in Windows.
Whether or not that's a huge deal is up for debate, but you're not really attacking a part of the argument that's relevant to their original point.
Dear MS. Thanks for going open source with dotNet. We will use it on our Linuxes and BSDs, with gratitude and joy. But when it comes to your intention of bringing your non-open-source'ed software to our data centers: we were actually almost finished taking them out, and feel much better that way.
Microsoft is on par with Linux and BSD machines. Until you are reading all the source code, there's no point in switching to Linux or BSD if you're already using Microsoft. Microsoft has the best and robust tools for the job.
Increasingly, many tools and environments work best on Linux - which is quite an amazing shift from a decade ago.