Like SpaceX this is structured to drain your 401k. It's not hard to find how and why. No path to profitability and a structure that makes sure the profits are privatized and the losses public.

I need food in my house.

If you were worth listening to, you wouldn't have needed help to write that comment.

So far US courts have said that person cannot have a copyright.

This might change up in the future, but so far, the prompter is not considered to be a creator.

That comment was about what if that code is later determined to have a copyright apply to it.

I think AI copyright is going to kill Linux. Allowing uncopyrightable code into your project could be determined by a court to destroy your whole license, forcing ALL your code to be released as uncopyrightable and putting GPL-licensed code into the public domain where it can be monetized by corporations without having to give anything back. None of this is how copyright law is supposed to work, but if I've learned one thing about governments and laws and courts it's that they often aren't created for our benefit.

This is a massive automation push after decades of automation pushes. What's worse this is a massive automation push that goes after high paying White collar jobs.

Furthermore this isn't us building a bunch of washing machines and using a bit more water (I say a bit because hand washing only uses less water if you're being careful about how much you use) Facebook's data center is alone or going to use more electricity than every single household in America. And there is a half dozen other companies planning on doing the same or more. And that's before we talk about water usage. Over and over and over again data centers have lied about how much water they use. It is perfectly possible for them to use less water but it costs more so they don't.

So we have a tech that is going to devour middle class jobs while taking all the water and electricity. Also it's going to spew shitloads of poison into the air because when the inevitably crash the power grid they switch over to gas generators.

I think one of the things folks don't realize is that the reason we were able to stay ahead of the automation curve as long as we did is that we had all this land we could keep expanding into and we were building new cities using government money.

Neither of those two things are true anymore. We are out of land. There is land but it's not usable at least not without massive amounts of what can only be described as terraforming. Nobody is going to pay for that. A private business won't make the money back for a century and nobody's going to take that long to get a return on investment and the government can't do anything anymore because we cut all the billionaire taxes and you can't get taxes from the working class because they're broke after four decades of non-stop automation and outsourcing.

We can't just expand our way out of this mess there's nowhere left to expand into. So we are either going to figure out how to create a cooperative society that doesn't constantly fall for moral panics or we're going to start world War 3 blow up absolutely everything and kill half the population maybe the entire population given that we are about the hand the nukes to religious lunatics.

Oh and while this is happening the tax base is going to collapse from the lack of jobs that pay enough to fund governments and you can say bye-bye to the police that maintain some semblance of order in your community. Always remember you're going to run out of bullets before the world runs out of desperate people with nothing to lose

I would not trust ChatGPT to do literally any of those things correctly, as they can all be misinterpreted, and even when I ask AI to answer simple questions it often does that. If I want a timer, I run the timer app on my phone. If I want a reminder tomorrow, I run the calendar app on my phone. There's no question about whether it got the information into it I wanted, because I can see that I put it in there. I don't have to wonder whether the LLM will fail to put the information in, but then confidently tell me it did it correctly, and then tell me I was correct to push back when it didn't do it and I'm late tomorrow. Fuck all of that, all day every day, and anyone who thinks it's an improvement is not only mentally deficient but also training themselves to be even moreso.

There's probably at least a smattering of middle managers here convinced that they "get it" because they read Slashdot. This slashvertisement is aimed at them.

There's a reason for this:
a) the ATA spec has error correction to maintain data in flight.
b) single-devices (e.g. your HDD) has error correction as part of its normal operation.

You can see how well this works by looking up the SMART attributes for any HDD and reading:
195 - Hardware ECC Recovered
184 - End-to-End error / IOEDC (not all drives report this one)
and
204 - Soft ECC Correction

and when shit hits the fan you get:
187 - Reported Uncorrectable Errors

There is no such thing, there never has been, and such a thing is undesirable. We do not want or need a paper which simply repeats claims as they are made. We need the media to compare claims to facts. It's not the media's fault that the reich wing lies more.

It's hard to say, because those courts have usually decided in favor of rights holders, and they are how we got a copyright cartel in the first place.

You don't need RAID anything. Reed-Solomon error-correcting codes are used on every drive compliant with the ATA specification. There's not a 1-1 relationship between bits on the platter, and storage capacity of a drive.

So yeah RAID-6 re-invented RAID-5, which reinvented the HDD that already existed, which reinvented the CD, which reinvented the mechanical tape... do you see how stupid the "literally re-invented" part of what you said actually is?

I'm finding that ZFS is stupid, and I'm thinking about switching to normal dmraid.

Notably, if you really load it up for a while such that it has a chance to fill up its buffers, it doesn't save any I/O for anything else. The whole system just gets punched right in the fucking balls and becomes completely unusable while the cache empties. Maybe there's some way to tune this tendency out of it, but...SANE DEFAULTS!!! If your project doesn't have them, you're a fuckup! Allowing one process to make a system unusable, that's a fuckup!

When you combine that with the raging arrogant attitudes of about 50% of ZFS think-they're-experts and all of the things which ZFS should be able to do which you're told not to do (like rotating a disk from a 3-way mirror as a short term backup strategy) it becomes clear that it's actually a big joke. The proponents say ZFS can do everything, then they tell you not to do thing after thing and it becomes clear it can only do about half of what they claim.

Can you expand on how you think this is supposed to work? ECC is ECC. When it is read is irrelevant especially in the case of HDDs. An unrecoverable error is not blindly passed anywhere, it will be logged by the kernel which would throw an error, and logged in SMART attributes (and is virtually always a precursor to a drive failure). Recoverable errors are just logged in SMART, but do not get passed to the kernel. Critically reading from a HDD does not in any way give you info about its marginal status, nor does it cause a re-write. At best it may find and flag a bad sector (and that is also logged as a SMART attribute), but in general there's no degradation over time of a sector that isn't read on a HDD.

You don't need ZFS to know an unrecoverable error has occurred, and you don't benefit from ZFS when a recoverable one has occurred. Now the exception to this rule is SSDs which need to periodically read to maintain charge. But this was only a problem in the early days where our knowledge of NAND storage was poor, these days SSD controllers do this in the background for the entire drive whether you request the data to be read or not.

I've been using ZFS for decades too on multi TB systems (currently 48TB). I've seen zero correlation between scrubs and errors. I'm curious as to if there's something I've missed here from a technical perspective.