Burned by Eschewing Best Practices
-
@DustinB3403 said in Burned by Eschewing Best Practices:
So what makes OF worse (or a never use appliance) in comparison to FreeNAS, since that was the original question. What makes OF worse than FreeNAS?
It's not even related.
https://community.spiceworks.com/topic/373443-why-we-recommend-against-openfiler
The issues with OpenFiler are unrelated to the idea of them both being bad.
- OpenFiler is a dead product, no work on it in ~6 years. FreeNAS is alive and well.
- OpenFiler was only ever a one man basement project. FreeNAS has a large hardware vendor behind it.
- OpenFiler is built on a dead OS and hasn't been patched in eons. FreeNAS is based on FreeBSD which is very much alive.
- OpenFiler was fundamentally unstable and would die at random. FreeNAS is stable.
- OpenFiler threatens people who expose them. FreeNAS has nothing to expose.
- OpenFiler has a web interface with no function as it doesn't work. FreeNAS has a working web interface.
- OpenFiler is officially listed as unusable by VMware. FreeNAS is fine with VMware.
- OpenFiler has a known broken iSCSI stack. FreeNAS has a working iSCSI stack.
- OpenFiler made their money selling fixes to their intentionally broken system. FreeNAS has nothing to sell except support.
- OpenFiler support is questionable if it even exists (we tried.) FreeNAS has a large, known support team.
- Both products suffer from being in the Jurassic Park Effect of being a product category that doesn't make sense as you can use their underlying OS better than you can use the packaged product.
That's a lot of differences.
-
@Dashrender said in Burned by Eschewing Best Practices:
What makes OpenFiler worse is that it's broken - or at least that's what I recall hearing. It has a flaw that can just outright lose your data.
Multiple flaws like that, and that's only part of the issue. And what is even worse is that the flaws are known, there is a fix and you only get the fix if you buy it. Paying to have an intentionally included flaw fixed is similar to extortion. It's not just paying for patches, it's paying for patches when the bugs are intentional.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
The reference was already provided by @stacksofplates in the screenshots. The wording is very easy to interpret as "OMG FreeNAS is satan!"
So you admit that I never said it and it is people just making up implications that are not there. The screenshots very clearly say nothing of the sort. The feeling that I have said this is caused by you and others repeating this all the time, then when there is a something that says that idea is bad, people just assume that I meant the product. It's you that has been saying it, not me.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
I said you come across as saying FreeNAS is a bad product, and in the never use category when there are other options such as CentOS or RHEL.
I said it is in a never use category. Find where I said it was a bad product. And don't try to conflate the two as being related as we clearly know that they are not.
The examples that have been provided are only of the later, which I have never disputed.
-
The lumping together of OpenFiler and FreeNAS that people contribute to you Scott I'm sure at this point was a misunderstanding.
But you rattle off a dozen reasons why NAS appliances (software, not hardware) are just a bad idea - and people, those of us who are not you, walk away with the assumption that they are all just bad.
Right or wrong, it's how people feel when they walk away from one of your conversations about it.
-
@Dashrender said in Burned by Eschewing Best Practices:
But you rattle off a dozen reasons why NAS appliances (software, not hardware) are just a bad idea - and people, those of us who are not you, walk away with the assumption that they are all just bad.
A bad idea. But I've been told that I explicitly said that FreeNAS itself is bad above and beyond being a bad idea or having a bad community or having people use it improperly. That I've said it's a bad idea is not in question. That it is a bad product other than that seems to be things that other people have said but keep getting attributed to me. Which happens with a lot of things, all the time. This is a regular problem of "Scott said..." but no one is sure where I said it, but tons of people repeat it. Same thing happened with the moderation issue on SW a few weeks ago, it turned out eventually that it was something that someone else said that I said, in a place that was private that I knew nothing about, and everyone kept repeating that so that I never found out exactly what people even thought that I had said. It's becoming a very common thing. RAID 5 info being repeated with only partial context is another that is treated like that.
-
@Dashrender said in Burned by Eschewing Best Practices:
Right or wrong, it's how people feel when they walk away from one of your conversations about it.
Well of course, most people work on implication instead of what is actually said. That's why marketing works so well, people assume that something is going to be said and even if the marketing doesn't say it, they just assume it to be true. There is no way to fix that.
-
@scottalanmiller said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
I said you come across as saying FreeNAS is a bad product, and in the never use category when there are other options such as CentOS or RHEL.
I said it is in a never use category. Find where I said it was a bad product.
It is very easy to correlate never use = bad product
Even if never use =! bad product
Because if you would never use it, it must be bad in comparison to the alternatives.
-
Here are some thought experiments:
RAID 5 should never be used on a new array of Winchester drives today, given current market available drives and those available since ~2009. Does this imply that RAID 5 itself is bad?
RAID 5 is the only single parity RAID approach that should be used today, surpassing RAID 4 which likewise replaced RAID 3. Does this mean that RAID 3 and 4 are bad, or were bad? Or does it mean that something has surpassed them? What does bad mean in this context?
CentOS 4 is old and deprecated. You should never deploy it. Does this mean that CentOS 4 is bad?
The point here is that in some ways, all of these things can be determined to be good. RAID 5 remains the best RAID for broad use on SSD arrays today and was the top pick for Winchester arrays twenty years ago. Does losing popularity or efficacy in one arena make something that was good, and did not change, bad?
RAID 3 and 4 were the best options, for many things, in their time. Does the invention of something more robust change them from good to bad, even though they themselves did not change?
CentOS 4 was new long ago. Does the fact that it has been replaced and has aged make it bad? Is bad and old the same thing?
Likewise, or similar, FreeNAS itself is a good product, but one that is in a category that makes no sense and should never be used. Does the fact that FreeBSD is better make FreeNAS bad? Is bad an absolute issue or a relative one? Does something turn from good to bad through no action of its own?
-
@DustinB3403 said in Burned by Eschewing Best Practices:
It is very easy to correlate never use = bad product
But it should not happen. That's an implication that does not exist in the statement. You should never use the "almost as good, second best product". But that doesn't make it bad, just not the best.
- Best is always determined by a variety of factors and is relative to the situation.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
Because if you would never use it, it must be bad in comparison to the alternatives.
It must be worse compared to, not bad compared to. And it is, FreeNAS is worse compared to FreeBSD, but better compared to nearly everything else. But it only takes being worse than one to be "Never use."
-
Here is a great example. There is an Olympic runner (he's immortal, bear with me) and he runs in every summer Olympics for a century. Over that time, he never, ever wins the gold. But he wins the silver every, single time. He was never the best, ever. Not once, but we would not call him bad for being the runner up consistently, right? If you wanted the fastest runner, he's never the best bet, he's always fast but never on top.
FreeNAS and RAID 5 (under the Winchester new array conditions) are like that. Sometimes they are second best for a scenario but never first. Because of good decision making, we rule out a known secondary player because we don't want to accidentally consider something we know isn't the right answer to make picking the right answer easier and to not waste time on something we know can't be right. But that doesn't mean that it is at the bottom of the heap or bad, only that it is not number one.
-
@scottalanmiller said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
Because if you would never use it, it must be bad in comparison to the alternatives.
It must be worse compared to, not bad compared to. And it is, FreeNAS is worse compared to FreeBSD, but better compared to nearly everything else. But it only takes being worse than one to be "Never use."
Do you see how one could read this statement as FreeNAS is worse than FreeBSD but better than RHEL.
?
-
@DustinB3403 said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
Because if you would never use it, it must be bad in comparison to the alternatives.
It must be worse compared to, not bad compared to. And it is, FreeNAS is worse compared to FreeBSD, but better compared to nearly everything else. But it only takes being worse than one to be "Never use."
Do you see how one could read this statement as FreeNAS is worse than FreeBSD but better than RHEL.
?
Nope, and you can't. It simply doesn't say that. You have, again, come up with an implication not existing in the English and stated it as fact. Just because something is "better compared to nearly everything else" in no way guarantees that RHEL is in the "nearly" category.
This is a common problem I see people take, things like "RAID 5 will fail 51% of the time" turns into "it will die every time." But most and always are totally different things.
-
Do you see how the words say nothing about RHEL whatsoever and in no way say that it is better than everything else? nor do they say always. Only often and most.
-
@scottalanmiller said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
@scottalanmiller said in Burned by Eschewing Best Practices:
@DustinB3403 said in Burned by Eschewing Best Practices:
Because if you would never use it, it must be bad in comparison to the alternatives.
It must be worse compared to, not bad compared to. And it is, FreeNAS is worse compared to FreeBSD, but better compared to nearly everything else. But it only takes being worse than one to be "Never use."
Do you see how one could read this statement as FreeNAS is worse than FreeBSD but better than RHEL.
?
Nope, and you can't. It simply doesn't say that. You have, again, come up with an implication not existing in the English and stated it as fact. Just because something is "better compared to nearly everything else" in no way guarantees that RHEL is in the "nearly" category.
This is a common problem I see people take, things like "RAID 5 will fail 51% of the time" turns into "it will die every time." But most and always are totally different things.
But you provide the ambiguity of the statement. You leave it for us to determine what "everything else" is.
This is purely your issue with how you explain a matter. Don't leave any room for interpretation and there wouldn't be issues such as this.
You left the meaning open ended, not I.
Do you believe I'm wrong in being allowed to interpret your statement?
-
@DustinB3403 said in Burned by Eschewing Best Practices:
But you provide the ambiguity of the statement. You leave it for us to determine what "everything else" is.
No, it's open for you to ask. Not the same thing.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
This is purely your issue with how you explain a matter. Don't leave any room for interpretation and there wouldn't be issues such as this.
That's not how that works. At all. Period.
My car runs well, most of the time.
You can't just say "it doesn't run today" and make that fact. My statement is true regardless of if my car works today or does not. And your statement needs to be true on its own. Nothing in my statement gives you the ground to make up your own facts.
This is insanely basic English language stuff.
-
@DustinB3403 said in Burned by Eschewing Best Practices:
Do you believe I'm wrong in being allowed to interpret your statement?
In every possible way. To the point that I have no ability to understand how you could be so wrong. Literally. This is a degree of wrong I actually can't figure out how it could happen.
I want you think about any statement, like this, ever made in the history of the world. You are claiming that unless every possibility, that could ever exist, is explicitly stated that YOU as the unique world defining listener can then inject any statement you want that is not explicitly denied by someone else and claim it to not only be fact, but to be claimed by the speaker?
Example:
Your mother said "I am your mother."
You say "You are also my father and my uncle by the fact that you didn't state that you were not."
WTF
-
@DustinB3403 said in Burned by Eschewing Best Practices:
But you provide the ambiguity of the statement.
It is not actually ambiguous either. You have a misunderstanding of what ambiguity is. It was a very clear statement with a single meaning. It only seems ambiguous to you because you have predetermined that there is another meaning that you yourself created and if I say something that doesn't support what you want me to say, you assume that I am using double speak or word trickery. I am not. My statement is clear, concise and accurate. It doesn't leave any ambiguity or room for interpretation. You can claim that it is wrong, but you can't claim that it is not clear.
