News for hackers. Stuff that matters.
Re:Introducing PackageManagement in Windows 10 by Goladus on Wednesday April 29, 2015 @02:26PM (#9460556)
It's an ssh client. It is robust, easy to install and it works well.

How much energy do you expect me to waste evaluating and choosing new ones when the one I have works just fine the way it is? I have better things to be doing.

Re:Introducing PackageManagement in Windows 10 by astrodust on Thursday April 30, 2015 @03:13PM (#9467031)
This is the poison in the open source world. If you have something that works "well enough" but never evolves, it holds everyone back. The barrier to entry is fairly high for an application like this, so I'm not saying this is an easy thing to fix, but it's worth fixing.

Linux in particular is filled with "well enough" solutions that should be striving to be better. Although there's misfires when controversial things like systemd happen, there has been steady improvement in other areas. Imagine if Nginx had never happened, if NCSA httpd was "good enough"?

The Windows user base deserves better than PuTTY.

Re:Introducing PackageManagement in Windows 10 by Aloha on Friday May 01, 2015 @12:51PM (#9472795)
But whats wrong with PuTTY?, is it missing features?, I mean. like it has full SSH support, its easy to use, and has a non-quirky terminal emulator.. I guess it could have more terminal types, but there are closed source options for that, like Reflections.
Re:Introducing PackageManagement in Windows 10 by Macha on Monday May 04, 2015 @06:42AM (#9485336)
Mostly it seems like overkill to run a ssh server + client to get a local terminal.