Comment Re:It still works like shit. (Score 2) 51
It makes it economical to solve problems in code.
It makes it economical to solve problems in code.
MS introduced the concept of the Windows Remote Desktop
Allow me to be pedantic...
It was actually Citrix who "invented" the Windows Remote Desktop concept. Citrix licensed the Windows NT 3.X source code, and created a customized version they called Metaframe. They added support for running multiple interactive sessions, and had an abstraction layer for connecting keyboard/mouse/video to each session. Citrix created the ICA protocol for remote desktop. Microsoft bought back the rights for NT 4.X and created Windows Terminal Server (code name "Hydra"). Rather than use ICA, Microsoft created their own RDP protocol (which is loosely based on an obscure video conferencing protocol). Originally you could run both ICA and RDP on the same server; I'm not sure if that is still supported.
In short the concept of a remote desktop was a hack to get Windows to have some remoting features
That is one perspective.
IMHO, for most Windows users running most Windows applications, remoting the entire desktop is usually the best experience.
Remoting individual applications, as with X over SSH, is a niche use case. Citrix could do this with ICA, but it wasn't used very often.
Note: The fact that you are reading
Next, they'll require McDonalds to sell Big Mac combo meals for $2.50 to qualified low income customers.
I've got no love for ISP's, but where does this stop?
Using Azure, AWS, or any other cloud service isn't about saving money. At least not once you get to any sort of scale.You can almost always host it yourself for less.
What the cloud provides is flexibility. You can spin up additional resources on demand, and shut them down when no longer needed. You can get these resources in data centers all over the world.
Whether that flexibility is important enough to justify the added expense will depend on what you're doing.
Though in this case, the cloud *is* on-premise. It's not somebody else's data center, it's actually their own.
This isn't how big companies like Microsoft work. The LinkedIn part of the business is organizationally distant from the Azure part of the business. There may not be any management in common until you reach the CEO level. Azure mind as well be a different company.
You also have to consider that LinkedIn started as a separate business. They already had significant IT infrastructure in place when Microsoft acquired them. The decision they're facing is not "should we use Azure?". The decision is "should we fix something that isn't broken?"
Time is nature's way of making sure that everything doesn't happen at once. Space is nature's way of making sure that everything doesn't happen to you.