Home » The PARIS Forums » PARIS: Main » /warning, uber geek/ New code better? 64 bit?
| /warning, uber geek/ New code better? 64 bit? [message #91975] |
Thu, 25 October 2007 13:17  |
TCB
Messages: 1261
Registered: July 2007
|
Senior Member |
|
|
Here's a link to a kernel trap story. It's about linux, of course, so it's
not specifically germane to M$oft or Fruit Based Computing, but if you can
stand the stink of geekdom check it out.
http://kerneltrap.org/Linux/Unified_x86_Architecture_Code_Qu ality
This is _really_ interesting to me for two reasons. First and most, we always
assume that newer code is better. That people learn from their mistakes and
don't make them again. Well, it turns out that writing computer code is like
my dating history--it involves making the same mistakes over and over again.
The new 64 bit architecture code in the linux kernel is actually in worse
shape than the old 32 bit code. Second, even in the uber geek world of free
software, and in the subset of kernel software where only the dweebiest of
angels dare to tread, there are these kinds of errors. Keep in mind that
your status as uber geek Big Swinging Dick is a lot easier to lose when some
16 year old in India can file a bug report and make you look like an ass.
But even in that world there are this many problems per line of code.
Ponder this next time you're wishing for an upgrade to an OS or an application,
not a single line of when you or anyone else will ever see. And you 64 bit
fans, make DAMN sure you dual boot for a while if any serious level of uptime
is important to you life. I'm still not sold on 64 bit for audio _at all_
but for those of you ready to go over the top of the trench and rush the
barbed wire, be careful.
TCB
|
|
|
|
| Re: /warning, uber geek/ New code better? 64 bit? [message #91996 is a reply to message #91975] |
Thu, 25 October 2007 19:18  |
DJ
Messages: 1124
Registered: July 2005
|
Senior Member |
|
|
I've been thinking about rushing the wire, but I'm too busy right now for
such adventures. I may just let Chris Ludwig do it for me and build me a
super box with a monster quad and 8G RAM running Vista 64 and Cubase 4/64.
This would be much easier, eventually cheaper and would make perfect sense
to do. The problem I have with *anyone* else building my boxes is that I
have this compusion to *fix* things that aren't broken and in order to know
(and be absolutely convinced that I know for sure) the definition of
*broken* I usually need to break it in numerous ways..........and actually
go to great lengths to find ways to break it that push the limits of
foolishness and wretched excess. I call it creative destruction....or maybe
it's destructive creation, I'm not sure. I have lived with this condition
my entire life. That's why I don't drink or do drugs anymore....I mean, who
needs that stuff when you've got an inherently nonsensical intellectual
curiousity anyway?
;o)
"TCB" <nobody@ishere.com> wrote in message news:4720f9bd$1@linux...
>
> Here's a link to a kernel trap story. It's about linux, of course, so it's
> not specifically germane to M$oft or Fruit Based Computing, but if you can
> stand the stink of geekdom check it out.
>
> http://kerneltrap.org/Linux/Unified_x86_Architecture_Code_Qu ality
>
> This is _really_ interesting to me for two reasons. First and most, we
> always
> assume that newer code is better. That people learn from their mistakes
> and
> don't make them again. Well, it turns out that writing computer code is
> like
> my dating history--it involves making the same mistakes over and over
> again.
> The new 64 bit architecture code in the linux kernel is actually in worse
> shape than the old 32 bit code. Second, even in the uber geek world of
> free
> software, and in the subset of kernel software where only the dweebiest of
> angels dare to tread, there are these kinds of errors. Keep in mind that
> your status as uber geek Big Swinging Dick is a lot easier to lose when
> some
> 16 year old in India can file a bug report and make you look like an ass.
> But even in that world there are this many problems per line of code.
>
> Ponder this next time you're wishing for an upgrade to an OS or an
> application,
> not a single line of when you or anyone else will ever see. And you 64 bit
> fans, make DAMN sure you dual boot for a while if any serious level of
> uptime
> is important to you life. I'm still not sold on 64 bit for audio _at all_
> but for those of you ready to go over the top of the trench and rush the
> barbed wire, be careful.
>
> TCB
|
|
|
|
| Re: /warning, uber geek/ New code better? 64 bit? [message #91998 is a reply to message #91996] |
Thu, 25 October 2007 19:29 |
Bill L
Messages: 766
Registered: August 2006
|
Senior Member |
|
|
DJ, you're a crack up. The Vedic Hymns describe how everything goes
through the cycle of Creation, Survival and Destruction. Somehow you got
the Create and Destroy all at once. Nice going, Dude!
DJ wrote:
> I've been thinking about rushing the wire, but I'm too busy right now for
> such adventures. I may just let Chris Ludwig do it for me and build me a
> super box with a monster quad and 8G RAM running Vista 64 and Cubase 4/64.
> This would be much easier, eventually cheaper and would make perfect sense
> to do. The problem I have with *anyone* else building my boxes is that I
> have this compusion to *fix* things that aren't broken and in order to know
> (and be absolutely convinced that I know for sure) the definition of
> *broken* I usually need to break it in numerous ways..........and actually
> go to great lengths to find ways to break it that push the limits of
> foolishness and wretched excess. I call it creative destruction....or maybe
> it's destructive creation, I'm not sure. I have lived with this condition
> my entire life. That's why I don't drink or do drugs anymore....I mean, who
> needs that stuff when you've got an inherently nonsensical intellectual
> curiousity anyway?
>
> ;o)
>
> "TCB" <nobody@ishere.com> wrote in message news:4720f9bd$1@linux...
>> Here's a link to a kernel trap story. It's about linux, of course, so it's
>> not specifically germane to M$oft or Fruit Based Computing, but if you can
>> stand the stink of geekdom check it out.
>>
>> http://kerneltrap.org/Linux/Unified_x86_Architecture_Code_Qu ality
>>
>> This is _really_ interesting to me for two reasons. First and most, we
>> always
>> assume that newer code is better. That people learn from their mistakes
>> and
>> don't make them again. Well, it turns out that writing computer code is
>> like
>> my dating history--it involves making the same mistakes over and over
>> again.
>> The new 64 bit architecture code in the linux kernel is actually in worse
>> shape than the old 32 bit code. Second, even in the uber geek world of
>> free
>> software, and in the subset of kernel software where only the dweebiest of
>> angels dare to tread, there are these kinds of errors. Keep in mind that
>> your status as uber geek Big Swinging Dick is a lot easier to lose when
>> some
>> 16 year old in India can file a bug report and make you look like an ass.
>> But even in that world there are this many problems per line of code.
>>
>> Ponder this next time you're wishing for an upgrade to an OS or an
>> application,
>> not a single line of when you or anyone else will ever see. And you 64 bit
>> fans, make DAMN sure you dual boot for a while if any serious level of
>> uptime
>> is important to you life. I'm still not sold on 64 bit for audio _at all_
>> but for those of you ready to go over the top of the trench and rush the
>> barbed wire, be careful.
>>
>> TCB
>
>
|
|
|
|
|
|
|
|
Goto Forum:
Current Time: Sun Nov 24 18:01:40 PST 2024
Total time taken to generate the page: 0.00885 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
