<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>slavapestov</author><text>Here&amp;#x27;s a funny story. At one point bcache development was funded by a startup (which I won&amp;#x27;t name here). They were using it as the local storage layer of a distributed storage product. I worked there for a year in 2014.&lt;p&gt;Apparently they were not aware of the fact that bcache was a) GPLd code, or b) developed before the company existed, first as a hobby project and then at Google. After a couple of years, they noticed that Kent was in fact posting the bcache source code on his personal web site. At this point they fired him and threatened to sue. I quit the company then (along with a number of other people, for mostly unrelated reasons, such as the fact that the CTO was a notorious brogrammer). Kent got a litigator and when it was made very clear to them that they had no case, they backed down, but not before wasting a ton of money.&lt;p&gt;As far as I know, they&amp;#x27;re still actively violating the GPL by shipping a product containing modified kernel code in it without releasing the source, nor do they acknowledge that they did not develop the key component of their product.&lt;p&gt;The &amp;quot;commercial&amp;quot; version had a rather broken and messy snapshots implementation and had diverged a bit from the open source bcachefs at that point, mostly because snapshots were poorly implemented. It&amp;#x27;s also kind of funny because after we left the company we still knew of some tricky data corruption bugs, and it&amp;#x27;s likely they&amp;#x27;re still there in the &amp;quot;commercial&amp;quot; version, because backporting the latest fixes would be non-trivial and I don&amp;#x27;t think their testing or development methodology would have caught them.&lt;p&gt;Anyway, I gave up on startups and enterprise storage after this, but Kent is still developing bcachefs on his own time and money, so if you use it please consider donating some money to support its development.</text><parent_chain></parent_chain></comment><story><title>Bcachefs: “the COW filesystem for Linux that won&apos;t eat your data”</title><url>http://bcachefs.org/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>zanny</author><text>I&amp;#x27;ve been using btrfs since about 2011, and I&amp;#x27;ve stopped using ext4 &amp;#x2F; xfs &amp;#x2F; zfs everwhere since about 2014.&lt;p&gt;From 2012-2014 it was mostly breakage every other month. From 2014-2016, it was semi-annual issues.&lt;p&gt;For the last ~18 months I have had ~30 machines running btrfs with no issues, some servers, some personal computers. The release notes are boring, the bugs are boring, and to me its definitely in a state I would strongly consider trusting it with any workload.&lt;p&gt;I worry that btrfs is just going to remain doomed. It wasn&amp;#x27;t stable half a decade ago, so it - for some reason - cannot be more stable now. But it has seen so much work put into it to make it as mature as it is now, and in my experience it is pretty damn mature now. All I want to see is another year and a half of perfect stability before I would start arguing to drop zfs entirely.</text><parent_chain></parent_chain></comment><story><title>Bcachefs: “the COW filesystem for Linux that won&apos;t eat your data”</title><url>http://bcachefs.org/</url></story>