Linked by Thom Holwerda on Mon 7th Apr 2014 22:17 UTC
Microsoft

It looks like the Internet of Things could be the next big computing battleground, and Microsoft seems willing to sacrifice a few battles in order to win that war. Facebook is chasing virtual reality; Google wants home automation, smartwatches, and internet-connected glasses. More than 200 billion devices are likely to be connected to the internet by 2020, a huge example of the way the technology industry will shift and new battles will emerge. Satya Nadella believes the future isn't Windows desktops, Windows tablets, and Windows Phones. It's not Windows everywhere, it's Microsoft everywhere, offering software and services for every device - including an entire world of interconnected devices that have yet to be built.

The speed with which is doing this u-turn makes it quite clear that people within the company wanted to do this for a long, long time (otherwise it could not have been done this quickly), which implies that Ballmer may have simply held these changes back.

The elephant in the room here is that while people talk about Microsoft as if the company is down and out, it's still hugely profitable and has consistently been posting great financial results. It's just that Microsoft's money isn't coming from sexy products like smartphones and tablets, but from enterprise and backend stuff - stuff the technology press either can't write about, doesn't understand, or both. It's very similar to all those articles claiming Apple no longer innovates and disrupts, even though the company sent shockwaves through the microprocessor world.

In any case, it seems like Microsoft finally found the right direction in this new world.

Thread beginning with comment 586650
To view parent comment, click here.
To read all comments associated with this story, please click here.
oiaohm
Member since:
2009-05-30

That's a very special use-case, however, and besides, it hasn't been a requirement even before. There are already companies doing this without Wayland.


How is the difference. Before render nodes tech you don't have kernel level splitting.

Doing it without the changes wayland has brought to kernel level in Linux has major issues of security. This also results in stability issues.

Your point is partly correct the possibilities that render nodes open up simply have not been possible todo with quality before. Yes you could do it before but when one program screwed up on the gpu all programs on the gpu could lose context this is even true under Windows.


Multi seat at home has a place. You have your low power tablet and a person is on the PC. If they are not doing anything heavy and the PC has a Linux VDI on it hello you can be using that PC as well.

This is not like XP remote desktop where you take over the PC desktop. Multi-user has a place in the home.

We are looking at a different model. How will the new model Linux will be using fit into the world time will tell.

Reply Parent Score: 1

WereCatf Member since:
2006-02-15

Multi seat at home has a place. You have your low power tablet and a person is on the PC. If they are not doing anything heavy and the PC has a Linux VDI on it hello you can be using that PC as well.


This has been possible for over a decade now. You've never heard of e.g. headless VNC? You do not need VDI or Wayland to do that.

Reply Parent Score: 3

oiaohm Member since:
2009-05-30

WereCatf headless VNC I have heard of it. In fact used it. Headless VNC falls apart when you start using GPU accelerated stuff.

VNC headless is part of VDI solution.

Before render nodes there was virtualgl on Linux. Virtualgl demoed what this tech could do but could never take off due to the stability issues.

Sorry the reality without the render nodes changes and the improvement in management of the graphical stack to support multi user that wayland has brought into existence there are stacks of limitations.

Possible for a decade in working form is not true. Headless VNC for most of the past decade has been software rendering. No GPU assistance.

Big changes is the fact GPU now works.

When I say remote in I mean remote in and be able to run any application as long as you don't run out of resources. Past VDI has limitations on what you can and cannot run.

Reply Parent Score: 1