Windows 10
-
@Dashrender said:
While it's not the same, MS has sorta recognized this by creating Windows Server Core.
Core addresses something different. In the UNIX world, you have always had the ability to remove the desktop completely. In fact for the first decade or more, there was no desktop at all (there were no monitors back then!) Windows Server Core allows Windows to be stripped of its desktop to make it a pure server as every OS except for Windows has always worked.
Microsoft is not doing anything that takes it towards the native networked interface model. That's just not something they are looking to do.
-
@Dashrender said:
From the server side, I can see it being extremely beneficial to pull the GUI off the machine and present it a la linux/Unix
For a server you would still never want a GUI. This is really about desktop / terminal server usage, not normal server usage.
-
@Dashrender said:
I was going to ask why you would want to run X over a network/WAN, but the answer is for the same reason you might want to run a Terminal Server/App Server, etc.
Correct. And using X has always given the ability to share a full desktop or to send only a single application / window over the network. It is pretty slick. What works great is that local windows and remote windows are completely the same, you can't tell where things are coming from. So a user can have a local desktop and have some apps running on a remote server somewhere, perfect for an application that needs heft computation or needs to run from a secured location or you need to balance network load. It's very nice. You can do the same thing with XenApp but it isn't cheap or simple. Every UNIX desktop can do this.
-
@Dashrender said:
Perhaps the Windows dev team at the time never considered windows to be used like nix was? The user interacting directly with the server machine like a remote session.
The Terminal Server product is quite old. They were definitely thinking in this direction a very long time ago, but maybe not as early as when they started down the OS/2 path with IBM which created the foundation of NT.
-
@scottalanmiller said:
@Dashrender said:
Perhaps the Windows dev team at the time never considered windows to be used like nix was? The user interacting directly with the server machine like a remote session.
The Terminal Server product is quite old. They were definitely thinking in this direction a very long time ago, but maybe not as early as when they started down the OS/2 path with IBM which created the foundation of NT.
True, they were thinking about it a long time ago.. but instead of solving it like Unix did, they bought technology from Citrix and applied it - that seems like a mistake in hindsight.
-
@scottalanmiller said:
@Dashrender said:
From the server side, I can see it being extremely beneficial to pull the GUI off the machine and present it a la linux/Unix
For a server you would still never want a GUI. This is really about desktop / terminal server usage, not normal server usage.
I'm trying to think why you would want this for general desktops? In an office environment, ok - maybe for support reasons, but for standard home users? would this really be that useful?
-
I'm feeling like the Linux 101 session has been just about covered in this thread...
-
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
From the server side, I can see it being extremely beneficial to pull the GUI off the machine and present it a la linux/Unix
For a server you would still never want a GUI. This is really about desktop / terminal server usage, not normal server usage.
I'm trying to think why you would want this for general desktops? In an office environment, ok - maybe for support reasons, but for standard home users? would this really be that useful?
You can say that about any feature. It's about the system being more robust and flexible. Think about the ENTIRE RDS, VDI and XenApp infrastructures just as a starting point that UNIX has had covered with every desktop since the beginning.
-
@Dashrender said:
True, they were thinking about it a long time ago.. but instead of solving it like Unix did, they bought technology from Citrix and applied it - that seems like a mistake in hindsight.
Yes, it does. It was the wrong architecture from the beginning. It was always a bit of "making due" with what they had rather than designing for the right solution.
-
@Dashrender said:
Thanks IRJ for posting the link - I would have missed it until tomorrow.
I think I'm going to buy this same tablet Garak has and use that as a platform for win10
I've held off putting Windows 10 on my WinBook...it is not optimized for tablets yet...more so for Desktop...
-
@garak0410 said:
@Dashrender said:
Thanks IRJ for posting the link - I would have missed it until tomorrow.
I think I'm going to buy this same tablet Garak has and use that as a platform for win10
I've held off putting Windows 10 on my WinBook...it is not optimized for tablets yet...more so for Desktop...
Might have spoke too soon...I do see the pictures IRJ posted... never could get the start screen going in my virtual Windows 10's...
-
@garak0410 said:
@garak0410 said:
@Dashrender said:
Thanks IRJ for posting the link - I would have missed it until tomorrow.
I think I'm going to buy this same tablet Garak has and use that as a platform for win10
I've held off putting Windows 10 on my WinBook...it is not optimized for tablets yet...more so for Desktop...
Might have spoke too soon...I do see the pictures IRJ posted... never could get the start screen going in my virtual Windows 10's...
Are you using Hyper-V?
-
@IRJ said:
@garak0410 said:
@garak0410 said:
@Dashrender said:
Thanks IRJ for posting the link - I would have missed it until tomorrow.
I think I'm going to buy this same tablet Garak has and use that as a platform for win10
I've held off putting Windows 10 on my WinBook...it is not optimized for tablets yet...more so for Desktop...
Might have spoke too soon...I do see the pictures IRJ posted... never could get the start screen going in my virtual Windows 10's...
Are you using Hyper-V?
I am using Hyper-V on my work desktop...VMWare Workstation on my Surface Pro 3 because Hyper-V and Surface Pro 3 do not play well together for standby mode...
-
I had no issue on Hyper-V on my Windows 8.1 machine. I just created a new VM, picked Generation 2, and mounted the ISO. The install only took about 20 minutes.
-
Well I have been playing around with Windows 10 a little more. Even though this is the initial beta, its seems more refined than Windows 8.1
Another thing I noticed is the compatibility seems better. I had an application that would not install in Windows 8.1. It kept giving me an access denied error even though I was logged in as an admin. I tried all sorts of different things to get it to work. Different admin accounts, different Windows 8.1 Pcs, and etc. For grins and giggles I tried to install the application on Windows 10. To my surprise it worked! It could be a freak incident, but so far I'm impressed
-
@IRJ said:
Well I have been playing around with Windows 10 a little more. Even though this is the initial beta, its seems more refined than Windows 8.1
It's a beta but not a beta of a new product but of a "point" release. This is the move from NT 6.3 to NT 6.4. So the way that a beta behaves is very different. It is some new code for sure, but the base is mostly extremely mature Vista-family (NT 6.x) code that has been running for nearly a decade now. They aren't making radical changes so I would expect the beta to be extremely stable and polished compared to more normal betas.
-
