6 ms·

>"Gow is one of the few things that makes Windows bearable/usable" Good quote, but that is not necessarily a positive if you look at things from the perspectiv

by natch 12y ago

>"Gow is one of the few things that makes Windows bearable/usable" Good quote, but that is not necessarily a positive if you look at things from the perspective of the sooner Windows is ditched, the better.

blumkvist 12y ago
2015 will be the year!
- cbd1984 12y ago
  > 2015 will be the year! For Windows Phones? Don't hold your breath.
  - blumkvist 12y ago
    This comment in the definition of butthurt.
    - cbd1984 12y ago
      Flagged for rape joke: http://neologisms.rice.edu/index.php?a=term&d=1&t=13903 http://neologisms.rice.edu/index.php?a=term&d=1&t=13903
quotemstr 12y ago
Why? Windows is an excellent system and gets a lot of things right that POSIX gets wrong. WMI is wonderful; COM is wonderful; the NT kernel is from 1989 and still worlds ahead of Unixy kernels in many respects. (It's 2014 and I still can't open a file descriptor that represents a process.)
- orf 12y ago
  I think some of your examples are iffy, COM and WMI are sometimes wonderful but sometimes definitely not. Windows is not perfect and POSIX is better for some use-cases, vice versa.
  - quotemstr 12y ago
    Of course. The systems have a lot to learn from each other, to be honest. One of my biggest gripes back when I worked on the Windows team was the lack of a pseudoconsole API equivalent to the Unix pty interface. That said, using Cygwin is, as far as I'm concerned, the best of both worlds. Unlike some people, I like integrating the two environments as much as possible. I install Cygwin to C:\, for example, and I added support for using native win32 widgets to Cygwin Emacs. (Try the cyg32 package. You'll like it.) Try the "injob" utility too. It gives you native Unix job control with arbitrary Windows programs. (That it's even possible to implement it is a consequence of NT job objects being much better abstractions than POSIX process groups.)

6 ms·

>"Gow is one of the few things that makes Windows bearable/usable" Good quote, but that is not necessarily a positive if you look at things from the perspectiv

by natch 12y ago

blumkvist 12y ago
2015 will be the year!
- cbd1984 12y ago
  > 2015 will be the year! For Windows Phones? Don't hold your breath.
  - blumkvist 12y ago
    This comment in the definition of butthurt.
    - cbd1984 12y ago
      Flagged for rape joke: http://neologisms.rice.edu/index.php?a=term&d=1&t=13903 http://neologisms.rice.edu/index.php?a=term&d=1&t=13903
quotemstr 12y ago
Why? Windows is an excellent system and gets a lot of things right that POSIX gets wrong. WMI is wonderful; COM is wonderful; the NT kernel is from 1989 and still worlds ahead of Unixy kernels in many respects. (It's 2014 and I still can't open a file descriptor that represents a process.)
- orf 12y ago
  I think some of your examples are iffy, COM and WMI are sometimes wonderful but sometimes definitely not. Windows is not perfect and POSIX is better for some use-cases, vice versa.
  - quotemstr 12y ago
    Of course. The systems have a lot to learn from each other, to be honest. One of my biggest gripes back when I worked on the Windows team was the lack of a pseudoconsole API equivalent to the Unix pty interface. That said, using Cygwin is, as far as I'm concerned, the best of both worlds. Unlike some people, I like integrating the two environments as much as possible. I install Cygwin to C:\, for example, and I added support for using native win32 widgets to Cygwin Emacs. (Try the cyg32 package. You'll like it.) Try the "injob" utility too. It gives you native Unix job control with arbitrary Windows programs. (That it's even possible to implement it is a consequence of NT job objects being much better abstractions than POSIX process groups.)