Slashdot is powered by your submissions, so send in your scoop


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Re:U.S. Patent 6384822 (Score 1) 94

by Rick the Red (#30350306) Attached to: Copyright and the Games Industry

Id Software is a U.S.-based company. It can't release Doom 3 under any GPL-compatible license until October 2019, when U.S. Patent 6384822 on depth-fail shadowing expires.

Why does it have to be GPL? Why can't they release it under BSD or just make it public domain? What you really mean is that you can't use the code until October 2019 because you won't consider anything but the GPL. I'm assuming you're not bound by U.S. patent law, or the license wouldn't be an issue -- Americans can't use a patent until it expires under any software license.

Comment: Re:Why reduce the DPI instead of using larger font (Score 0, Offtopic) 549

by Rick the Red (#30124176) Attached to: Are There Affordable Low-DPI Large-Screen LCD Monitors?

Windows programs can either let Windows handle things like the minimize, maximize, and close buttons or it can do them itself. Microsoft Office applications have ALWAYS done these themselves, rather than let Windows do it. Their reason is to give Office the latest-and-greatest look and feel, even on older versions of Windows. The downside is that older versions of Office have the older look and feel, even on the newest version of Windows. If you understand why they think this is a Good Thing, please post here because it makes little sense to me. Sure sets a poor example for the other Windows developers.

Comment: Re:The comment may also be complex.. (Score 1) 660

by Rick the Red (#30122140) Attached to: If the Comments Are Ugly, the Code Is Ugly

IMHO the documentation should be written first, and the code should then be written to behave as documented, with the user acceptance tests also based on the documentation. Really, you shouldn't need a requirements document if you start with the user's manual, and if the user can't understand the user's manual they probably won't understand the software and you should re-think your design. IMHO.

Comment: Re:The comment may also be complex.. (Score 4, Funny) 660

by Rick the Red (#30116652) Attached to: If the Comments Are Ugly, the Code Is Ugly

I once coded a function that varied depending on what quadrant (+x,+y; -x, +y; -x,-y; +x,-y) it was in. I couldn't get it to work right in the second quadrant, but finally got it working by chance and said so in my comments. The code worked, but I didn't understand why and said so. Is that bad coding? It worked!

Comment: Re:Nothing to see here, move on (Score 1) 402

by Rick the Red (#30116446) Attached to: Copyright Time Bomb Set To Go Off

This is a prime example of companies failing to recognize what business they're in. The railroads thought they were in the railroad business but they were really in the transportation business. The record labels think they're in the record business but they're really in the entertainment aggregation business. The record labels aggregated musicians for customers and customers for musicians, and this convenience will break down as the artists take their catalogs back. Who wants to go to,,, etc.? Everyone wants to go to one site -- iTunes or Amazon (and we don't want them to be monopolies, either). I hope the artists realize this and go for multiple distribution channels.

After any salary raise, you will have less money at the end of the month than you did before.