221–230 of 296 posts
So now I’m just waiting to hear Microsoft is switching its kernel to Linux. Especially after the switch to chromium.
Earlier quoted context omitted.
Microsoft's GUI management tools were really good and generally very discoverable. IMO they were a much better way to manage an OS than cryptically named CLI programs and text files. And most of them worked remotely. And by comparison to modern software they can not even remotely be considered bloated. Every electron application ever made is larger than all of RSAT. Now of course they suck ass because MS has no idea…
> GUI management tools were really good and generally very discoverable The snap-ins? A main criticism of all this is that the usual tools didn't work remotely - you need a different, undiscoverable, possibly differently licensed, set of tools from what you use to change settings on your local computer. And of course you can't easily set up Computer A and then clone its settings to Computer B; you can only do this gl…
I can't think of any that I use regularly that don't work remotely. Which snap-ins are you referring to? Most of them you just right-click on the top level object and select "connect to another computer".
Earlier quoted context omitted.
Microsoft's GUI management tools were really good and generally very discoverable. IMO they were a much better way to manage an OS than cryptically named CLI programs and text files. And most of them worked remotely. And by comparison to modern software they can not even remotely be considered bloated. Every electron application ever made is larger than all of RSAT. Now of course they suck ass because MS has no idea…
Those cryptically named programs are scriptable, and those text files (including scripts) are easy to version and backup.
Now all they have to do is switch their kernel to linux, their gui to kde and get their office suite to LibreOffice, and Windows will be the perfect computer.
Windows ux is better out of the box than on any Linux so far, it's really polished. The office suite is also much better than alternatives. So just switching the kernel to Linux would be enough and super winrar.
See the rants at:
https://social.technet.microsoft.com/Forums/en-US/415943c7-7...
https://www.tenforums.com/windows-updates-activation/111890-...
I'd love to be able to submit this bug on the issue tracker, if you could tell me where to find it.
And we are talking here about an OS and GUI made by the same vendor. Hugely different from the Linux+GUI situation.
[1] which is another example of a awful legacy interface where by default you can only peek at the first 2 unrelated lines of every log mesage (and even worse: without a standardized format)
Earlier quoted context omitted.
They started on this in the late 2000s when I was an intern there. But there was a lot to untangle. It’s the biggest refactoring job you can imagine. A decade long effort. Back then they didn’t really understand the point of ssh though. They had a vision of remote management via .net RPC and powershell.
This makes you seem like you don't understand the point of PowerShell remoting. Passing serialised scriptblocks to the remote host, executing them, and getting serialized objects back. Meaning you can pass serialisable objects around, handle errors, the multiple output streams, etc. over the remoting connection. Because it's integrated into the language, you can pull PowerShell modules over from the remote host to th…
That's fine in theory, except that some very common Windows Objects can't be serialized in any meaningful way (most painful one for me being the Windows Update Client), which means that certain "remote" operations are actually affecting the client machine, or are failing because the client lacks support for certain operations.
I've been using Powershell since v2, but to me, it's essentially a walled garden automation environment. Just one more way for Microsoft not to give you the tools to efficiently manage your fleet.
Microsoft is becoming the defacto leader in open source.
Microsoft only releases the source on products they create when they clearly can't compete, and they have no other option. In terms of open source leading and inovation ms is worth 0.
Although they have a good R&D. There isn't anything new they contributed to OSS community.
Earlier quoted context omitted.
How is it misleading at all? Hyper-V Manager for example is literally a wrapper for Powershell commands. Virtually all Windows administration can be done entirely in Powershell. And like I said, the literal default installation of Windows does not even include a GUI.
What do you consider the "literal default installation"?
Earlier quoted context omitted.
Microsoft's GUI management tools were really good and generally very discoverable. IMO they were a much better way to manage an OS than cryptically named CLI programs and text files. And most of them worked remotely. And by comparison to modern software they can not even remotely be considered bloated. Every electron application ever made is larger than all of RSAT. Now of course they suck ass because MS has no idea…
It's almost 2019. Are we still fighting over this? OTOH, purely from my experience, MS's tools are good for managing a domain, or some computers. When you start to administer hundreds or thousands of servers, scriptability of CLI tools and pliability of text files trumps all computer automation. xCAT and Salt are two tools (that I use regularly) which are built on these properties and can manage thousands of servers…
As someone who just started working as a developer and is using windows for the first time in 4.5 years, I can't believe how much I miss ssh and command line tools for everything... ssh keys would solve so much trouble with scripting and credentials... Also sudo...
As other comments mentioned, just use the Linux sub-system + I would add Cmder as an alternative to the horrible native console. Edit: Cmder - http://cmder.net/
However, I have changed the following:
* Set the default font to Droid Sans Mono (Slashed) [1]
* Set the scroll back to 9000 lines, and the default width/height to 132x50.
* Used ANSI to colour code the prompt.
* created a small tool called su.exe that re-launches cmd.exe as Administrator (it can't be done inline unfortunately)
And then I use openSSH (the Windows 10 bundled version) to remote to linux boxes.
It's all fine. I really don't understand the hate.
---
[1] my own edited copy of Droid Sans Mono where the Zero has a 'slash' added.
Earlier quoted context omitted.
> GUI management tools were really good and generally very discoverable The snap-ins? A main criticism of all this is that the usual tools didn't work remotely - you need a different, undiscoverable, possibly differently licensed, set of tools from what you use to change settings on your local computer. And of course you can't easily set up Computer A and then clone its settings to Computer B; you can only do this gl…
> A main criticism of all this is that the usual tools didn't work remotely I can't think of any that I use regularly that don't work remotely. Which snap-ins are you referring to? Most of them you just right-click on the top level object and select "connect to another computer".
A quick check shows the availability of "connect to another computer" is a bit random; I can do it in services.msc and taskschd.msc but not in diskmgmt.msc . Maybe that's why I've never found it before.