So write to your congressman, telling them that spam is a big issue for you. Also tell them that a method is required for secure and verifiable form of email that does not depend on a standard or API controlled by someone with commercial interests.
Continue by talking about the benefits that email has for commercial and personal relations.
Advocate a patent and license free system based on existing RFCs.
Your contention is that copyrights only harm culture, apparently because they limit the ability for a person to experience it. If that were true, your comparison to the 1830s slavery conflict would be appropriate.
However, in my opinion, copyrights, when applied appropriately, can extend culture. When combined with an appropriate business model(which isn't the way the RIAA/MPAA are handling things), they can simultaneously help artists continue to produce, while exposing everyone else to their work.
The artist deserves to be paid. He puts a lot of work into making a recording sound exactly as he wishes to express himself.
The consumer, on the other hand, shouldn't be the one paying. That does have detrimental effect on culture through limiting exposure.
The best solution I've seen so far is to use a website to promote artists' work, and use advertising and other revenues from that website to pay the artists.
Hopefully, a large portion of the consumer base is going to get pissed off when they discover they have to purchase their content again every time they upgrade their computers. Or have their faulty laptop exchanged. Or whatever.
The only non-Orwellian solution I can see is to allow TCPA keys to be transferred on something like a secure key fob. That would be useful, because it would mean I could carry my keys around with me, and use them wherever I go.
Of course, such a convenient solution would have to have legislation supporting it. Otherwise, legislation would get pushed through that restricted it.
If you're writing a JIT-style runtime, you have a couple of options. First, you could compile the whole thing to native code when you start the application. This might be OK for small apps, but for large jobs such as a Java implementation of WordPerfect, it'll take a long time. (Comparable, I suspect, to compiling the gcj runtime.)
The second option is to compile bytecode you encounter to native code, when you encounter it. This means that highly-used code will see the most improvement, but periphery code will actually seem to slow down. A large, complex app, especially if it has a GUI, is going to see serious performance issues if it has a lot of features that are typically only used once or twice while the program is left running.
If you leave the application running for a long time, the features you've already used will have been compiled to native code, so a speed improvement might be noticable. (I say might, since to the user, the overall improvement will have been so gradual that they may not have noticed the change at all.)
However, for small jobs like this scientific number cruncher, your application is small and you'll see a significant improvement in the rate at which numbers are crunched, over a very short period of time. In addition, he's talking about running these applications constantly for an amount of time that would be rediculous if you were talking about a larger application like WordPerfect or Eclipse.
Think about it; with spammers bending over backwards to avoid filters, spam messages are much less likely to cause false hits in content searches than they used to be.
In a strictly mathematical sense, 2U would probably cost more than $300, since you're asking for adjacent units. With random distribution, or distribution that leaves space between boxes for cooling, adjacent units will be harder to come by than a single unit.
"I think that all right-thinking people in this country are sick and tired of being told that ordinary, decent people are fed up in this country with being sick and tired. I'm certainly not! But I'm sick and tired of being told that I am!" -- Monty Python's Flying Circus
I'd completely forgotten about that Onion article. And I wouldn't really advocate going without a TV.
For me, I just find the interactive nature of the Internet much more entertaining. Especially Slashdot.
I've been so consumed with Slashdot recently that all but about 3 of my 1103 comments were from after 10/24/03.
(Nevermind the fact that I don't have an internet connection at home. heh. I write D&D tools in Perl instead.)
As for the evangilism, I agree that the 'soft' approach is best. It's painful when people preach to me...I usually keep my religous views to myself out here in Real Life.
A company (I don't remember what) was trying to sell some of a wetting agent to a fire department I was part of. They demonstrated that it got soot stains out of concrete, got oil off your hands, etc.
They mixed the stuff about at about a 1:5 ration with gasoline, and used a bucket to splash the resulting mixture onto a pile of burning tires. It darned near put it out. It did reduce the temperature of the fire by 2500 degrees Farenhuit.
The faster your bus (at least for HyperTransport), the lower your latency will be. And regardless of the throughput of a drive, added latency is always a bad thing.
Not that I have any experimental data to show, though...
Neither are any of Intels other current x86 offerings. The 64-bit nature of any G5 competitor is irrelevant anyway; 64-bits won't inherently improve your app unless it's the memory/address space you need to tune (read, remove swapping kludges) your app.
In the PC world, 64-bit computing has been bundled with other, arguably more useful features (like an extra 8 GPRs on x86-64), in order to make it available for future usage.
In the Mac world, 64-bit computing is there because Apple chose to stop selling non-64-bit hardware.
Slashdot Mirror
So write to your congressman, telling them that spam is a big issue for you. Also tell them that a method is required for secure and verifiable form of email that does not depend on a standard or API controlled by someone with commercial interests.
Continue by talking about the benefits that email has for commercial and personal relations.
Advocate a patent and license free system based on existing RFCs.
It did. Blockbuster tried it out. Unfortunately, nobody wanted to pay the extra cash required to "rent" them.
Your contention is that copyrights only harm culture, apparently because they limit the ability for a person to experience it. If that were true, your comparison to the 1830s slavery conflict would be appropriate.
However, in my opinion, copyrights, when applied appropriately, can extend culture. When combined with an appropriate business model(which isn't the way the RIAA/MPAA are handling things), they can simultaneously help artists continue to produce, while exposing everyone else to their work.
The artist deserves to be paid. He puts a lot of work into making a recording sound exactly as he wishes to express himself.
The consumer, on the other hand, shouldn't be the one paying. That does have detrimental effect on culture through limiting exposure.
The best solution I've seen so far is to use a website to promote artists' work, and use advertising and other revenues from that website to pay the artists.
Hopefully, a large portion of the consumer base is going to get pissed off when they discover they have to purchase their content again every time they upgrade their computers. Or have their faulty laptop exchanged. Or whatever.
The only non-Orwellian solution I can see is to allow TCPA keys to be transferred on something like a secure key fob. That would be useful, because it would mean I could carry my keys around with me, and use them wherever I go.
Of course, such a convenient solution would have to have legislation supporting it. Otherwise, legislation would get pushed through that restricted it.
If you're writing a JIT-style runtime, you have a couple of options. First, you could compile the whole thing to native code when you start the application. This might be OK for small apps, but for large jobs such as a Java implementation of WordPerfect, it'll take a long time. (Comparable, I suspect, to compiling the gcj runtime.)
The second option is to compile bytecode you encounter to native code, when you encounter it. This means that highly-used code will see the most improvement, but periphery code will actually seem to slow down. A large, complex app, especially if it has a GUI, is going to see serious performance issues if it has a lot of features that are typically only used once or twice while the program is left running.
If you leave the application running for a long time, the features you've already used will have been compiled to native code, so a speed improvement might be noticable. (I say might, since to the user, the overall improvement will have been so gradual that they may not have noticed the change at all.)
However, for small jobs like this scientific number cruncher, your application is small and you'll see a significant improvement in the rate at which numbers are crunched, over a very short period of time. In addition, he's talking about running these applications constantly for an amount of time that would be rediculous if you were talking about a larger application like WordPerfect or Eclipse.
And spam.
Think about it; with spammers bending over backwards to avoid filters, spam messages are much less likely to cause false hits in content searches than they used to be.
In a strictly mathematical sense, 2U would probably cost more than $300, since you're asking for adjacent units. With random distribution, or distribution that leaves space between boxes for cooling, adjacent units will be harder to come by than a single unit.
"I think that all right-thinking people in this country are sick and tired of being told that ordinary, decent people are fed up in this country with being sick and tired. I'm certainly not! But I'm sick and tired of being told that I am!" -- Monty Python's Flying Circus
As another poster pointed out, you don't have to use Qt.
Also, in the interview, they pointed out that Trolltech gets a boost on Win32 sales due to their easy exposure on Linux.
But what will you do when your characters meet? Does your true neutral druid mediate? Or does he disappear into the woodwork?
I know a guy who pronounces it both ways...and he's a Debian developer.
;)
On the other hand, "I pronounce leenux leenux."
I'd completely forgotten about that Onion article. And I wouldn't really advocate going without a TV.
For me, I just find the interactive nature of the Internet much more entertaining. Especially Slashdot.
I've been so consumed with Slashdot recently that all but about 3 of my 1103 comments were from after 10/24/03.
(Nevermind the fact that I don't have an internet connection at home. heh. I write D&D tools in Perl instead.)
As for the evangilism, I agree that the 'soft' approach is best. It's painful when people preach to me...I usually keep my religous views to myself out here in Real Life.
I can't find a link to the /. article, but there was a story about using loopbacks to distant points on a network as a form on non-RAM storage.
I distinctly recall the BOFH coming up with the idea first, though.
Sadly, whether a show is popular or not usually has very little to do with whether it's groundbreaking or otherwise noteworthy.
Granted, I never watched Firefly...I don't have TV.
Does outsourcing jobs in one catagory save jobs in another? e.g. Having Xerox handle internal publishing.
What makes you think it's not true? If not, it seems a pretty well-thought-out hoax.
I'd insist that my grandparents wear them at all times. And I'd set up a monitoring box to dial 911 in case of an emergency.
It's not, perchance, reproduced here: (.)
If you read the article, the town priest decided along with the villagers to allow the scientists to have a go at it before trying religious means.
(Aside from praying, obviously.)
That's similar to power over Ethernet, isn't it? Your energy comes with your data?
Who wants to be cited as the scientist who couldn't solve the mystery?
It reminds me of a biblical story where the king killed all his advisors who couldn't tell him what his dream meant.
Don't laugh. I've seen it done.
A company (I don't remember what) was trying to sell some of a wetting agent to a fire department I was part of. They demonstrated that it got soot stains out of concrete, got oil off your hands, etc.
They mixed the stuff about at about a 1:5 ration with gasoline, and used a bucket to splash the resulting mixture onto a pile of burning tires. It darned near put it out. It did reduce the temperature of the fire by 2500 degrees Farenhuit.
You can be as geeky cool as you want. I've been an unpopular nerd since 2nd grade. And I'm glad. :)
The faster your bus (at least for HyperTransport), the lower your latency will be. And regardless of the throughput of a drive, added latency is always a bad thing.
Not that I have any experimental data to show, though...
Neither are any of Intels other current x86 offerings. The 64-bit nature of any G5 competitor is irrelevant anyway; 64-bits won't inherently improve your app unless it's the memory/address space you need to tune (read, remove swapping kludges) your app.
In the PC world, 64-bit computing has been bundled with other, arguably more useful features (like an extra 8 GPRs on x86-64), in order to make it available for future usage.
In the Mac world, 64-bit computing is there because Apple chose to stop selling non-64-bit hardware.