I'm not sure "washed up" is the right term. Considering the ratings he was pulling, you might think he retired the show to lets the others have a chance at some viewers. He probably just wanted the show to go out on top, which it did. Other TV shows made jokes about how empty the streets were when Seinfeld was on or how out of touch people were if they didn't recognize the latest Seinfeld meme.
But to be fair, the black Macbook will heckle him really hard and he won't mean what he says. He'll just be saying it to lash out at the Macbook in anger, because he actually has plenty of black laptops among his friends.
One of my best friends (a coworker at the time) had the final release candidate for Windows 98 running flawlessly on his PC. When the retail box came out, he ran out and bought it. It didn't work. It flat out refused to recognize his SCSI adapter properly.
This paragraph is for anyone who doesn't know what a "Release Candidate" is, like the Windows 98 development team. A Release Candidate is supposed to be past alpha and past beta. A Release Candidate is the code you put out to test broadly to see if it's ready to be released, hence the name. You only change what's actually broken and don't change any features. You make sure everyone who could use the previous Release Candidate can still use the current one and that the problems you fixed are actually fixed for the users who experienced them. Then, when you have no credible bug reports that your users submit from testing, you make that last Release Candidate the release version. Then if anything is broken, it's because not anyone in the whole Release Candidate testing program would have been affected and you just didn't think of that configuration at all.
Now, would someone -- anyone, anywhere -- after ten years please explain to me how the hell the final release candidate worked and the released retail boxed version did not work? I'm still at a loss how that happens when the development team actually knows what the hell a release candidate is.
IIRC, the word on the tribute shows and fan sites has always been that damn near everything in the apartment was there because Seinfeld had one just like it at home.
The boxes of cereal in his cabinets were the brands he ate. The fruits Kramer mooched from his fridge were the fruits he'd have at home. He was known for supporting products, characters, and shows on his show that he actually used, admired, or watched. He's a huge Superman fan IRL, for example.
I'm not sure why I remember this, because I think the show was funny (and still watch the occasional syndicated airing on the CW) but I was never a diehard fan. I might not be recalling correctly, but it'd be an odd thing to remember for no reason.
"If you like C++, fine. Good for you. But accept that some people prefer other languages." ???
Um, wait. Isn't that what I just said to you?
You're judging languages based on the number of libraries readily at hand. All I suggested is that if that's your killer stat, you might want to consider a language with better numbers on that axis.
CPAN is not a window system and development toolkit. CPAN is a module archive network, similar to (and the inspiration for) PyPi. There are over 12,200 module distributions on it. Pypi has 4583 packages.
A quick search on Google didn't give me a strong idea of how many public Pypi mirrors there are, but CPAN has over 250. There are tools to make local bundles of module distributions, or even grab the latest version of every module distribution and keep them in sync for when you have to forgo connectivity, too.
If you're going to cite metrics as a justification, be prepared to enumerate and defend your metrics. There are C and C++ libraries available for damn near everything. Your language might centralize access to libraries a bit better, but it doesn't do that as well as Perl.
I'm all for you continuing to work in Python. I personally don't care for the language much as a personal preference. I like many of the projects people who enjoy coding in Python produce, though. If you can fix stuff that irks me in PySol, that's great because then I don't have to.;-)
This is exactly the type of "harmful government interference" the small ISPs were all glad to have the big network players like AT&T and Verizon fight against.
Then, towards the end of viability for most small ISPs, they realized that AT&T telecom division being guaranteed to have to charge the same rates to AT&T's internet service division for line access as what they'd charge a competitor didn't mean much when AT&T offered huge volume discounts -- but mostly on volumes only AT&T internet service division would need.
The small ISPs were the death of the small ISPs. They were the flies happy to play in the telecom company webs so long as The Bad Ole Guvmint didn't tell them what to do.
I'm sure there are parts of your native natural language you don't fully understand. There's too much to know in most languages that anyone would know all the vocabulary, tenses, voices, spellings (especially with ideographs), idioms, slang, connotations, and etymologies perfectly without a reference or at least a doctorate in the language. Yet we tend to use subsets of the natural languages very effectively. Some people have massively larger subsets of their native natural language mastered than others and still they use a reference from time to time.
To be fair, the majority of complaints you hear about most programming languages on Slashdot are complete bull. People complain about the ones they don't like or don't know well enough and praise the ones they do like.
Once in a while you'll get someone who admits their pet language has faults and warts who explains why they use it anyway. On rare occasions, you might even hear someone say that a language they dislike has their language beat in some way or another. None of these are the rule, though.
Personally, I think of the C family of languages as an actual family... The patriarch C is somewhat portable macro assembly all grown up with some new tricks his dad never knew. C++ is C's little brother on steroids, complete with the unsightly rippling veins and man boobs. Java is C++ castrated and off the juice. Perl is the awkward bastard child of C and sed with a great skill for vocabulary but a wild of ADHD. C# is Java's soap-opera style evil twin. Objective C is C++'s hot female tree-hugging cousin from northern California who can't quite understand why the family always bickers and can't just get along. D kind of married into the family (probably to Objective C) and brought in a bunch of non-C things back to a style that suits C pretty well, even if he is a young punk. Cmm is the weird survivalist uncle none of C's kids, nieces, and nephews really want to spend time with at the holidays.
It's a pretty dysfunctional family, but on some level they all belong together. They're not as sophisticated as the Lisp family down the street. They don't coordinate as well as the Concurrents. The Pascal and Modula clan talks a lot more and is stricter with their rules. The C family just keeps getting useful work done, though, and that's why people keep coming back to them.
My primary language is Perl, but then again I'm an awkward guy with a gift for vocabulary and a wild case of ADHD. At least I know who my father is.
I used to think like that, but then all the things you talk about are just syntactic sugar. There is nothing you can do with a compiled language that you can't do in an assembled or directly executable one.
Beware the Turing Tarpit. Just because all Turing-complete languages can be used to create equivalent programs does not mean they take an equivalent amount of effort.
If your mantra is "give me more libraries" then perhaps you should look into Perl and CPAN. Let the C++ folks have their language. You're not going to convince them to use Python instead of C++ any more than you're going to be convinced to use C++ or Perl instead of Python.
There's the rub. If it's not written in both, how do you know C++ is faster? By intuition? I think the one best lesson a code profiler can teach you is that intuition is often wrong.
I'm not sure what part of my post you read and saw the words "emulation", "emulate", or even "virtual". It's quite possible to compete with an x86 without using the x86 ISA in any way. I was implying that someone at Inq got their facts wrong (as usual).
It was a little tongue-in-cheek. I do believe 4.1.x isn't quite ready to take over from the 3.5.x line.
I am actually running a patched 3.5.7 right now, though. Mandriva One 2008.0 is the distro. The base KDE packages are listed as 3.5.7-38.3mdv2008.0 and there are packages for 4.0 RC2. It's my main business desktop, so I'm a little conservative with it and let the repositories and automatic updates take care of most of my software. The only things I update outside of those tools are browsers, programming tools, some graphics stuff, and my kernel.
My home box some more recent stuff for playing around, but at work I need to make sure I'm not spending more time compiling my productivity stuff than actually doing work.
Well, maybe they're making a chip that competes with the x86 that doesn't require an x86 chipset. That could mean it's a system-on-chip design. It could mean it's a MIPS, ARM, or Sparc design -- all of which compete with x86 within certain segments.
It could also be that the rumor about exiting the chipset business was just a rumor, too. It's more likely that the rumors about Via leaving the AMD and Intel chipset business and focusing on chipsets for their own processors is true than the rumor about NVidia leaving the chipset business.
Slashdot Mirror
Why in the world would you point out to a man who calls himself "CrazyJim1" that he might not be right in the head? Is it really necessary?
I'm not sure "washed up" is the right term. Considering the ratings he was pulling, you might think he retired the show to lets the others have a chance at some viewers. He probably just wanted the show to go out on top, which it did. Other TV shows made jokes about how empty the streets were when Seinfeld was on or how out of touch people were if they didn't recognize the latest Seinfeld meme.
But to be fair, the black Macbook will heckle him really hard and he won't mean what he says. He'll just be saying it to lash out at the Macbook in anger, because he actually has plenty of black laptops among his friends.
Microsoft would spend $500m to sue them into oblivion? Am I right? Can I haz cheezburger?
One of my best friends (a coworker at the time) had the final release candidate for Windows 98 running flawlessly on his PC. When the retail box came out, he ran out and bought it. It didn't work. It flat out refused to recognize his SCSI adapter properly.
This paragraph is for anyone who doesn't know what a "Release Candidate" is, like the Windows 98 development team. A Release Candidate is supposed to be past alpha and past beta. A Release Candidate is the code you put out to test broadly to see if it's ready to be released, hence the name. You only change what's actually broken and don't change any features. You make sure everyone who could use the previous Release Candidate can still use the current one and that the problems you fixed are actually fixed for the users who experienced them. Then, when you have no credible bug reports that your users submit from testing, you make that last Release Candidate the release version. Then if anything is broken, it's because not anyone in the whole Release Candidate testing program would have been affected and you just didn't think of that configuration at all.
Now, would someone -- anyone, anywhere -- after ten years please explain to me how the hell the final release candidate worked and the released retail boxed version did not work? I'm still at a loss how that happens when the development team actually knows what the hell a release candidate is.
IIRC, the word on the tribute shows and fan sites has always been that damn near everything in the apartment was there because Seinfeld had one just like it at home.
The boxes of cereal in his cabinets were the brands he ate. The fruits Kramer mooched from his fridge were the fruits he'd have at home. He was known for supporting products, characters, and shows on his show that he actually used, admired, or watched. He's a huge Superman fan IRL, for example.
I'm not sure why I remember this, because I think the show was funny (and still watch the occasional syndicated airing on the CW) but I was never a diehard fan. I might not be recalling correctly, but it'd be an odd thing to remember for no reason.
Better yet, Newman. Or Bana.
"If you like C++, fine. Good for you. But accept that some people prefer other languages." ???
Um, wait. Isn't that what I just said to you?
You're judging languages based on the number of libraries readily at hand. All I suggested is that if that's your killer stat, you might want to consider a language with better numbers on that axis.
CPAN is not a window system and development toolkit. CPAN is a module archive network, similar to (and the inspiration for) PyPi. There are over 12,200 module distributions on it. Pypi has 4583 packages.
A quick search on Google didn't give me a strong idea of how many public Pypi mirrors there are, but CPAN has over 250. There are tools to make local bundles of module distributions, or even grab the latest version of every module distribution and keep them in sync for when you have to forgo connectivity, too.
If you're going to cite metrics as a justification, be prepared to enumerate and defend your metrics. There are C and C++ libraries available for damn near everything. Your language might centralize access to libraries a bit better, but it doesn't do that as well as Perl.
I'm all for you continuing to work in Python. I personally don't care for the language much as a personal preference. I like many of the projects people who enjoy coding in Python produce, though. If you can fix stuff that irks me in PySol, that's great because then I don't have to. ;-)
This is exactly the type of "harmful government interference" the small ISPs were all glad to have the big network players like AT&T and Verizon fight against.
Then, towards the end of viability for most small ISPs, they realized that AT&T telecom division being guaranteed to have to charge the same rates to AT&T's internet service division for line access as what they'd charge a competitor didn't mean much when AT&T offered huge volume discounts -- but mostly on volumes only AT&T internet service division would need.
The small ISPs were the death of the small ISPs. They were the flies happy to play in the telecom company webs so long as The Bad Ole Guvmint didn't tell them what to do.
I'm sure there are parts of your native natural language you don't fully understand. There's too much to know in most languages that anyone would know all the vocabulary, tenses, voices, spellings (especially with ideographs), idioms, slang, connotations, and etymologies perfectly without a reference or at least a doctorate in the language. Yet we tend to use subsets of the natural languages very effectively. Some people have massively larger subsets of their native natural language mastered than others and still they use a reference from time to time.
To be fair, the majority of complaints you hear about most programming languages on Slashdot are complete bull. People complain about the ones they don't like or don't know well enough and praise the ones they do like.
Once in a while you'll get someone who admits their pet language has faults and warts who explains why they use it anyway. On rare occasions, you might even hear someone say that a language they dislike has their language beat in some way or another. None of these are the rule, though.
Personally, I think of the C family of languages as an actual family... The patriarch C is somewhat portable macro assembly all grown up with some new tricks his dad never knew. C++ is C's little brother on steroids, complete with the unsightly rippling veins and man boobs. Java is C++ castrated and off the juice. Perl is the awkward bastard child of C and sed with a great skill for vocabulary but a wild of ADHD. C# is Java's soap-opera style evil twin. Objective C is C++'s hot female tree-hugging cousin from northern California who can't quite understand why the family always bickers and can't just get along. D kind of married into the family (probably to Objective C) and brought in a bunch of non-C things back to a style that suits C pretty well, even if he is a young punk. Cmm is the weird survivalist uncle none of C's kids, nieces, and nephews really want to spend time with at the holidays.
It's a pretty dysfunctional family, but on some level they all belong together. They're not as sophisticated as the Lisp family down the street. They don't coordinate as well as the Concurrents. The Pascal and Modula clan talks a lot more and is stricter with their rules. The C family just keeps getting useful work done, though, and that's why people keep coming back to them.
My primary language is Perl, but then again I'm an awkward guy with a gift for vocabulary and a wild case of ADHD. At least I know who my father is.
I used to think like that, but then all the things you talk about are just syntactic sugar. There is nothing you can do with a compiled language that you can't do in an assembled or directly executable one.
Beware the Turing Tarpit. Just because all Turing-complete languages can be used to create equivalent programs does not mean they take an equivalent amount of effort.
Hopefully C++'s revision is better than the crapfest that is "D&D" > 2.0.
FTFY.
If your mantra is "give me more libraries" then perhaps you should look into Perl and CPAN. Let the C++ folks have their language. You're not going to convince them to use Python instead of C++ any more than you're going to be convinced to use C++ or Perl instead of Python.
There's the rub. If it's not written in both, how do you know C++ is faster? By intuition? I think the one best lesson a code profiler can teach you is that intuition is often wrong.
I'm not sure what part of my post you read and saw the words "emulation", "emulate", or even "virtual". It's quite possible to compete with an x86 without using the x86 ISA in any way. I was implying that someone at Inq got their facts wrong (as usual).
It was a little tongue-in-cheek. I do believe 4.1.x isn't quite ready to take over from the 3.5.x line.
I am actually running a patched 3.5.7 right now, though. Mandriva One 2008.0 is the distro. The base KDE packages are listed as 3.5.7-38.3mdv2008.0 and there are packages for 4.0 RC2. It's my main business desktop, so I'm a little conservative with it and let the repositories and automatic updates take care of most of my software. The only things I update outside of those tools are browsers, programming tools, some graphics stuff, and my kernel.
My home box some more recent stuff for playing around, but at work I need to make sure I'm not spending more time compiling my productivity stuff than actually doing work.
Sorry, but I care more about getting the work done than the physical beauty of the code.
Try making the same data structure in COBOL, ISO Pascal, C, or Ada and get back to me about how ugly it is.
It's 11 years closer to coming out than it used to be...
Why in the world would you want it to? KDE 3.5.7 FTW for now. KDE 4.4 maybe. Maybe.
They didn't make that announcement and demanded a retraction. This is just a rumor for now, too, and they may very well do the same.
Maybe they can, if we're lucky, get the Alpha processor freed up in the process. I know, whichful thinking...
IBM used to, but I'm not sure about now. Via does. I don't know that Transmeta, Via, or IBM have any rights of relicensing, though.
x86 is basically free for the taking. MMX, SSE, SSE2, SSE3, 3dNow!, and x86-64 are not.
Well, maybe they're making a chip that competes with the x86 that doesn't require an x86 chipset. That could mean it's a system-on-chip design. It could mean it's a MIPS, ARM, or Sparc design -- all of which compete with x86 within certain segments.
It could also be that the rumor about exiting the chipset business was just a rumor, too. It's more likely that the rumors about Via leaving the AMD and Intel chipset business and focusing on chipsets for their own processors is true than the rumor about NVidia leaving the chipset business.