Linked by Thom Holwerda on Mon 15th Oct 2007 21:06 UTC, submitted by Valour
OpenBSD "A few weeks ago, the OpenBSD Project announced that the Portable C Compiler had been added to the OpenBSD source tree. There has already been some explanation of why the traditional GNU Compiler Collection is troublesome and why a new compiler is needed, but there are still some details left uncovered. In this interview, Theo de Raadt and Otto Moerbeek of the OpenBSD Project offer more information about PCC and GCC and where they are headed within the project."
Permalink for comment 278486
To read all comments associated with this story, please click here.
RE[4]: ...
by phoenix on Tue 16th Oct 2007 02:33 UTC in reply to "RE[3]: ..."
phoenix
Member since:
2005-07-11

Oddly enough, one of the big reasons why I use Windows is PuTTY. Even when I do use OpenSSH, I learned how to use most of the features on PuTTY. PuTTY has better documentation, a simpler interface (i.e. no need to pull out vi to edit config files or deal with long command line parameters), and seems to behave with non OpenSSH servers better.


PuTTY is available for Linux, *BSD, Windows, and more. Why would you use Windows just for a terminal app when that same app runs on more than just Windows?

Problem with PuTTY is that it uses the Windows registry to store just about everything. Makes it very inconvenient to use on a USB stick. Newer versions tend to use the registry less, but you still leave tracks on every computer you connect from. Not exactly a security conscious development method.

Reply Parent Bookmark Score: 7