(This post was last modified: 05/09/2013 01:30 PM by Kuu.)

(This post was last modified: 05/09/2013 01:50 PM by Joom.)

This is just one of those "your opinion" answers. Unfortunately I'm with Kuu on this one, I'd probably stay in linux if it had commercial support (relevant to myself like office/photoshop/VIDEO GAMES) but that just undermines what the whole idea of free software linux (I know there are commercial products, but most desktop linux OS's are based around the free principle) is about anyway. Yeah, I'm probably getting buttfudgeed by the companies but unfortunately commercial software sometimes does things better than our free alternatives.

As for Windows being a clusterfudge...it is, but that doesn't mean you can learn your way around the operating system to tune it. So far I've been using it in a pseudo-unix/gnutools/whateverencompassestheshell environment by doing my file operations and other spoon with powershell. It's nice, not a lot of people like it, but it seems to be a suitable replacement for a bash shell that I sorely miss from linux.

If anything, you can pull ideas from linux and see if you can apply them in windows, I'm doing that effectively so far.

What it really boils down to is that you can really get either operating system to do what you want if you just have an open mind to learn. So it'll be better or worse depending on your knowledge. Learn your tools!

Apologies to the linux gurus for my terminology, I can never follow it correctly :/

If I have to make a closing statement though, you may want to support the linux distros just because they're free. The last thing you need is for someone to put a pricetag on things that you use to get on with your life in the digital age.

(This post was last modified: 05/09/2013 02:14 PM by Tetris999.)

(05/09/2013 02:12 PM)Joom Wrote:  I suggest using Cygwin over Powershell. Where Linux lacks in commercial support, it makes up for with free alternatives. Now that Steam is on Linux, new games are hitting it just about every day. Games and other software also aren't that tedious to get working in WINE if you know what you're doing. Also, I still can't swap out the NT kernel for a custom one. That's another area where Windows fails. It's the only system you can't run a custom kernel on (and I don't want to get into it about the more obscure, ReactOS spin offs).

Yeah, cygwin is a bitch to update packages for though. Then again, it may just be that I've been too lazy to find a better alternative to the GUI package updater. I like to lean towards powershell just for the fact it's a windows tool, so it'll probably be able to interact better with the operating system than an emulation that is trying to be shoehorned into the windows system.

(This post was last modified: 05/09/2013 02:20 PM by Tetris999.)

(This post was last modified: 05/09/2013 02:21 PM by Joom.)

(05/09/2013 02:20 PM)Joom Wrote:  I just threw "setup.exe" in C:\cygwin. Any time it needs an update, I just run it. It should do everything for you. And it's not emulation. Cygwin sets up an actual POSIX compliant environment.

Woops, this is why I should stay away from assumptions, thanks jooms for pointing that out. I guess the thing that I was getting at was this part of an answer on stack overflow

Quote:My original intent was to include a set of Unix tools in Windows and be done with it (a number of us on the team have deep Unix backgrounds and a healthy dose of respect for that community.) What I found was that this didn't really help much. The reason for that is that awk/grep/said don't work against COM, WMI, ADSI, the Registry, the cert store, etc, etc. In other words, UNIX is an entire ecosystem self-tuned around text files. As such, text processing tools are effectively management tools. Windows is a completely different ecosystem self-tuned around APIs and Objects. That's why wee invented PowerShell.

What I think you'll find is that there will be lots of occasions when text-processing won't get you what you want on Windows. At that point, you'll want to pick up PowerShell. NOTE - it is not an all or nothing deal. Within PowerShell, you can call out to your Unix tools (and use their text process or PowerShell's text processing). Also you can call PowerShell from your Unix tools and get text.

http://stackoverflow.com/questions/57362...on-windows