Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Comment Re:Software? (Score 1) 715

If we were to consider software failures as component failures, this poll would be a non-starter. Software fails daily. Got a 404 lately? Fail. Had to reboot your windows box? Fail. Got the latest "Here you go" or the PDF-exploit worm? Fail. Your spam filter did not catch all of your spam? Fail. Your fancy smartphone froze up and had to be power-cycled? Fail.

Half the software I use does not perform anywhere close to my expectations. I am used to it; I am a software engineer by trade, I write my own bugs, my expectations are remarkably low. As long as I can get by somehow without throwing my computer out the window, I consider it a good day.

Comment Standalone headless devices (Score 1) 715

My wireless routers keep croaking over and dying. Mostly the ones provided by Comcast/Verizon. I think I am on the 4th one in 2-3 years. When another one bites the dust, I pull out my old trusty WRT54G, which still works like a champ.

My print server recently went to the hardware heaven.

Most recently my Roku box started flaking. Not sure what I'll do when that one dies. Can't easily replace that with WRT54G...

Those aren't very complex devices by today's standards. What's going on here? Widespread quality control lapses? Conspiracy to keep me upgrading? The room where all this electronics is located is clean, no excess dust, I am in a fairly cool climate, so the temperature rarely rises to 't-shirt friendly'. I don't abuse/misuse/overclock the devices, even if I could.

Comment Re:What? (Score 5, Interesting) 245

It's actually not uncommon. My current employer has a "no open source allowed without explicit approval by the legal dept, which takes an eternity and is a royal pain, so don't do it unless there's absolutely no alternative" policy. I am not kidding.

One of my previous employers had the same policy. This is not at all uncommon.

A few years ago a company found some of my code on the web. The code was released under an apache-like license. They contacted me because they wanted to buy it, but with a couple of minor modifications and under a different license. Essentially very similar scenario as the situation the OP found himself in. I agreed, made the modifications, and sold the original product plus the mods to them under a different license. I think it was cheaper for them to get the modifications they wanted, and the license they liked than develop the same code themselves.

As for me, I felt that nobody besides that company would have probably wanted those modifications anyway. That's probably not entirely true, but I convinced myself of that so that way I did not feel like I was totally selling out :) The Open Source community probably did not miss much by me not releasing those mods. I treated the modifications as "work for hire", and since I never released them, I avoided most of the possible legal difficulties. The original product stayed under the same license, of course. That company is now one of the 5 largest software companies, so I presume the practice is not unusual.

Comment You are not really getting it, are you? (Score 4, Insightful) 245

There is no legal trick, no dirty tactic. Yes, EULAs are horrible, blah, blah, blah, I agree with all of that. But that is totally beside the point.

The point is that the software is Apple's. Period. They can do whatever they want with it. If they want to sell it, they can. If they want to open-source it, they can. If they want to attach a EULA, they can. If they want to _refuse_ to sell it to you, they can. If they want to bundle it with hardware, they can. If they want to add DRM, they can. Get it? It's theirs. They can do whatever they want.

Now, what can you do? You can: (1) Play by Apple's rules and do whatever their license allows you to do or (2) Feel free to create your own OS. When you create it, it's yours, and you can do whatever you want with it -- sell, refuse to sell, add DRM, not add DRM, etc.

Apple can do whatever they want. You (and psystar, and everyone else) can't do jack besides whatever is allowed by Apple's license. It's that simple. Tough luck.

Comment You guys are missing the point! (Score 5, Insightful) 278

No single entity controls the source of mysql either. It's GPL. If you want to fork it, fork it. You guys are missing the point.

The point is Widenius wants to start a new company, and wants to work off of what mysql, the company (and thousands of volunteers who have contributed to the project) have created over the past N years. He does not care if it goes to Oracle, Microsoft, some made-up nonprofit-ish foundation, or dies. He could really care less about that. He wants to build a company that will make a proprietary product and will make him money.

The thorn in his side, however, is the fact that he can't take the code that was once released as GPL and use it in his proprietary software. He either has to open up his software (which he does not want to do), or else not be able to benefit from all those years worth of effort by mysql AB and others who have contributed to the project.

If the license was just about anything but GPL (apache, BSD, whatever), he could do just that. But he can't.

What, you really think it's all about evil Oracle taking over mysql, and it's not really the license that's a thorn in Wideniuses side? Read a more in-depth analysis by someone who understands the issue a _whole lot better_ than I or just about any of you folks do. Here: http://www.groklaw.net/article.php?story=20091208104422384

Slashdot Top Deals

A list is only as strong as its weakest link. -- Don Knuth