http://readwrite.com/2014/07/01/linux-world-domination-compl...
I laughed hard. Also what is with all the question marks on the right side of the table? It's almost like they are not confident with their statements about Linux.
Linux Wins. Windows Sux is not the cookie-cutter answer I would expect on HN.
However, I'll bite:
> Will your Linux provider be able to support your entire infrastructure in the Cloud if the time comes?
We wouldn't put our entire infrastructure in the "Cloud", nor would our provider suggest it. Other companies have done so, though. While speaking informally, they're not happy with being "in the cloud" generally - regardless of provider.
> Does your provider offer a robust group of offerings, including Infrastructure-as-a-Service (IaaS) and Platform-as-a-Service (PaaS)?
I'm not very good at buzzword bingo.. but yes, they do provide their infrastructure and platform as a service. The last outage was about 18 months ago, entirely our fault. When was the last Microsoft cloud outage?
> Are they focused solely on the private cloud,
No, they're not focused solely on the private cloud - nor are Microsoft.
> and can they support Microsoft technologies for your existing Windows, Office, SQL Server and .NET users?
We have no need for supporting users of Microsoft technologies, so I really don't know how they'd be. Crap, I guess.
> Considering starting your next project on Linux? Yes. Have you?
> Acquisition costs are a fraction of the Total Cost of Ownership of software projects. Will skilled talent be readily available if your project grows? Yes, we have been successful in the past and we don't expect any problems in the near future. Personal note: Finding a good Windows developer out of the crowd of clowns is more difficult.
> What will support costs be if you choose to outsource? This is not something we have considered.
> Could future migration costs be prohibitive? We do have a back-out strategy. We're not locked in.
> Will patching and security lead to downtime? No. We do not use Microsoft products in production.
> We encourage you to fully assess these factors. Good advice, I will read more than just this "article" when deciding what platform we'll use...
> What does the vendor ecosystem look like for your proposed Linux solution? There is more than one.
> Do your potential partners have a certification program for their professionals and how extensive is their experience? To be honest, in my role I really don't give a damn about our "potential partners". Most non-windows shops seem to be adept, in my experience.
> Persistent threats and dedicated attackers can slow your projects and put your IT environment at risk with Linux projects.
As with all platforms, as Microsoft has experienced.
>Microsoft: Proven security development lifecycle
>Linux: Security threats?
You owe me a new keyboard. This one is full of coffee.
Also got to love the whole "Linux doesn't do AD" BS. If you still live in 2005, perhaps not, but that's about it. You could also argue that AD is a misfeature, given the almost hilarious insecurity of NTLM password hashes, etc.
Also, you can't claim that your systems are secure and then not have the code publicly auditable. That's preposterous.
edit: example: "Will patching and security lead to downtime?" There's ksplice and kgraft and more - patch the kernel with no downtime. And even without using either, I can't remember the last time I had to reboot immediately because a patch was that critical, or the last time I had to sit there waiting for my laptop to reboot 3 times trying to install the weekly updates. Windows Update blows.
edit: another example: "Proven security development lifecycle". Ha ha ha ha ha!
First it was the "Don't get scroogled" campaign, now this.
Oh, and the iPhone funeral fiasco too.
http://www.engadget.com/2010/09/10/microsoft-celebrates-wind...
They desperately need a Chief StayClassy Officer.
"you may be trying to access this site from a secured browser on the server. Please enable scripts and reload this page."
"a secured browser on the server"
where "secured browser" == one that has JS disabled (?)
"on the server": what is "something you shouldn't do on a server"
In general, however, your statement is on the same level of correctness as Microsoft's advertisement linked here.
You should use Microsoft server solutions because 1. Microsoft servers work well managing linux solutions 2. Linux systems can't handle microsoft solutions themselves 3. We are uncertain what Linux is capable of/how secure it is 4. Therefore, you should go Microsoft (QED)
Ignoring how blatantly misleading these points might be given that linux is quite mature and we now live in a work of system virtualization (Wine anyone?), the argument here only serves to convince me that I should be using linux solutions instead of Microsoft solutions in my company. If a given solution works for linux (which, despite calling out Active Directory, they don't seem to have ruled out as a possibility) and can also be managed through Azure, then Why on earth would I create an inflexible system that can only be managed through Microsoft branded tech? Am I supposed to be convinced by their skepticism on linux? I'm perfectly capable of researching linux server solutions myself. Am I supposed to be amazed at the flexibiliy of Microsoft servers while simultaneously scared away from the flexibility of using linux solutions? Outside of server use, this doesn't seem like a good argument to use Microsoft solutions at all.
wha?
Everything else in that page is a lie.
- The cloud as we know it is built on Linux.
- Web development has moved to Linux. Rails, Django, Laravel, Nodejs, all run better on Linux.
- Git works better in Linux, both as a server and as a client.
- The security issues are more severe in Windows.
And yes, MS AD is a killer feature.
I did a bit of digging, and apparently you need to follow a ridiculously long CNAME chain just to resolve the domain:
www.whymicrosoft.com. CNAME whymicrosoft.sharepoint.com.
whymicrosoft.sharepoint.com. CNAME prodnet17-37a0001.sharepointonline.com.akadns.net.
prodnet17-37a0001.sharepointonline.com.akadns.net. CNAME prodnet17-37ipv4a0001.sharepointonline.com.akadns.net.
prodnet17-37ipv4a0001.sharepointonline.com.akadns.net. A 157.55.62.117
For me, that's a typical example of why I avoid Microsoft stuff. They promise the world, but never seem to get the details right.Persistent threats and dedicated attackers can slow your projects and put your IT environment at risk with Linux projects.