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."
Thread beginning with comment 278426
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: ...
by Janizary on Mon 15th Oct 2007 22:21 UTC in reply to "RE: ..."
Janizary
Member since:
2006-03-12

The near monopoly of OpenSSH is not uncontested by open source alternatives, they are all just significantly inferior to the OpenBSD ssh suite.

Reply Parent Score: 12

RE[3]: ...
by MacTO on Tue 16th Oct 2007 01:33 in reply to "RE[2]: ..."
MacTO Member since:
2006-09-21

The near monopoly of OpenSSH is not uncontested by open source alternatives, they are all just significantly inferior to the OpenBSD ssh suite.


Well, people tend to use GCC because the competition (in the open source world) is inferior. By GCC being superior, I mean in a Microsoft sort of way: all of the extensions to the languages and dependence upon the GNU tool chain to build software tends to make it difficult to drop in a third party product.

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.

Reply Parent Score: 3

RE[4]: ...
by phoenix on Tue 16th Oct 2007 02:33 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 Score: 7

RE[4]: ...
by Oliver on Tue 16th Oct 2007 16:35 in reply to "RE[3]: ..."
Oliver Member since:
2006-07-15

>one of the big reasons why I use Windows is PuTTY

Are you aware of the nonsense you're talking of? Are you also aware of the existence of putty in Linux/BSD?

>PuTTY has better documentation

A big, fat LOL.

Reply Parent Score: 2