Go to the FreeLists Home Page Home Signup Help Login
 



[openbeosnetteam] || [Date Prev] [04-2004 Date Index] [Date Next] || [Thread Prev] [04-2004 Thread Index] [Thread Next]

[openbeosnetteam] Re: libbind.so status

  • From: "Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx>
  • To: <openbeosnetteam@xxxxxxxxxxxxx>
  • Date: Fri, 16 Apr 2004 10:38:46 +0200
> >To put shortly, I concerned about the UNIXification of OBOS code.
> >BeOS was not an UNIX, and I always like the cleaness feeling you get 
> >browsing develop/headers/*.
> >I think it's important for the project to keep control on our public 
> >headers to keep this BeOS *feature* that way.
> >
> >The net kit is more exposed to such issues due to de-facto UNIX origin 
> >of most INET network stuffs...
> >
> >So, let's toss blindly all these headers under private/* subtree!
> >Just kidding :-p
> >But I think we should decide some policy on that topic.
> >
> >What's your opinion, guys?
> 
> As they say in boxing, "Keep it clean".  I am DEFINATELY for keeping the 
> system clean in general.  That is one of the best things about BeOS.  It 
> is small, simple, clean, you can fully understand it, and fix it when it 
> breaks.  This is the thing that made me love this OS (after coming from 
> Linux), and what made me very enthusiastic and committed to this 
> project.  I think our over-riding design and implementation should 
> revolve around:
> 
> 1. Clean
> 2. Simple (where possible)
> 
> If we lose these we cease to be BeOS, and we will just sink into the 
> morass of other ugly UNIX-likes that are already out there!
> 
> That's my two cents worth,

Nice two cents. :)
You are totally right and I cannot disagree with both of you.

Bye,
Waldemar





[ Home | Signup | Help | Login | Archives | Lists ]

All trademarks and copyrights within the FreeLists archives are owned by their respective owners.
Everything else ©2007 Avenir Technologies, LLC.