9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Enrico Weigelt <weigelt@metux.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Announce: standalone libixp
Date: Mon,  2 Jul 2007 02:45:46 +0200	[thread overview]
Message-ID: <20070702004546.GC10308@nibiru.local> (raw)
In-Reply-To: <1183332159.10665.3.camel@linux.site>

* Roman Shaposhnik <rvs@sun.com> wrote:
> On Sat, 2007-06-30 at 18:47 +0200, Uriel wrote:
> > Most of your changes don't make any sense to me, pkg-config is at best
> > stupid, and shared libraries are plain disgraceful.
> 
>   I apologize if I already had sent it out, but I'm close to putting
> a petition out there to ban the shared libraries. 

A petition ? Addressed to whom ? 

> http://blogs.sun.com/rvs/entry/what_does_dynamic_linking_and

Starts w/ typical, stupid U$ flaming: $what_I_hate is like communism.
Next logic step would be declaring dynamic linking "unamerican".
Well, those ideas are really irrelevant to me. 

To address some of your points:

* Broken compiler: I don't know which compiler you're talkig about.
  Never ever seen such trouble in recent 15 years.
  An clean namespace separation would have done the trick.
  
* Bug vs. feature: with clean development methods, it's really 
  clear what some module should do. First design, then implement
  and test. If you just hack up something w/o any clear spec,
  you can easily run into trouble. In that case: your fault.
  
* Control over shared code: I *have* control over *all* code on 
  my systems. If necessary, I'm able to lay hands on every module.
  Actually this is only rarely necessary. I'm not dependent on
  some "vendor".

* Commercial or half-Commercial stuff like OO: I'm neither resposible 
  for their unability to produce clean code, nor do I care. If I, for
  some reason get interested in such an package, ie. Mozilla, I just
  break off my own branch and cleanup things as I feel its right.
  This includes kicking off all these bundled 3rd-party libs.


Okay, this was alread too much useless traffic on that issue. 
If you don't like my branch, simply don't use it. But please stop
trying to evangelize me, I'll redirect those efforts to 
/dev/null immediately.

We all have our different destinies and different ways of thinking
or coding. IMHO it's best if we try to learn from each other with
leaving others in peace, instead of wasting resoures by stupid 
conflicts.


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------


  reply	other threads:[~2007-07-02  0:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-30 15:38 Enrico Weigelt
2007-06-30 16:47 ` Kris Maglione
2007-06-30 16:50   ` Kris Maglione
2007-06-30 17:30   ` Enrico Weigelt
2007-06-30 17:41     ` Kris Maglione
2007-07-01 12:50       ` Enrico Weigelt
2007-07-01 16:15         ` Iruata Souza
2007-07-01 10:11     ` Charles Forsyth
     [not found]     ` <dba1bd02516b1cfbf4119d7c567ec8e9@terzarima.net>
2007-07-01 12:42       ` Enrico Weigelt
2007-06-30 16:47 ` Uriel
2007-07-01 23:22   ` Roman Shaposhnik
2007-07-02  0:45     ` Enrico Weigelt [this message]
2007-07-03  3:50       ` Roman Shaposhnik
2007-07-03  4:09         ` Kris Maglione
2007-07-03 15:10         ` Enrico Weigelt
2007-07-03 19:45           ` Federico Benavento
2007-07-03 20:31           ` Jonathan Cast
2007-07-03 21:14             ` Wes Kussmaul
2007-07-03 21:51           ` Martin Neubauer
2007-07-03 23:16             ` Enrico Weigelt
2007-07-04  3:36               ` Iruata Souza

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070702004546.GC10308@nibiru.local \
    --to=weigelt@metux.de \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).