Date: Wed, 18 Apr 2007 17:42:48 +0200 From: "=?ISO-8859-1?Q?Jos=E9_Manuel_Molina_Pascual?=" <raistlinmolina@gmail.com> To: "Scott Long" <scottl@samsco.org> Cc: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no>, advocacy@freebsd.org Subject: Re: The sorry state of open source today Message-ID: <bdd6c4b90704180842s21439a65nbbc6b5f1f94306b6@mail.gmail.com> In-Reply-To: <46262C7C.7020908@samsco.org> References: <86slaxlrbd.fsf@dwp.des.no> <46262C7C.7020908@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I've never posted to the advocacy list but as I read the post this guy wrote..... well, no comment. I've only read the chapter "bugs in the free", it seems to me that this gut is the typical "Security by obscurity", this phrase: "Security fixes are indeed benefiting for having the code in the open, but this also has a price: security advisories are issued more often than ever, as everyone can dig for weaknesses" is very clear, in fact it says that is better to get binary code and trust it. I think that what he does not say is that many development languages are going to the "code once run anywhere" paradigm, via intermediate files runnable under a virtual machine (being Java its maximum exponent) or interpreting ASCII code (ruby, Perl, PHP..........), and what it happens with these languages is that the "closed" application you get is by no means closed to those guys who are capable today of look for weaknesses in open source code. It can be argued that for instance Java classes can be obfuscated but this obfuscation can not stop a determined developer, there are very good tools that let you analyze code, it's true that it will take you more time but it can be done, =BFaren't the drivers for the Intel 3945ABG wifi chipset evolving? =BFhas intel released the specs?. This man is the classical example of corporate guy, can't live if the tools he uses aren't provided by IBM, Oracle, Microsoft............... Maybe he's paid by Microsoft. On 4/18/07, Scott Long <scottl@samsco.org> wrote: > Dag-Erling Sm=F8rgrav wrote: > > The subject refers to an editorial by Radu-Cristian Fotescu, which was > > published on the author's own website and in The Jem Report: > > > > http://beranger.org/feature/sorryfeature.php > > http://www.thejemreport.com/mambo/content/view/309/ > > > > The article contains several factual errors regarding FreeBSD. I have > > posted a rebuttal on my blog: > > > > http://maycontaintracesofbolts.blogspot.com/2007/04/sorry-state-of-jem-= report.html > > > > DES > > I'll rebut you're rebuttal =3D-) > > You're absolutely correct about feature-based vs time-based being a > problem. However, KSE was NOT, I REPEAT NOT, the major nor the second > major reason for the FreeBSD 5.x problems. 5.x releases suffered from > the following problems that were much larger and much more immediate: > > - ULE and the modularized scheduler > - PREEMPTION > - ATA > - UFS2 > - Immature locking model, too much Giant > > Now, I'll entertain that the KSE development caused hurt feelings among > some developers, but that was a professionalism issue, not a technical > issue. I also do agree that M:N is a nice academic theory that has run > into real-world roadblocks, and that FreeBSD seems to be better off in > the end with 1:1 threads, just like most other OSes. But KSE was a > stepping stone to get there; without it, who knows when we would have > moved passed libc_r? It was a definitely a painful step, but it would > have been much more painful to not have any alternatives to libc_r. I'm > glad that the project and certain developers in it had the courage to do > it AND to stick with it to resolve the tough problems. > > Scott > > > > _______________________________________________ > freebsd-advocacy@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-advocacy > To unsubscribe, send any mail to "freebsd-advocacy-unsubscribe@freebsd.or= g" > --=20 What is history but a fable agreed upon? In politics stupidity is not a handicap
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bdd6c4b90704180842s21439a65nbbc6b5f1f94306b6>