News for hackers. Stuff that matters.
Re:Porting Node to Windows With Microsoft’s Help by Derbasti on Thursday June 23, 2011 @12:17PM (#2688444)
Not fast, ugly, bad integration in the OS, often outdated, bad package manager. Well, still better than not having a Unix prompt I guess.
Re:Porting Node to Windows With Microsoft’s Help by rbanffy on Thursday June 23, 2011 @12:36PM (#2688519)
The minTTY terminal helps a lot. Windows console is, indeed, a horrid environment.
Re:Porting Node to Windows With Microsoft’s Help by endtime on Thursday June 23, 2011 @12:48PM (#2688575)
Agreed about Windows console - I use http://sourceforge.net/projects/console/.
Re:Porting Node to Windows With Microsoft’s Help by MatthewPhillips on Thursday June 23, 2011 @02:16PM (#2689114)
Try Power Shell.
Re:Porting Node to Windows With Microsoft’s Help by heresy on Friday June 24, 2011 @01:50AM (#2691176)
PowerShell is handy, but man, is it slow. If you thought text rendering by cmd.exe was slow, wait till you get a load of PowerShell.

I don't really understand why the console subsystem in Windows is so slow that it can actually add a significant amount of time to a build with lots of scrolling text.

Even the "slow" Terminal.app is a whiz by comparison, to say nothing of Gnome Terminal, or, rxvt.

Re:Porting Node to Windows With Microsoft’s Help by contextfree on Friday June 24, 2011 @05:30AM (#2691586)
I remember a few occasions at work where I figured I'd write a quick Powershell script to process some text files or something, and writing the script was quick and pleasant enough, but then it turned out to be quicker to just write a C# program to do the same thing rather than wait for the Powershell script to finish =)
Re:Porting Node to Windows With Microsoft’s Help by rbanffy on Friday June 24, 2011 @06:53AM (#2691719)
> it turned out to be quicker to just write a C# program

I you really should install cygwin (and MinTTY).

http://www.catb.org/~esr/writings/unix-koans/shell-tools.htm...

Re:Porting Node to Windows With Microsoft’s Help by contextfree on Friday June 24, 2011 @11:04AM (#2692476)
iirc I had cygwin installed as well, but had mostly stopped using it for some reason I forget.
Re:Porting Node to Windows With Microsoft’s Help by contextfree on Thursday June 23, 2011 @03:25PM (#2689437)
... which runs in the standard console, and therefore does nothing whatever to address the problem with the Windows console being awful.
Re:Porting Node to Windows With Microsoft’s Help by MatthewPhillips on Thursday June 23, 2011 @04:07PM (#2689639)
It adds a bunch of useful stuff to the Path including select, sort, and ls. The lack of utilities in the standard cmd is my major gripe, what's yours?
Re:Porting Node to Windows With Microsoft’s Help by contextfree on Thursday June 23, 2011 @10:07PM (#2690669)
You were responding to someone's complaint about the lousy console window.
Re:Porting Node to Windows With Microsoft’s Help by natesm on Thursday June 23, 2011 @09:59PM (#2690655)
The emulator itself is absolutely terrible, compared to, say, gnome-terminal or iTerm.
Re:Porting Node to Windows With Microsoft’s Help by mikemaccana on Friday June 24, 2011 @05:04AM (#2691547)
PoSH 2+ includes tabs and a method browser IIRC.
Re:Porting Node to Windows With Microsoft’s Help by iambot on Thursday June 23, 2011 @12:23PM (#2688470)
pretty much, compared to an integrated terminal like *nix, im a big fan of things "just working"
Re:Porting Node to Windows With Microsoft’s Help by Derbasti on Thursday June 23, 2011 @03:58PM (#2689599)
I consistently prefer running a Linux terminal in a virtual machine to running Cygwin natively. And it is faster, too.
Re:Porting Node to Windows With Microsoft’s Help by chromic on Thursday June 23, 2011 @04:11PM (#2689659)
This is my preferred unix-in-windows setup as well. Free VMWare player and your favorite distro of linux and you're good to go.