I code computationally intensive number crunching code
I don't know if you care about this, or whatever. But...
I would assume you mean floating point, since that's what most number crunching is in (and also because GCC totally crushes Intel C++ in the area of computationally intensive integer code - that's my big thing). GCC 3.1 is supporting SSE, which (supposedly) increases the fp speed on SSE machines by 10-20%. Of course, if you already have the compilers, I doubt you care (Compaq's compiler is really nice, I rather like it).
And what are you thinking, running heavy fp code on x86 when you have an Alpha?:P
a) It's not ISO C++ compliant code: you should sell them, or throw them out, or burn them, or something.
or
b) It's a regression in GCC. In which case you should report it to the GCC team. They are very concerned with regressions, and work hard to make them go away (the release of 3.1 is currently blocked on a small handful of regressions)
Given that it's a textbook, and textbook code is usually pretty trivial, I'm leaning highly towards (a) as the correct answer.
ISO C++ broke a lot of old (pre-Standard) C++ code. Them's the breaks. But I've written a ~18K line C++ program (using modern features like the STL, dynamic_cast, etc) that runs on egcs 1.1.2 up to gcc 3.0.4, and over half a dozen commercial compilers, including VC7. Portability is entirely possible, it just needs some care, just like it does with C or Perl.
Unless a few of the unimplemented language features have uses that nobody has thought of (not entirely unlikely since this is the first compiler I know of that supports all of them)
The only one I can think of is export. Export is hard, maybe even impossible, to get right. If it could be made to work, it would be amazingly useful. But I'm skeptical export will ever really work, especially in the presense of things like shared libraries.
So while it is worth applauding a product which can handle the entire language, their work is not complete by any means. I sincerely hope they can produce the additional utilities that would make it worth implementing on. It is certainly promising.
They won't. They never have. They don't need to. Other people pay them a *lot* of money to do it. In particular, I know that KAI C++ and Compaq's C++ compiler are both based on EGD. Probably there are 3 or 4 others, at least.
EGD is a damn good optimizing compiler, too. I generates code that beats about anything out there.
My understanding of C++ is that it doesn't define things like how class data is stored, standard name-mangling, etc.
Which, overall, is a good thing. I should note C doesn't either - the C ABIs are specified by systems people. For example, there is a System V ABI for x86, which is basically what all the Unix versions on x86 use.
So I guess that this is a good step towards compiler compatibility, but linking will probably still be a problem.
There is now an official IA-32 C++ ABI. Nobody has done it completely, but GCC and Intel are supposed to converge on it in the future. There has also been an IA-64 C++ ABI since the start, though AFAIK some incompatibilies still remain between different compilers (but they are working on it, I think).
Um, technically 'Archon' would qualify, as it depicts "the killing of human beings or human-like beings by the use of an object as a lethal weapon or hand-to-hand fighting".
I wonder if Super Smash Brothers would as well. Beating the crap out of human-like beings (well, some of them, anyway) with baseball bats, ray guns, bombs, etc. Some of them children, too. No blood, but they certainly sound like they're getting hurt pretty bad.
Collosal Caves certainly would fit in there as well. Damn axe-throwing dwarves...
They just realized that most people hear ".0" and think "unstable".
Which, in the case of Red Hat, is correct. Someone at securityfocus did a graph that showed the number of security bugs found in RH releases, covering 5.x-7.0 or so (this was maybe last year sometime). The x.0 releases had two or three times the number of security problems that the.2 releases had.
I still use Red Hat on my home machine, but I always make a point of avoiding x.0 completely, and only installing x.1 about 3-5 months after it's been released (and then grabbing all the new updates right away). I've been doing this successfully since 5.2, and am often glad for it, for example people I knew who installed 6.0 got screwed by all kinds of nastly problems.
You forget physics, some chemistry, engineering, symbolic logic, and some computer science.
Most computer science, I would say. Every journal that I keep up with (mostly crypto and security stuff) requires TeX or LaTeX, and every paper I've read that was written by people at my university (in NLP, graphics, operating systems, computer languages) was done with TeX. I mostly just see hardcopy, but it's pretty easy to tell the difference between TeX and the various wordproccesors when it's on paper.
I would say virtually all papers in CS coming out of academia or R&D shops are done with TeX. Leaving for Office, essentially, the marketing departments of companies, and marketing departments rarely put out many CS research papers.
Beast Wars and Beast Machines which followed, were incredibly well made and the writing was superb...true continuations of the original series I enjoyed as a kid.
I'm with you all the way, at least on Beast Wars. I was totally nuts about that show my sophomore and junior years of college. In fact, it kind of re-sparked my interest in cartoons in general, and I started getting into anime about 6 months after that. Funny how that works.
Actually, I didn't like Beast Machines at all. I felt it messed with the characters too much, especially Rattrap: when did he become a total coward? Sure, in BW he would complain that "we're all gonna die", but at the end of the day, he was a nasty a fighter as anyone. Oh, well. Not meaning to start a flame war (seriously!), so I'll shut up now.
If I use *vectors* to hold fifteen different types of objects, then I'll be using at least fifteen different vectors and causing fifteen different classes to be generated.
Yes, 15 different classes, but the overhead, in almost all implementations, is very very low, because each of these 15 different classes has most of their code stored in type independant storage.
For example, the map type stores it's stuff in a red-black tree. In the implementations I've seen, the map type just forwards most of it's calls into an internal object that does almost all of the actual work, and which is NOT a template, so only one copy of that code exists. These internal types aren't type safe at all; they rely on the external interface to ensure that they are used safely.
because it's standardized, but that's about the only thing going for it, from a programmer's perspective. (Yes, it's highly optimized, but the API isn't very rich. I like rich APIs!) In other words, build your own string class, and give it a Has-A relationship to the STL string.
I agree, it is missing some stuff. But I suppose it depends on what you're used to. I would much rather use std::string than the C str* functions, and I've never felt particularly constrained by the string API. It's one of those YMMV things, I guess. Personally, I like the simplicity, and I've never run into a problem with anything that couldn't be done easily with std::string and the generic algorithms.
But OTOH if you want to do your own string class that's a Has-A of std::string, go for it. C++ is all about reuse, after all.:)
Also, I hate that Containers change paradigms on you, some places you can use integer indecies, sometimes you have to use iterators - and in my opinion, the line isn't very clearly drawn.
So, always use iterators. That's what they're there for, after all. The operator[] access operations are useful, and I use them a lot with vectors and maps, but all of the generic algorithms use only the core container API and work great.
Really, I think the best advice I can give is this : get to really know an API before you start to use it. Because, if you try to just use the parts of an API that you know and like, you're going to make horrible mistakes. Invest the time to get to know the library well enough to use it the right way. STL is no exception.
Walk around the city (assuming you live in a city). Find free stuff sitting in trash cans or whatever. Take it home. You walk a bunch, and when you find something, you get a little bit of weight training (if it's something sizable).
It's low impact, and you can smoke while you're doing it (so maybe it's not really too good for me after all...)
Just last night I brought home a new coffee table.
I challenge anyone to describe the plot of Akira in a way that is accessible to anyone.
I agree, the movie's plot is a bit hard to follow (ok, understatement there). I highly recommend reading the manga, because:
a) It's looks incredible. Some of the best art I've ever seen. b) You can finally understand what happens in the movie. The movie is basically books 1-3 with the very end that's either made up, or taken from book 6. I'm not sure, as book 6 hasn't been published yet (it was supposed to be out last month but I haven't seen it around yet). c) It's all around good. I mean really good.
The funny thing is, I'm think the original Akira did about all it could to describe the plot. I mean the plot is convoluted, and the manga is easily over 1000 pages long. Telling that in an hour and a half to two hours and having it make sense is something well beyond most directors, including, I'm pretty sure, this one.
and possibly had very painfully unhealthy conditions to contend with.
That, to me, seems like something that reduce population growth.
That still leaves open the possiblity that people had shortened lifespans during that time
True, but we would easily be able to see that. Just count the number of adult bodies that died without any visible wounds, and figure out their ages. Then do the same for sometime farther in the past, and again sometime after the pole shift. If the three are roughly the same, the we're all set. If not, we're fucked. Anyway, it's not like we can really do anything about it either way.:)
Also, if it were really that serious, we would have to see pretty good sized die offs of pretty much everything every few hundred thousand years.
Anyway, my whole point was that nobody (at least according to my geology prof) knows a) how long a pole shift takes - anything between a day and a thousand years, basically, and b) nobody knows if there is any radiation increase at all during this time.
I'm not so bothered by it flipping; I'm bothered by the suggestions that in the process of flipping the field weakens and practically disappears.
It's one thing to think "N is S, and S is now N", it's quite another to think "my compass is useless, and I'm probably going to get cancer from the next solar mass ejection because there's no magnetic field to offset all those high energy particles".
[I'm actually in a class that discussed this last week; hows that for relevance:)]
Humans were around during the last pole flip, and it seems from what we know about how they lived, they did not suffer any ill effects from extra radiation, etc during the transsision time.
You assume that our human actions are what is causing this. We are in a warming period between ice ages and this could very well be completely natural. Without data from the previous ages, we have nothing to base these opinions on other than direct data for the past few decades and some guesswork on geological surveys.
I would have to agree with you there. I have old copies of Popular Science from the 70s and early 80s talking about how we will very shortly be in another ice age, with many experts (possibly that should be "experts") saying things like that the average temperature of the Earth will drop 10 degrees within the next 40 years (or something like that, this was a long while ago, I can't remember the exact figures). That has made me pretty skeptical of assertions such as the person who submitted this story make.
And if someone uses compromised computers on the net to DDOS your server, it is your problem. After all, your end node should be smart enough to deal with it, right?
That isn't a problem smarts can deal with (well, at least in a reasonable sense). Anyway, if those zombie boxen had any smarts to start with, they wouldn't be wasting their bandwidth DDOSing some random server.
I went and saw a talk this afternoon, given by John Peter Barlow (another co-found of EFF) at my school. Someone asked about this, and he had a very good response, one which makes me side with Gilmore on this:
The whole point of the internet is dumb network, smart nodes. If the end nodes aren't smart enough to deal with spam (99.9% is quite easy to identify) and viruses (hello MS, I'm talking to you), then that is the problem of the end nodes, not the network.
<possible flamebait> If I take a bus to downtown and proceed to throw a brick through a store window, is that the fault of the city, for running the bus service? (I know this isn't a particularly good analogy, but it's the best I can come up with on short notice) </possible flamebait>
Actually, it was released in beta form. I have 2-3 copies of W2K for the Alpha, RC2 era or so. Got them in a big box of MSDN CDs that were getting thrown out at work [I just grabbed the whole box in the hope there would be something good:P]
All sorts of network (and other) applications are written in C, even though there certainly isn't any need for performance
I disagree. Hell, Mozilla was painfully slow on 350 Mhz Pentium II until about 0.9.5 or so. That doesn't mean it needed C, of course, but to ignore performance is a bad idea.
(At least, I would place security way above performance!)
On the other hand, if it's secure, but too slow to be of any use, there's no point in it being secure, is there? Fortunately, Perl, Python, O'Caml, and others are fast enough so that it doesn't really matter except in relatively rare cases (media players, etc). I do agree that, for example, my mail client doesn't need to be written in C.
(Try SML or O'Caml, for instance.)
You have a point, but OTOH for most people (including myself), the jump from C/C++/etc -> ML/O'Caml/friends is going to be very long. I do think O'Caml is a good language (and programming in it is as good a mind-expansion excercise as Zen and acid), but it is hard to deal with at first.
Where are Suns being used as something other than a server? Are there business sectors where Sun workstations are common?
They're all over my university. There are still a few SGIs left, but everywhere you look there are Ultra5s (not to mention SS5-SS20s). After all, if you're going to have a support contract with Sun for your server, you might as well deal with them for workstations, too (that is the logic around here, according to the head CS department sysadmin, anyway).
but I'd be willing to bet that Gene was sleeping with Suzuka and Aysha, too. They also edit out any blood for some reason.
Nope, he wasn't (I got the whole thing on DVD last year after seeing it on Cartoon Network). They do edit a lot of weird things, though, including stuff like episode 23, plus scenes in other episodes that help make it make a lot more sense. However, I can understand why they cut ep 23. A cartoon network is the kind of thing that parents will just let their kids watch without seeing what it is first (it's "just cartoons", etc), and I could see them getting it some serious problems if they weren't careful about it. And that particular episode is (intentionally) pretty over the top.
BTW, I disagree with you about the Bebop dub; I really like the choice of voices there.
I just turned 21, and I have that exact same Pikachu on top of my monitor.
Rock on brother! I'm 20 and have a Pikachu pillow (helps my back when I'm doing programming runs). And my 22 year old housemate has a little stuffed Snorlax on his printer, not to mention a shirt and several big posters featuring you-know-what.
I would be interested in a Pokemon poll: love it / hate it / never seen it.
Slashdot Mirror
I code computationally intensive number crunching code
:P
I don't know if you care about this, or whatever. But...
I would assume you mean floating point, since that's what most number crunching is in (and also because GCC totally crushes Intel C++ in the area of computationally intensive integer code - that's my big thing). GCC 3.1 is supporting SSE, which (supposedly) increases the fp speed on SSE machines by 10-20%. Of course, if you already have the compilers, I doubt you care (Compaq's compiler is really nice, I rather like it).
And what are you thinking, running heavy fp code on x86 when you have an Alpha?
compiles under the g++ 2.x series, but not g++ 3)
Then:
a) It's not ISO C++ compliant code: you should sell them, or throw them out, or burn them, or something.
or
b) It's a regression in GCC. In which case you should report it to the GCC team. They are very concerned with regressions, and work hard to make them go away (the release of 3.1 is currently blocked on a small handful of regressions)
Given that it's a textbook, and textbook code is usually pretty trivial, I'm leaning highly towards (a) as the correct answer.
ISO C++ broke a lot of old (pre-Standard) C++ code. Them's the breaks. But I've written a ~18K line C++ program (using modern features like the STL, dynamic_cast, etc) that runs on egcs 1.1.2 up to gcc 3.0.4, and over half a dozen commercial compilers, including VC7. Portability is entirely possible, it just needs some care, just like it does with C or Perl.
Unless a few of the unimplemented language features have uses that nobody has thought of (not entirely unlikely since this is the first compiler I know of that supports all of them)
The only one I can think of is export. Export is hard, maybe even impossible, to get right. If it could be made to work, it would be amazingly useful. But I'm skeptical export will ever really work, especially in the presense of things like shared libraries.
So while it is worth applauding a product which can handle the entire language, their work is not complete by any means. I sincerely hope they can produce the additional utilities that would make it worth implementing on. It is certainly promising.
They won't. They never have. They don't need to. Other people pay them a *lot* of money to do it. In particular, I know that KAI C++ and Compaq's C++ compiler are both based on EGD. Probably there are 3 or 4 others, at least.
EGD is a damn good optimizing compiler, too. I generates code that beats about anything out there.
My understanding of C++ is that it doesn't define things like how class data is stored, standard name-mangling, etc.
Which, overall, is a good thing. I should note C doesn't either - the C ABIs are specified by systems people. For example, there is a System V ABI for x86, which is basically what all the Unix versions on x86 use.
So I guess that this is a good step towards compiler compatibility, but linking will probably still be a problem.
There is now an official IA-32 C++ ABI. Nobody has done it completely, but GCC and Intel are supposed to converge on it in the future. There has also been an IA-64 C++ ABI since the start, though AFAIK some incompatibilies still remain between different compilers (but they are working on it, I think).
You need to have a stable relationship with your programs. It's like dating a girl, except you can sell it later.
:)
I've had relationships like that.
Um, technically 'Archon' would qualify, as it depicts "the killing of human beings or human-like beings by the use of an object as a lethal weapon or hand-to-hand fighting".
I wonder if Super Smash Brothers would as well. Beating the crap out of human-like beings (well, some of them, anyway) with baseball bats, ray guns, bombs, etc. Some of them children, too. No blood, but they certainly sound like they're getting hurt pretty bad.
Collosal Caves certainly would fit in there as well. Damn axe-throwing dwarves...
They just realized that most people hear ".0" and think "unstable".
.2 releases had.
Which, in the case of Red Hat, is correct. Someone at securityfocus did a graph that showed the number of security bugs found in RH releases, covering 5.x-7.0 or so (this was maybe last year sometime). The x.0 releases had two or three times the number of security problems that the
I still use Red Hat on my home machine, but I always make a point of avoiding x.0 completely, and only installing x.1 about 3-5 months after it's been released (and then grabbing all the new updates right away). I've been doing this successfully since 5.2, and am often glad for it, for example people I knew who installed 6.0 got screwed by all kinds of nastly problems.
You forget physics, some chemistry, engineering, symbolic logic, and some computer science.
Most computer science, I would say. Every journal that I keep up with (mostly crypto and security stuff) requires TeX or LaTeX, and every paper I've read that was written by people at my university (in NLP, graphics, operating systems, computer languages) was done with TeX. I mostly just see hardcopy, but it's pretty easy to tell the difference between TeX and the various wordproccesors when it's on paper.
I would say virtually all papers in CS coming out of academia or R&D shops are done with TeX. Leaving for Office, essentially, the marketing departments of companies, and marketing departments rarely put out many CS research papers.
Beast Wars and Beast Machines which followed, were incredibly well made and the writing was superb...true continuations of the original series I enjoyed as a kid.
I'm with you all the way, at least on Beast Wars. I was totally nuts about that show my sophomore and junior years of college. In fact, it kind of re-sparked my interest in cartoons in general, and I started getting into anime about 6 months after that. Funny how that works.
Actually, I didn't like Beast Machines at all. I felt it messed with the characters too much, especially Rattrap: when did he become a total coward? Sure, in BW he would complain that "we're all gonna die", but at the end of the day, he was a nasty a fighter as anyone. Oh, well. Not meaning to start a flame war (seriously!), so I'll shut up now.
If I use *vectors* to hold fifteen different types of objects, then I'll be using at least fifteen different vectors and causing fifteen different classes to be generated.
Yes, 15 different classes, but the overhead, in almost all implementations, is very very low, because each of these 15 different classes has most of their code stored in type independant storage.
For example, the map type stores it's stuff in a red-black tree. In the implementations I've seen, the map type just forwards most of it's calls into an internal object that does almost all of the actual work, and which is NOT a template, so only one copy of that code exists. These internal types aren't type safe at all; they rely on the external interface to ensure that they are used safely.
because it's standardized, but that's about the only thing going for it, from a programmer's perspective. (Yes, it's highly optimized, but the API isn't very rich. I like rich APIs!) In other words, build your own string class, and give it a Has-A relationship to the STL string.
:)
I agree, it is missing some stuff. But I suppose it depends on what you're used to. I would much rather use std::string than the C str* functions, and I've never felt particularly constrained by the string API. It's one of those YMMV things, I guess. Personally, I like the simplicity, and I've never run into a problem with anything that couldn't be done easily with std::string and the generic algorithms.
But OTOH if you want to do your own string class that's a Has-A of std::string, go for it. C++ is all about reuse, after all.
Also, I hate that Containers change paradigms on you, some places you can use integer indecies, sometimes you have to use iterators - and in my opinion, the line isn't very clearly drawn.
So, always use iterators. That's what they're there for, after all. The operator[] access operations are useful, and I use them a lot with vectors and maps, but all of the generic algorithms use only the core container API and work great.
Really, I think the best advice I can give is this : get to really know an API before you start to use it. Because, if you try to just use the parts of an API that you know and like, you're going to make horrible mistakes. Invest the time to get to know the library well enough to use it the right way. STL is no exception.
Agreed.
Walk around the city (assuming you live in a city). Find free stuff sitting in trash cans or whatever. Take it home. You walk a bunch, and when you find something, you get a little bit of weight training (if it's something sizable).
It's low impact, and you can smoke while you're doing it (so maybe it's not really too good for me after all...)
Just last night I brought home a new coffee table.
I challenge anyone to describe the plot of Akira in a way that is accessible to anyone.
I agree, the movie's plot is a bit hard to follow (ok, understatement there). I highly recommend reading the manga, because:
a) It's looks incredible. Some of the best art I've ever seen.
b) You can finally understand what happens in the movie. The movie is basically books 1-3 with the very end that's either made up, or taken from book 6. I'm not sure, as book 6 hasn't been published yet (it was supposed to be out last month but I haven't seen it around yet).
c) It's all around good. I mean really good.
The funny thing is, I'm think the original Akira did about all it could to describe the plot. I mean the plot is convoluted, and the manga is easily over 1000 pages long. Telling that in an hour and a half to two hours and having it make sense is something well beyond most directors, including, I'm pretty sure, this one.
and possibly had very painfully unhealthy conditions to contend with.
:)
That, to me, seems like something that reduce population growth.
That still leaves open the possiblity that people had shortened lifespans during that time
True, but we would easily be able to see that. Just count the number of adult bodies that died without any visible wounds, and figure out their ages. Then do the same for sometime farther in the past, and again sometime after the pole shift. If the three are roughly the same, the we're all set. If not, we're fucked. Anyway, it's not like we can really do anything about it either way.
Also, if it were really that serious, we would have to see pretty good sized die offs of pretty much everything every few hundred thousand years.
Anyway, my whole point was that nobody (at least according to my geology prof) knows a) how long a pole shift takes - anything between a day and a thousand years, basically, and b) nobody knows if there is any radiation increase at all during this time.
I'm not so bothered by it flipping; I'm bothered by the suggestions that in the process of flipping the field weakens and practically disappears.
:)]
It's one thing to think "N is S, and S is now N", it's quite another to think "my compass is useless, and I'm probably going to get cancer from the next solar mass ejection because there's no magnetic field to offset all those high energy particles".
[I'm actually in a class that discussed this last week; hows that for relevance
Humans were around during the last pole flip, and it seems from what we know about how they lived, they did not suffer any ill effects from extra radiation, etc during the transsision time.
You assume that our human actions are what is causing this. We are in a warming period between ice ages and this could very well be completely natural. Without data from the previous ages, we have nothing to base these opinions on other than direct data for the past few decades and some guesswork on geological surveys.
I would have to agree with you there. I have old copies of Popular Science from the 70s and early 80s talking about how we will very shortly be in another ice age, with many experts (possibly that should be "experts") saying things like that the average temperature of the Earth will drop 10 degrees within the next 40 years (or something like that, this was a long while ago, I can't remember the exact figures). That has made me pretty skeptical of assertions such as the person who submitted this story make.
And if someone uses compromised computers on the net to DDOS your server, it is your problem. After all, your end node should be smart enough to deal with it, right?
That isn't a problem smarts can deal with (well, at least in a reasonable sense). Anyway, if those zombie boxen had any smarts to start with, they wouldn't be wasting their bandwidth DDOSing some random server.
I went and saw a talk this afternoon, given by John Peter Barlow (another co-found of EFF) at my school. Someone asked about this, and he had a very good response, one which makes me side with Gilmore on this:
The whole point of the internet is dumb network, smart nodes. If the end nodes aren't smart enough to deal with spam (99.9% is quite easy to identify) and viruses (hello MS, I'm talking to you), then that is the problem of the end nodes, not the network.
<possible flamebait>
If I take a bus to downtown and proceed to throw a brick through a store window, is that the fault of the city, for running the bus service? (I know this isn't a particularly good analogy, but it's the best I can come up with on short notice)
</possible flamebait>
Posting at +2 on purpose. Moderate as you like.
GCC will be going into the crapper as soon as somebody produces a good fast compiler for linux.
Then go buy one from KAI or Intel, if it makes you happy.
2k was never (or at least never released).
:P]
Actually, it was released in beta form. I have 2-3 copies of W2K for the Alpha, RC2 era or so. Got them in a big box of MSDN CDs that were getting thrown out at work [I just grabbed the whole box in the hope there would be something good
All sorts of network (and other) applications are written in C, even though there certainly isn't any need for performance
I disagree. Hell, Mozilla was painfully slow on 350 Mhz Pentium II until about 0.9.5 or so. That doesn't mean it needed C, of course, but to ignore performance is a bad idea.
(At least, I would place security way above performance!)
On the other hand, if it's secure, but too slow to be of any use, there's no point in it being secure, is there? Fortunately, Perl, Python, O'Caml, and others are fast enough so that it doesn't really matter except in relatively rare cases (media players, etc). I do agree that, for example, my mail client doesn't need to be written in C.
(Try SML or O'Caml, for instance.)
You have a point, but OTOH for most people (including myself), the jump from C/C++/etc -> ML/O'Caml/friends is going to be very long. I do think O'Caml is a good language (and programming in it is as good a mind-expansion excercise as Zen and acid), but it is hard to deal with at first.
Where are Suns being used as something other than a server? Are there business sectors where Sun workstations are common?
They're all over my university. There are still a few SGIs left, but everywhere you look there are Ultra5s (not to mention SS5-SS20s). After all, if you're going to have a support contract with Sun for your server, you might as well deal with them for workstations, too (that is the logic around here, according to the head CS department sysadmin, anyway).
And thank god. I fscking hate CDE.
but I'd be willing to bet that Gene was sleeping with Suzuka and Aysha, too. They also edit out any blood for some reason.
Nope, he wasn't (I got the whole thing on DVD last year after seeing it on Cartoon Network). They do edit a lot of weird things, though, including stuff like episode 23, plus scenes in other episodes that help make it make a lot more sense. However, I can understand why they cut ep 23. A cartoon network is the kind of thing that parents will just let their kids watch without seeing what it is first (it's "just cartoons", etc), and I could see them getting it some serious problems if they weren't careful about it. And that particular episode is (intentionally) pretty over the top.
BTW, I disagree with you about the Bebop dub; I really like the choice of voices there.
I just turned 21, and I have that exact same Pikachu on top of my monitor.
Rock on brother! I'm 20 and have a Pikachu pillow (helps my back when I'm doing programming runs). And my 22 year old housemate has a little stuffed Snorlax on his printer, not to mention a shirt and several big posters featuring you-know-what.
I would be interested in a Pokemon poll: love it / hate it / never seen it.