All the BSL/SSPL ones shouldn't be in an "open source" section. Just change the heading to "source available" or put them with the "vendors".
DeWitt Clause, or can you benchmark %database% and get away with it
11–20 of 93 posts
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#12Interesting. As a SaaS vendor, we do not allow performance testing of the production system. Because, you know, just casually saturating production resources can become very iffy for strange and unexpected reasons. And you will always be able to saturate a system, or a subsystem of the subsystem of the system.
However, we have provided bigger customers, or customer willing to pay for it, with performance testing environments. We have, however, usually survived into the curiosity phase - "just how much to I have to throw at this thing to break it?".
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#13If you want to benchmark for internal reasons you don't publish the results and nobody knows. If you want to make a service to the community, run your benchmarks, download Tor and publish the results anonymously. I don't see what the big deal is? Is this only limited to marketing claims where you post it on your company's website?
Its mainly related to MSSQL and Horracle. Horracle will just use their legal team (which is bigger than their engineers and developers) to bludgeon you over benchmarks.
"This just in Oracle legal team takes down entire Tor Network"
Jokes aside, I'm surprised they're so touchy about these things. They can make plenty of money without it, they can also save plenty of money with less lawyers.
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#14Has either the Dewitt clause or the Dewitt Embrace ever resulted in some kind of legal action? It seems like more of a threat stance to various partners and ecosystem players than anything else.
I think someone from Oracle would be more informed on that matter. JK. On a more serious note, who would dare to displease a multibillion corp with hundreds of lawyers (without being backed by a similar co & lawyers)?
These things become substantially easier when approached correctly.
In this case, never run Oracle software. Not only will it vastly improve your mood during budget season; your developers will be less likely to stab you in your sleep and you will never worry about their primary line of business: lawsuits.
And you don't care how they benchmark.
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#15[deleted]
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#16Interesting. As a SaaS vendor, we do not allow performance testing of the production system. Because, you know, just casually saturating production resources can become very iffy for strange and unexpected reasons. And you will always be able to saturate a system, or a subsystem of the subsystem of the system. However, we have provided bigger customers, or customer willing to pay for it, with performance testing envi…
There's a really big difference between "don't performance test on our hardware that you're sharing with other tenants" and "don't performance test on our software no matter whose hardware it's running on".
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#17It would be quite refreshing if we could have a story in which Oracle are the good guys for once. I'm sure they are at least purchasing some modern-day 'indulgences' by - for instance - donating food to starving north korean elites?
If Oracle ever wants to be the good guys just once, I have an idea for them that's right in their wheelhouse. Step 1: buy grsecurity's kernel hardening patches. Step 2: put said patches in the publicly released UEK source. Step 3: wait for grsecurity to refuse to give them future patches. Step 4: sue grsecurity for imposing further restrictions on the exercise of rights granted by the GPL.
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#18If you want to benchmark for internal reasons you don't publish the results and nobody knows. If you want to make a service to the community, run your benchmarks, download Tor and publish the results anonymously. I don't see what the big deal is? Is this only limited to marketing claims where you post it on your company's website?
How likely is it that one takes an anonymous benchmark published by a noname researcher seriously?
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#19All the BSL/SSPL ones shouldn't be in an "open source" section. Just change the heading to "source available" or put them with the "vendors".
Author of the blog post in question here. Let me clarify: they shouldn't be there because they're not OSI-approved, right? Just wanna get your point here.
(While I understand that BSL/SSPL lack certain liberties, I deemed it okay to mark them as "open source" for the purposes of this post.)
Re: DeWitt Clause, or can you benchmark %database% and get away with it
#20Has either the Dewitt clause or the Dewitt Embrace ever resulted in some kind of legal action? It seems like more of a threat stance to various partners and ecosystem players than anything else.
It does result in cease and desist threats quite often. We have been on the receiving end of one.
Oh! Would love to learn more :—)
As I'm the author of the blog post in question, I can think of including your account there, if you'd like to.