1) Cut the "Emperor of Japan" crap. It doesn't add anything to the discussion.
2) GPL'd code can't be "unGPL'd". One can always take the last version to be released under the GPL and continue your own development based on that version. That's the whole point of the GPL.
I don't think the GPL is any more "intricate" than any of the shrink-wrap licenses you see on non-free software (and, in actual fact, it's a lot easier to read and understand - have you tried reading it?).
For that matter, if you recommend ANY software to your boss without discussing the possible implications of its license, then you're not doing your job properly.
(BTW, your sig is pretty silly - why don't you try changing it to something more interesting?)
Don't you just love the "sue for stepping on my toes" mentality? How about growing up and realizing that [A] rational discussion has solved more problems than the courts ever will, and [B] not everybody in the world is as suit-happy as you are.
Oh, bollocks. If you've seen some of the crap about the Gnome Consortium, etc., coming out of the KDE camp, you'd realise that it was actually very mild. F'chrissakes, Gnome is the FSF's official graphical interface; why shouldn't he encourage them, since many of them started to work on Gnome in response to the KDE licensing problems?
How many people outside of Japan know about the guy who set up a WAP home page that redirected the viewer's phone to 110 (the Japanese phone number for emergency services)? They got 5500 false calls in three months around the country from idiots viewing the page. The guy who made it was arrested the other day for interfering with official services.
Oh, rubbish. You don't have permission to copy it == You're stealing it. The only way this could change is if current copyright law is revised or labels ease up their licenses.
As for your second point, that's like saying "I stole a Ford from the dealer, but I'm sure I'll buy another Ford in the future, so it's not theft."
Actually, no. The P4 has doubled the depth of its instruction pipelines to 20 compared with the 10 of the PIII. However, they haven't put as much effort as they should have into improving their branch preiction, with the result that every time there's a missed prediction, the entire pipeline has to be flushed. This is not good for performance, and will make the P4 slower than the PIII for almost all current applications (clock for clock).
Find me a SCSI harddrive that can match my Maxtor DiamondMax 20 at the same price
Well, if Intel had pushed for onboard SCSI instead of going with IDE, maybe we could be using Ultra160 drives at the price of current IDE drives.
USB was a decent technology that freed up those IRQs.
The technology is OK, but the implementation sucks. Try distinguishing between two mice, two keyboards, or two of anything without unique IDs connected to USB.
USB 2.0 might not be as good as firewire, but do you really want to pay Apple licensing fees?
Stop repeating that bit of misinformation, OK? Licensing fees for Firewire (which are a puny $1 per machine) go to a non-profit consortium formed by companies using Firewire, of which Apple is only one. As for USB 2.0, come back when there's actually hardware available.
As for AGP, I'd really like to see a performance benchmark of PCI vs. AGP.
I've seen such benchmarks; the difference is minimal until you get up to AGPx4. In fact, for most people there is no detectable difference.
for those people with 4MBers, AGP is a godsend.
I'm really not sure what you meant to say here.
They wanted backside cache, and a slot was the only way to do it at the time.
Not true. Apple was able to do it with G3's without moving to a slot architecture.
Slot1 isn't as closed as you think. AMD's license with Intel would have allowed them to use it as well.
Untrue. It was precisely because Intel had the Slot1 specifications locked up with patents that AMD had to select a different bus architecture for the Athlon.
But no, really, it doesn't mean "upgrade". The word you'd use for a (memory) upgrade is zosetsu, or more generally, appugureedo.
To give you a better "feel" for the word, kaizo is made up of the characters "to revise" and "to make". Among similar words using the first character are kaizen ("improvement") and kaishin ("repentment"), as well as kaichiku ("renovation (of buildings)"), kaikaku ("reformation") and kaizan ("tampering", also used for alteration of web pages). Words using the second character include zosen ("ship construction") and kenzobutsu ("building" or "construction").
Basically, you'd use kaizo for something where you were altering an object, but not necessarily improving it; rather, converting it to meet your own needs. It's commonly used to describe the things that young males in Japan do to their cars or motorcycles; adding fins, spoilers, wide wheel wells, etc.
Sorry for the self-response, but it would seem that Google caches searches, because on the third or fourth try, it went from 0.11 seconds down to this:
Google results 1-10 of about 82,300,000 for b. Search took 0.05 seconds.
Maybe I will update my sig - but I'll leave it for later so this thread doesn't become any more pointless than it already is;)
I get told that roughly once every five posts I make, but I think a search time of less than a twentieth of a second is cooler than adding an extra 20 million sites;)
Why do you "seriously doubt" that they did it in Akihabara? It even has photos of the place where they did it. And Akihabara is nowhere as busy as Shibuya, Shinjuku or any of the major business areas in Tokyo. Added to that is the fact that they did it in the evening (after 7:30), when Akihabara is a lot quieter than it is during the day.
They even thank the owner of the bar for letting them use electricity and bring a soldering iron into the bar;)
Yeah. Then there's the people who post to linux-kernel saying things like, "I've been getting these strange oopses - it looks like something's buggy in the memory management", and go on to give a system report that begins "CPU: Dual 300MHz Celerons @ 450MHz..."
Kaizo doesn't mean "upgrade"; it means "alteration" or "modification".
BTW, if you go here you can read the original Japanese (and if you can't read Japanese, you can look at the pictures of the place where they did the modification - a little bar in Akihabara). The hack is more impressive when you realize they did it while getting drunk;)
I think you'll find most authors of music are very supportive of copyright on their music; that's why there was such an outcry when the "work-for-hire" clause was slipped into completely unrelated legislation. The problem isn't so much copyright itself, but rather how that copyright is "leveraged" (an awful bit of business-speak that I detest) to control the distribution of the copyrighted works.
And before you go off ranting about how people "just want to share", remember, "he who writes the code (or in this case, "performs the music") gets to choose the license." Either respect the wishes of the artist or don't listen to their music. You can't have it both ways.
If artists could find another way to distribute their music for sufficient reward, I'm sure they'd leap at it. Unfortunately, most people just want to copy the music for free...
Copying, for your own use, copyrighted material that you have obtained legally has never been illegal. They're trying to make free use look like so-called "piracy", which is a total crock.
Well said. The list of companies I refuse to buy from is long and getting longer every day. What else can you do? Voting with your wallet is the only way for the average Joe to influence corporations (in a small way, certainly; but there's a saying in Japanese - "If dust piles up, it makes a mountain").
There is no way that NVidia has spent "billions" on R&D. Millions, yes - but if the R&D for their last three generations of cards cost more than $100 million in total, I'd be surprised.
Slashdot Mirror
RMS isn't a leader of the "open-source community". He's a supporter of "free software". At least get that much right...
1) Cut the "Emperor of Japan" crap. It doesn't add anything to the discussion.
2) GPL'd code can't be "unGPL'd". One can always take the last version to be released under the GPL and continue your own development based on that version. That's the whole point of the GPL.
I don't think the GPL is any more "intricate" than any of the shrink-wrap licenses you see on non-free software (and, in actual fact, it's a lot easier to read and understand - have you tried reading it?).
For that matter, if you recommend ANY software to your boss without discussing the possible implications of its license, then you're not doing your job properly.
(BTW, your sig is pretty silly - why don't you try changing it to something more interesting?)
Don't you just love the "sue for stepping on my toes" mentality? How about growing up and realizing that [A] rational discussion has solved more problems than the courts ever will, and [B] not everybody in the world is as suit-happy as you are.
Oh, bollocks. If you've seen some of the crap about the Gnome Consortium, etc., coming out of the KDE camp, you'd realise that it was actually very mild. F'chrissakes, Gnome is the FSF's official graphical interface; why shouldn't he encourage them, since many of them started to work on Gnome in response to the KDE licensing problems?
What did you use to download it? Netscape, perhaps? Try using wget instead (or even just plain ftp or ncftp).
How many people outside of Japan know about the guy who set up a WAP home page that redirected the viewer's phone to 110 (the Japanese phone number for emergency services)? They got 5500 false calls in three months around the country from idiots viewing the page. The guy who made it was arrested the other day for interfering with official services.
Now imagine that as a phone virus...
Oh, rubbish. You don't have permission to copy it == You're stealing it. The only way this could change is if current copyright law is revised or labels ease up their licenses.
As for your second point, that's like saying "I stole a Ford from the dealer, but I'm sure I'll buy another Ford in the future, so it's not theft."
Actually, no. The P4 has doubled the depth of its instruction pipelines to 20 compared with the 10 of the PIII. However, they haven't put as much effort as they should have into improving their branch preiction, with the result that every time there's a missed prediction, the entire pipeline has to be flushed. This is not good for performance, and will make the P4 slower than the PIII for almost all current applications (clock for clock).
I think Tyan have a Slot1 baby AT board available (although the last time I saw one was about six months ago).
Just a few points...
Find me a SCSI harddrive that can match my Maxtor DiamondMax 20 at the same price
Well, if Intel had pushed for onboard SCSI instead of going with IDE, maybe we could be using Ultra160 drives at the price of current IDE drives.
USB was a decent technology that freed up those IRQs.
The technology is OK, but the implementation sucks. Try distinguishing between two mice, two keyboards, or two of anything without unique IDs connected to USB.
USB 2.0 might not be as good as firewire, but do you really want to pay Apple licensing fees?
Stop repeating that bit of misinformation, OK? Licensing fees for Firewire (which are a puny $1 per machine) go to a non-profit consortium formed by companies using Firewire, of which Apple is only one. As for USB 2.0, come back when there's actually hardware available.
As for AGP, I'd really like to see a performance benchmark of PCI vs. AGP.
I've seen such benchmarks; the difference is minimal until you get up to AGPx4. In fact, for most people there is no detectable difference.
for those people with 4MBers, AGP is a godsend.
I'm really not sure what you meant to say here.
They wanted backside cache, and a slot was the only way to do it at the time.
Not true. Apple was able to do it with G3's without moving to a slot architecture.
Slot1 isn't as closed as you think. AMD's license with Intel would have allowed them to use it as well.
Untrue. It was precisely because Intel had the Slot1 specifications locked up with patents that AMD had to select a different bus architecture for the Athlon.
Yes, it is a very important distinction. Unfortunately, it doesn't give you the right to steal the artist's work for nothing.
If you saw the way some English speakers use Japanese, you wouldn't be laughing so much...
My angle? Well, he's wrong ;)
But no, really, it doesn't mean "upgrade". The word you'd use for a (memory) upgrade is zosetsu, or more generally, appugureedo.
To give you a better "feel" for the word, kaizo is made up of the characters "to revise" and "to make". Among similar words using the first character are kaizen ("improvement") and kaishin ("repentment"), as well as kaichiku ("renovation (of buildings)"), kaikaku ("reformation") and kaizan ("tampering", also used for alteration of web pages). Words using the second character include zosen ("ship construction") and kenzobutsu ("building" or "construction").
Basically, you'd use kaizo for something where you were altering an object, but not necessarily improving it; rather, converting it to meet your own needs. It's commonly used to describe the things that young males in Japan do to their cars or motorcycles; adding fins, spoilers, wide wheel wells, etc.
Sorry for the self-response, but it would seem that Google caches searches, because on the third or fourth try, it went from 0.11 seconds down to this:
;)
Google results 1-10 of about 82,300,000 for b. Search took 0.05 seconds.
Maybe I will update my sig - but I'll leave it for later so this thread doesn't become any more pointless than it already is
I get told that roughly once every five posts I make, but I think a search time of less than a twentieth of a second is cooler than adding an extra 20 million sites ;)
Why do you "seriously doubt" that they did it in Akihabara? It even has photos of the place where they did it. And Akihabara is nowhere as busy as Shibuya, Shinjuku or any of the major business areas in Tokyo. Added to that is the fact that they did it in the evening (after 7:30), when Akihabara is a lot quieter than it is during the day.
;)
They even thank the owner of the bar for letting them use electricity and bring a soldering iron into the bar
Yeah. Then there's the people who post to linux-kernel saying things like, "I've been getting these strange oopses - it looks like something's buggy in the memory management", and go on to give a system report that begins "CPU: Dual 300MHz Celerons @ 450MHz..."
Kaizo doesn't mean "upgrade"; it means "alteration" or "modification".
BTW, if you go here you can read the original Japanese (and if you can't read Japanese, you can look at the pictures of the place where they did the modification - a little bar in Akihabara). The hack is more impressive when you realize they did it while getting drunk
"Fair pay" for the work involved in making and distributing music:
Artist: Royalty per person for each work (not each copy of that work)
Label: Reasonable compensation for promotional work
Retailer: Profit margin comparable to other products
RIAA: Big, fat ZERO.
I think you'll find most authors of music are very supportive of copyright on their music; that's why there was such an outcry when the "work-for-hire" clause was slipped into completely unrelated legislation. The problem isn't so much copyright itself, but rather how that copyright is "leveraged" (an awful bit of business-speak that I detest) to control the distribution of the copyrighted works.
And before you go off ranting about how people "just want to share", remember, "he who writes the code (or in this case, "performs the music") gets to choose the license." Either respect the wishes of the artist or don't listen to their music. You can't have it both ways.
If artists could find another way to distribute their music for sufficient reward, I'm sure they'd leap at it. Unfortunately, most people just want to copy the music for free...
Copying, for your own use, copyrighted material that you have obtained legally has never been illegal. They're trying to make free use look like so-called "piracy", which is a total crock.
I think he's talking about IE...
Well said. The list of companies I refuse to buy from is long and getting longer every day. What else can you do? Voting with your wallet is the only way for the average Joe to influence corporations (in a small way, certainly; but there's a saying in Japanese - "If dust piles up, it makes a mountain").
There is no way that NVidia has spent "billions" on R&D. Millions, yes - but if the R&D for their last three generations of cards cost more than $100 million in total, I'd be surprised.