Which of Amazon's components are GPL licensed that Amazon does not publish source code for?
MySQL is the obvious example here, since that's what the story is about. They took the source, added some nice clustering mods, and didn't give it back. Now the CEO of MySQL is upset about that.
You're being too emotional about it. "Choose the right tool for the job," that's all that matters. If you don't want people to use the tivo trick, then use GPL 3. If you don't care, then use GPL 2. Figure out what your needs and desires are, and choose the correct license.
Of course, if you don't like the GPL3 then you're a freedom hating corporate tool, but that's just my opinion and irrelevant. You're free to be a cocksucking whore. That's your choice and there's nothing wrong with that.
If MariaDB cared they should have used the AGPL. This has been an issue with open source for a long time now. Solutions are available, and you need to think before using the license.
1) BSD - if you want your code to be used as many places as possible (even if you don't know about it)
2) GPL - If you want to get paid when people use your code, either by keeping it free (redistribution/returning modifications), or by dual-licensing.
3) AGPL - When you want to close the loophole here.
And we can also add that the GPL3 closes the tivo and patent loopholes. Decide what you want, and choose the right license, otherwise you'll end up whining like Michael Howard.
a bare metal setup of the same size (same CPU cores, same RAM amount) will annihilate the EC2 instance on performance and at about half of the TCO over three years, but nobody seems to care about that these days.
I think most people don't know how to set that up, and they are afraid they won't be able to scale.
Fear of not being able to scale seems like the #1 concern in SV these days, but I swear to you for the average startup there are many, many more important problems you have to solve first.
Not only did Apple go from zero to the biggest watchmaker in the world in under two years, but they now outsell the entire Swiss watchmaking industry combined.
You should realize that the Swiss watchmaking industry is not very big. The watch industry is not very big, having been destroyed by the cell phone industry. It's an impressive sounding fact, but a number would give more concreteness and clarity.
. Due to the limitations of distribution methods and storage media of the time software was also far less bloated and much more stable at launch. You couldn't easily patch something post launch like you can now so you had to get it mostly right the first time
The amazing thing is that they are able to do it without at least three different noSQL databases.
There is a legal definition of employee, and it's the only thing that matters. It doesn't matter if "logically, they would be an employee" or "by any reason of common sense they are an employee" or even "you'd have to be daft to think they aren't employees!"
The only thing that matters at all is whether they are legally employees or not.
Perfect security is impossible, and the problem gets worse the further down you go
This limitation is much more often used as an excuse than it is reached. If someone says, "Perfect security is impossible" you better check for SQL injection attacks, because they most likely have them. Better make sure their passwords are encrypted, too.
Deflation is very much not a good thing. That's why central banks pretty much make sure it doesn't happen.
Note that deflation happens so rarely that you can't say much empirically about it. People theorize that it would be worse for the economy (which you did here), but no one actually knows.
Slashdot Mirror
The problem is that the GPL3 and the AGPL are different licenses, and it you want both protections you are in a bit of a bind.
What do you get from GPL3 that you don't get from AGPL? The AGPL is just GPL3 with an extra clause, right?
IBM has great support if you are willing to pony-up a modest $200/month for support.
What do you get for that?
The 'spirit' of the GPL? What is this - poetry class?
No, it's Slashdot, didn't you notice? Enjoy your stay, get an account.
Which of Amazon's components are GPL licensed that Amazon does not publish source code for?
MySQL is the obvious example here, since that's what the story is about. They took the source, added some nice clustering mods, and didn't give it back. Now the CEO of MySQL is upset about that.
You're being too emotional about it. "Choose the right tool for the job," that's all that matters. If you don't want people to use the tivo trick, then use GPL 3. If you don't care, then use GPL 2. Figure out what your needs and desires are, and choose the correct license.
Of course, if you don't like the GPL3 then you're a freedom hating corporate tool, but that's just my opinion and irrelevant. You're free to be a cocksucking whore. That's your choice and there's nothing wrong with that.
We use it in production because it outperforms everything else.
Do you have benchmarks?
Lambda means that you don't have to give a rat's ass about servers.
Whenever someone talks about how they use Lambda, you know their setup is messed up.
They aren't following the spirit of the GPL. They are being anti-social: taking from the labors of others, and not contributing back.
There is no law against being anti-social, so they are free to do it.
If MariaDB cared they should have used the AGPL. This has been an issue with open source for a long time now. Solutions are available, and you need to think before using the license.
1) BSD - if you want your code to be used as many places as possible (even if you don't know about it)
2) GPL - If you want to get paid when people use your code, either by keeping it free (redistribution/returning modifications), or by dual-licensing.
3) AGPL - When you want to close the loophole here.
And we can also add that the GPL3 closes the tivo and patent loopholes. Decide what you want, and choose the right license, otherwise you'll end up whining like Michael Howard.
a bare metal setup of the same size (same CPU cores, same RAM amount) will annihilate the EC2 instance on performance and at about half of the TCO over three years, but nobody seems to care about that these days.
I think most people don't know how to set that up, and they are afraid they won't be able to scale.
Fear of not being able to scale seems like the #1 concern in SV these days, but I swear to you for the average startup there are many, many more important problems you have to solve first.
The Swiss watchmaking industry is actually quite big.
How big?
even today it is hit or miss except for the most sophisticated systems.
I don't know, Google translate does a really, really good job figuring out what I'm trying to write, sometimes even when I write the wrong character.
Not only did Apple go from zero to the biggest watchmaker in the world in under two years, but they now outsell the entire Swiss watchmaking industry combined.
You should realize that the Swiss watchmaking industry is not very big. The watch industry is not very big, having been destroyed by the cell phone industry. It's an impressive sounding fact, but a number would give more concreteness and clarity.
None of that has "blown you away."
I can't think of any type of deployment that involves having the database exposed directly to the internet.
. Due to the limitations of distribution methods and storage media of the time software was also far less bloated and much more stable at launch. You couldn't easily patch something post launch like you can now so you had to get it mostly right the first time
The amazing thing is that they are able to do it without at least three different noSQL databases.
Rewriting it from scratch with today's programmers is almost certainly going to end up with a negative result.
There is a legal definition of employee, and it's the only thing that matters. It doesn't matter if "logically, they would be an employee" or "by any reason of common sense they are an employee" or even "you'd have to be daft to think they aren't employees!"
The only thing that matters at all is whether they are legally employees or not.
Perfect security is impossible, and the problem gets worse the further down you go
This limitation is much more often used as an excuse than it is reached. If someone says, "Perfect security is impossible" you better check for SQL injection attacks, because they most likely have them. Better make sure their passwords are encrypted, too.
Is that song triggering for you?
Try the "Zero Bugs and Program Faster" method.
Well, what kind of problem is it then?
it's the FEELINGS that exclusively matter,
This is something very annoying about the current political climate. People don't even try to find out the truth.
And didn't play it much so the sound quality didn't degrade.
Deflation is very much not a good thing. That's why central banks pretty much make sure it doesn't happen.
Note that deflation happens so rarely that you can't say much empirically about it. People theorize that it would be worse for the economy (which you did here), but no one actually knows.