ignirtoq

I don't see how this wouldn't be derivative work. I highly doubt a robust, commercial software solution using AI-generated code would not have modified that code. I use AI to generate boilerplate code for my side projects, and it's exceedingly rare that its product is 100% correct. Since that generated code is not copyrightable, it's public domain, and now I'm creating a derived work from it, so that derived work is mine.

As AI gets better at generating code and we can directly use it without modification, this may become an issue. Or maybe not. Maybe once the AI is that good, you no longer have software companies, since you can just generate the code you need, so software development as a business becomes obsolete, like the old human profession of "computer."

This makes sense to me, and is in line with recent interpretations about AI-generated artwork. Basically, if a human directly creates something, it's protected by copyright. But if someone makes a thing that itself creates something, that secondary work is not protected by copyright. AI-generated artwork is an extreme example of this, but if that's the framework, applying it to data newly generated by any code seems reasonable.

This wouldn't/shouldn't apply to something like compression, where you start with a work directly created by someone, apply an algorithm to transform it into a compressed state, and then apply another algorithm to transform the data back into the original work. That original work was still created by someone and so should be protected by copyright. But a novel generation of data, like the game state in memory during the execution of the game's programming, was never directly created by someone, and so isn't protected.

If it's dangerous to repair it, it's dangerous to own. That's the domain for regulations by the government, not arbitrary software restrictions by software manufacturers.

They don't implement these to keep you safe. They do it purely to make more money.

Before my comment I want to make clear I agree with the conclusion that abortion bans are clearly killing women at statistically significant rates.

That said, the stats reporting here doesn't make sense:

Among Hispanic women, the rate of women dying while pregnant, during childbirth or soon after increased from 14.5% in 2019 to 18.9% in 2022. Rates among white women nearly doubled — from 20% to 39.1%. And Black women, who historically have higher chances of dying while pregnant, during childbirth or soon after, saw their rates go from 31.6% to 43.6%.

There's no way 14.5% of Hispanic women in Texas who got pregnant died some time during pregnancy, during child birth, or soon after. That would be unprecedented for any time since the advent of modern medicine. And the chart above this paragraph does not agree with it either. It's a chart of deaths per hundred THOUSAND live births, and the numbers for all racial groups are all under 100, so less than 0.1%.

The way it's stated also doesn't suggest it's a percent increase because it says it rose from 14.5% to 18.9%. I can't figure out what they're trying to say, but they should definitely have been more careful with presenting the numbers.

If the pig option included immune suppression drugs for the rest of your life, or for like 10 years until it wore out and you had to have another major surgery to replace it, mechanical valve plus blood thinners and a yearly blood draw sounds like the much better deal. I know blood thinners come with their own long term effects, but nothing compared to immune suppression.

The judge also noted that the cited study itself mentions that GitHub Copilot “rarely emits memorised code in benign situations.”

"Rarely" is not zero. This looks like it's opening a loophole to copying open source code with strong copyleft licenses like the GPL:

1. Find OSS code you want to copy
2. Set up conditions for Copilot to reproduce code
3. Copy code into your commercial product
4. When sued, just claim Copilot generated the code

Depending on how good your lawyers are, 2 is optional. And bingo! All the OSS code you want without those pesky restrictive licenses.

In fact, I wonder if there's a way to automate step 2. Some way to analyze an OSS GitHub repo to generate inputs for Copilot that will then regurgitate that same repo.

next year when the Trump tax cuts expire

It's worth repeating again that the middle class Trump tax cuts expire next year. The Trump tax cuts for the wealthy have no expiration date and are permanent.

Also, they're not "Trump" tax cuts but Republican tax cuts, but at this point the distinction doesn't really mean anything anymore since Trump has completely taken over the party.

I don't recommend making significant changes to activity levels at the same time as making diet changes. Weight loss comes from changing what you eat. Exercise is absolutely necessary for a healthy lifestyle, but it is not the major factor in weight loss. And increasing exercise behaviors can destabilize eating habits, making it harder to stick to any good changes you do make with either diet or exercise.

Disambiguation page says it's also sometimes used as another name for the egg in the basket dish.

That strongly depends on the job. If the company has to follow regulations to meet some security posture, wiping the OS (and all the security tools and configuration set up by IT) to put your own favored OS without matching the security requirements could wind up with you getting fired.

No laws have been changed. Court decisions are not considered the passage of a law, so ex post facto doesn't apply. Changes to how laws are interpreted don't factor into ex post facto considerations.

Ex post facto is for if a new law is passed making something a crime, and the act was committed before its passage. This is all about interpretation of already passed law. It's basically the justices saying that this was against the law the whole time. Ex post facto doesn't apply here.