Alright, folks. Where is it? I'm looking for a single Web page, designed with FrontPage 2002, that describes this EULA and says it's stupid. A wonderfully self-referential violation.
For a while back in the mid-90's I was at Amaze!nc, which produced the Bloom County screensaver. We would occasionally have Mr. Breathed come by the offices to work on the project. Not only were the screensavers hilarious (we even got sued for the one where Opus shoots down the flying toasters =), but Berke himself was a very nice guy, perfectly willing to take suggestions and laugh out loud with animation interns, just out of college with no corporate power of their own.
-Dug
Re:Funny or not, it really makes you think...
on
Windows in 2020
·
· Score: 1
I don't think it is - the problem is finding the best protocol to use to let computers talk to each other. The OS is several levels above this, and standardising on the OS is like standardising on a singe type of cell phone.
But won't the OS of today be the protocol of the future? If we programmers are going to be getting anywhere, we're going to have to keep building on top of what's been already done. I no longer use assembly, many Web designers now know very little HTML -- folks are always building on what was made in the past.
And if they can all build on a common base (TCP/IP now, an OS in the future), it'll mean more and better things get done.
Slashdot Mirror
Alright, folks. Where is it? I'm looking for a single Web page, designed with FrontPage 2002, that describes this EULA and says it's stupid. A wonderfully self-referential violation.
Any takers?
For a while back in the mid-90's I was at Amaze!nc, which produced the Bloom County screensaver. We would occasionally have Mr. Breathed come by the offices to work on the project. Not only were the screensavers hilarious (we even got sued for the one where Opus shoots down the flying toasters =), but Berke himself was a very nice guy, perfectly willing to take suggestions and laugh out loud with animation interns, just out of college with no corporate power of their own.
-Dug
I don't think it is - the problem is finding the best protocol to use to let computers talk to each other. The OS is several levels above this, and standardising on the OS is like standardising on a singe type of cell phone.
But won't the OS of today be the protocol of the future? If we programmers are going to be getting anywhere, we're going to have to keep building on top of what's been already done. I no longer use assembly, many Web designers now know very little HTML -- folks are always building on what was made in the past.
And if they can all build on a common base (TCP/IP now, an OS in the future), it'll mean more and better things get done.
-Dug