Re:A Baseline for Front-End Developers
by MatthewPhillips on Thursday April 12, 2012 @02:18PM
(#3833570)
Unfortunate truth. Microsoft made a major error in abandoning the command line so many years ago and it is crippling for developing in not-.NET. powershell isn't the solution. Windows doesn't even ship with an unzip cli tool
It doesn't ship with a curl equivalent and to get curl you have to go to a page with pop-up ads and download some other dependencies on top of it. Windows doesn't ship with a Screen or Tmux equivalent. All of these things are unacceptable.
[ Parent
| on HN ]
Re:A Baseline for Front-End Developers
by MattRogish on Thursday April 12, 2012 @02:45PM
(#3833679)
Played with Win7 today in a VM, trying to test IE stuff - you can't even drag the command line window handle to make it bigger. Your options are taller window or full screen, but the text just gets larger. Pure garbage. Glad I switched to OSX a long long time ago (Linux is also equally awesome, but I like the hardware/software integration Apple gives me).
This is possible to do, but you need click on the icon in the top left corner and then properties. Full instructions here: http://stackoverflow.com/a/319317/478893.
You can also do this by running a third-party console app.
As a post earlier in the thread indicates, you can often do the same things on Windows but it requires a little extra work.
Literally every third-party console app sucks, though. Making it even harder is that the terminal emulators available through cygwin are bad, too.
Last time I needed to use Windows, I installed sshd in Cygwin and used Penguinet to connect to localhost. It was that bad.
For what it's worth, I find Console2 tolerable.
First thing, if you're required to use a Windows workstation, is install Cygwin, and I really like puttycyg[1] as a terminal.
One fairly simple install gives you all the basic unix utilities, and almost anything else, yes even X11 stuff, is available in a fairly usable click-to-install management interface.