Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer
-
@Obsolesce said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
Everything else was a Strawman.
So keeping things equal:
a) Fresh Windows 10 + Google Chrome web browsing
b) Fresh Ubuntu Workstation (Gnome) + Google Chrome web browsing.a) Fedora Server minimal install + (FLAMP)
b) There is no Windows equivalent... Linux is the pure winner here by lack of Windows equivalent. -
@Obsolesce said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
@IRJ said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
Many of Microsoft's own features are not supported on core
Like what? Core does everything I can think of... Are you thinking of Nano?
Yes I must have been thinking of nano. I have been a Windows admin in awhile. I know 2012 Core was missing features, it does look like 2016 does have nearly everything.
-
@IRJ said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
@Obsolesce said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
@IRJ said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
Many of Microsoft's own features are not supported on core
Like what? Core does everything I can think of... Are you thinking of Nano?
Yes I must have been thinking of nano. I have been a Windows admin in awhile. I know 2012 Core was missing features, it does look like 2016 does have nearly everything.
Has nearly everything, but still tons and tons of Windows-only workloads don't run on it. Try running a QuickBooks server or a AviMark server on Core. Don't think that it works. Microsoft's own tools work, yeah. But Windows exists essentially exclusively for the third party ecosystem which almost always demands a GUI. Linux could have that same problem, but its ecosystem of users simply wouldn't put up with that, and it is that user base that has protected it and not Windows.
-
@scottalanmiller said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
@Obsolesce said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
@IRJ said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
Who would license Windows Server to run an inefficient web server?
Nobody in their right mind would do that. Again, like Scott, why add in things that were never part of any point?
Let me refresh the point:
- Scott originally compared full blown Windows Desktop GUI plus web browser and other app RAM usage, to a minimal gui-less Linux server RAM usage.
This was what I was arguing against, that the comparison was not fair and was not set up correctly.
Except I was specifically making the comparison on use case, not on technology. So the bases for your correction doesn't make sense. I pointed out that one was assumed to have a GUI and be used graphically, and one was assumed to be a headless server. So my comparison wasn't Windows vs Linux, it was use case vs. use case.
What use case comparison involves Windows GUI + web browsing versus GUI-less Linux minimal install?
-
@scottalanmiller said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
@IRJ said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
@Obsolesce said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
@IRJ said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
Many of Microsoft's own features are not supported on core
Like what? Core does everything I can think of... Are you thinking of Nano?
Yes I must have been thinking of nano. I have been a Windows admin in awhile. I know 2012 Core was missing features, it does look like 2016 does have nearly everything.
Has nearly everything, but still tons and tons of Windows-only workloads don't run on it. Try running a QuickBooks server or a AviMark server on Core. Don't think that it works. Microsoft's own tools work, yeah. But Windows exists essentially exclusively for the third party ecosystem which almost always demands a GUI. Linux could have that same problem, but its ecosystem of users simply wouldn't put up with that, and it is that user base that has protected it and not Windows.
Right no vendor supports it. Because they are equally scared of it. It only works for windows services.
-
@Obsolesce what percentage of your windows servers for domain services are core at where you work now? I would assume less than 50%
-
@IRJ said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
@Obsolesce what percentage of your windows servers for domain services are core at where you work now? I would assume less than 50%
100%
-
@Obsolesce said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
@IRJ said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
@Obsolesce what percentage of your windows servers for domain services are core at where you work now? I would assume less than 50%
100%
-
@Obsolesce said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
@scottalanmiller said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
@Obsolesce said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
@IRJ said in Client-side Virtualization - CompTIA A+ 220-1001 Prof Messer:
Who would license Windows Server to run an inefficient web server?
Nobody in their right mind would do that. Again, like Scott, why add in things that were never part of any point?
Let me refresh the point:
- Scott originally compared full blown Windows Desktop GUI plus web browser and other app RAM usage, to a minimal gui-less Linux server RAM usage.
This was what I was arguing against, that the comparison was not fair and was not set up correctly.
Except I was specifically making the comparison on use case, not on technology. So the bases for your correction doesn't make sense. I pointed out that one was assumed to have a GUI and be used graphically, and one was assumed to be a headless server. So my comparison wasn't Windows vs Linux, it was use case vs. use case.
What use case comparison involves Windows GUI + web browsing versus GUI-less Linux minimal install?
Lots. Like when you are using RDS versus using a PBX.
It's that we are comparing different use cases is the point. Not comparing the same use case in two different places.
-
Very Interesting!
