Kazinsal wrote:
onlyonemac wrote:
And this is exactly the reason why WSL shouldn't exist.
WSL shouldn't exist because it runs everything Linux can and more?
WSL shouldn't exist because it deceives users into thinking that they can get all the benefits of Linux wihtout actually using Linux.
Kazinsal wrote:
Windows is plenty customizable [...] there are utilities for reskinning your window manager
In other words, Windows is only customisable if you install extra bloat and hack it up in ways that it was never intended to be used and that break more things than they're worth. In Linux, if I want to re-skin my login screen, I just need to copy and edit one or two XML files, and that's not a hack because the login screen is designed to be customised through the use of XML files. Likewise, installing a new window manager theme is one click away, and if I don't like the icon in the applications menu that that theme chooses I can change it with a few shell commands.
Kazinsal wrote:
This is not a Windows problem. svchost is a host process that hosts services (which are not wholly standalone programs but rather modules that run under the generic sandboxing host process). Third-party drivers and software can include services that are run by the generic host process, and if we're going to be blaming services for making an entire OS crap, then Linux is worthless because the touchpad user-space daemon likes to busy hang on my single-core laptop when I put resume it from sleep in a virtual terminal and it makes the entire computer unusable.
As I said, these are completely different systems so I doubt that they all have exactly the same problematic driver, and on one of the systems it was the Windows Update service that was causing the problem anyway (I still haven't found a fix for that, either - I tried emptying the Windows Update cache, reinstalling Windows Update, and running all of the crappy "FixIt" tools from Microsoft, and it still uses a whole CPU core and refuses to install any updates). By contrast, I've only had issues with two Linux systems, and one was an old laptop (which would sometimes hang when switching to a virtual console) from the era when laptop manufacturers were notorious for putting lots of proprietary components in laptops and Linux support was known to be poor on laptops, and the other was an old nVidia card which Noveau wouldn't recognise and I couldn't find a proprietary driver for it (and it worked except for the 3D acceleration).
Kazinsal wrote:
I don't know what you're getting your information from, but NTFS supports every Unicode character in filenames except NUL and forward-slash. Win32 has a few other restricted characters because the API handles globbing and argument sets for all Win32 programs to give a consistent interface across the system.
I never said anything about NTFS. I don't care whether it's the fault of the kernel, the filesystem, or simply the interface, but whatever part it is it prevents me from entering certain commonly-used characters in filenames, and even if it's just the interface that's still what most people see of NT (and not completely seperable from the kernel) and therefore enough to qualify in a "Microsoft is crap" argument.
Kazinsal wrote:
a system I have that has eight Marvell Fast Ethernet NICs in it
I'm going to assume that the problem is because your NICs are perhaps obsolete or obscure hardware, as you haven't really given enough information to properly assess the situation and what may be causing the problem (or even exactly wha tthe problem is). Linux can utilise as many NICs as you can fit in your computer in ways that no other OS that I've ever seen can.
Kazinsal wrote:
and every surround sound system I've ever encountered
My motherboard has onboard surround-sound and it works fine with the right software. Make sure that your media player supports surround-sound output - I use VLC and I've never had any problems getting the right channels to play through the right speakers.
Also, stop mis-spelling my username.