As soon as someone says "We need X amount of money to do Y", you have to look into exactly who they are and why they need it and what they'll do with it. Those Kickstarter projects that are basically "We'd like to make an indie game that does X" really annoy me. You do? Bugger off and do it then!
I'm one of those developers who is saying "I need X to do Y". Who also just happens to be working on an indie game. Who also just happens to be using Kickstarter to fund our second stage of development. You know why I know what resources I need? I've been working in the startup industry for the last 25 years.
Kickstarter is fairly picky about projects they let in. These days you have to either talk a good game, or really show a working proof of concept. Yeah, a few stinkers get through, but I've backed 21 projects so far, and not a single one has failed (admitedly only 3 are software). YMMV, but don't assume a group of developers are full of it because they're using Kickstarter as a funding option. It's an excellent way to guage interest and spur innovation, even if you've never heard of them before.
Look at the project, determine if it *is* possible based on it's merits and the current technology available, investigate the people involved as much as possible and treat it like a high risk investment that might just get you a t-shirt and a nifty piece of software.
Contact the original owner, and extort them for $50k. It worked so well for Anonymous and Symantec.
Sure the ROMs are running in an emulator on a modern machine, but nothing beats a game of Mule with some friends for nostalgia.
Pulling out an old computer and seeing if I could get a pre-1.0 linux kernel loaded was what I did up until the hardware was finally recycled. Ahh, the days when command line skills really made the geek.
Okay, black boxing is out, but looking over old copies of 2600 is a walk down memory lane.
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.
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.
As a member of the military who has no fear of asking logical questions of his superiors, I asked my Communications Officer why this "ban" was being instated (it hadn't been instated at the time). The answer I recieved was that it was against the UCMJ to look at the material.
That answer is a gross over simplification of the truth, but it is essentially true. As a member of the armed forces, we are required to safeguard the secrets of the United States and prevent their dissemination. Therefore the simple act of viewing one of those documents in a non-secure manner without need to know represents a security spillage, and is essentially against the UCMJ.
As to the *reasoning* behind this, honestly? It probably has more to do with keeping DoD computers free of this material than keeping DoD employee's minds frees of this material. The
The real explanation could be as simple as "Those 55 and older are the ones who can afford to buy the cars in question".
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
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.
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
Haven't heard back from you for a while...
"You can have my Unix system when you pry it from my cold, dead fingers." -- Cal Keegan