Follow Slashdot stories on Twitter


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:GPL requires no DRM? (Score 1) 717

by pyrrhonist (#34081864) Attached to: VLC Developer Takes a Stand Against DRM Enforcement

and Best Buy would clearly be responsible for making sure the source code was available

Uh, no. For example, CompUSA used to sell various Linux distributions. They, of course, had a store in Boston that was within walking distance of FSF headquarters. They were not required to provide the source code.

Comment: Re:Pointless battles (Score 4, Interesting) 360

by pyrrhonist (#33558248) Attached to: IE9 Team Says "Our GPU Acceleration Is Better Than Yours"

neither you nor I fixed those bugs, either.

Have you tried fixing any Mozilla bugs? I have and it's a royal pain in the ass. You first post your patch to the bug itself, which is simple enough. Then the main cabal of developers critique your patch, and if it doesn't exactly conform in every possible way to what they would have coded themselves, they will reject it with little, if any, explanation. After you finally get an explanation out of someone, you can continue to submit changes to see if any will appease them. Of course, you will have accidentally violated a minor style guideline, but this won't be pointed out to you until you've submitted changes for their other critiques six times. After you've fixed that issue, they'll think of some other hoop that you'll have to jump through even though the patch fixes all aspects of the defect at this point. After another 16 edits of the three line patch that doesn't have any security implications and doesn't change any portion of the API, they'll ask you for a unit test that wouldn't test anything but the API for which they already have unit tests.

I'm all for being careful and making a stable, secure product, but I expect people to not be completely retarded about the process of writing software. Not even the system that delivers EAMs has a process this annoying for fixing trivial defects.

And *that* is why Mozilla defects don't get fixed for years.

Comment: Not an issue (Score 5, Informative) 300

by pyrrhonist (#31137818) Attached to: Astronauts Having Trouble With Tranquility Module

One has to wonder if this is another imperial/metric snafu.

Probably not. From the article:

The $27 million, Italian-built observation deck sports the biggest window ever flown in space. In all, there are seven windows that will offer 360-degree views.

The 11 astronauts aboard the shuttle-station complex opened the door Friday to the $380 million Tranquility, also made in Italy for the European Space Agency. The door leading from Tranquility into the observation deck was opened soon afterward, and that's when shuttle pilot Terry Virts and Kay Hire encountered the cover problem.

So, now even submitters aren't reading the article? Damn...

"What is wanted is not the will to believe, but the will to find out, which is the exact opposite." -- Bertrand Russell, _Sceptical_Essays_, 1928