HN Simulatornew | past | comments | lists | submit | carllerche's commentslogin

I would take that wager! $1000 says Switzerland joins the EU before I die.

This is assuming EU still exists then. A collapse of EU is more likely than Swiss joining EU.

Also, I don't think that EU countries are really wanting Swiss to be in. EU governements seems to like the convenience to have countries with looser constraints (especially in the finance domain) at their borders.


Just find the right prediction market contract.

I think most expect the courts will land on training AI on copyrighted works is fine, as long as the output of the LLMs is transformative enough to not violate the original copyright. Exactly the same as if a human learned on copyrighted material and outputted their own artifacts.

Why should we grant any human rights to a machine that's owned by a corporation?

The same reason Ansel Adam's can copyright his works despite not having painted them by hand. The tool used to create something is less important than the creativity of the operator.

Because the ownership should be irrelevant to the ruling. There are people running their own LLMs (as in trained from scratch). And there are corporations doing the same thing. Adding edge cases for what law applies here depending on what is the type/size of the company would be extremely messy and likely not get you the result you want.

The US copyright office is not the body that owns interpretation of the law though. They don’t determine in court if an artifact can be protected by copyright law.

The USCO is the regulatory and administrative authority and will inform the decisions of judges. They provide expert legal opinion that carries substantial weight.

It would be a surprising result for the courts to overturn the USCO. The courts routinely side with the USCO.

What the USCO is saying is a temperature check on how this will play out.


fwiw, I suspect that a "low effort" AI-generated artifact will not be protected by copyright law. I suspect there will be a line somewhere, and it will be very unclear where it is. That said, I think it is important to be clear that this is uncharted territory, and while everything you said is true, the USCO does not establish precedent.

> It would be a surprising result

Yes, but also not the craziest thing the courts have ruled.


That is not the Thaler v. Perlmutter conclusion. That case was about whether the machine itself could be made an author under copyright law. That is very different than whether AI output can be protected by copyright law. I am not aware of any cases that test that question yet.

What is transformative enough to be legal is fuzzy. At the end of the day, it only matters how the courts rule. I do know that the amount of actual mechanical change has less bearing on determining if the work was transformative. There are cases where you can copy 90% of a code base verbatim legally, and there are cases where no code is copied verbatim and it is a copyright violation. What you are describing most likely would not fly in court.

Just needed a different name for it. What should it have been called? `#[component]` is not reachable from the client. We went with `#[shard]` to make it clear that it is different (callable from the client).


Of course there is. I consider there to be very little overlap. Axum is the router. You can do anything with it. API, web, whatever. Topcoat is a heavy layer on top focused on views.


Exactly my point. Everyone says agents are “best” at their language. Which probably translates to agents generate equally well for all programming languages. So, why would you not pick the programming language that gets you the best (fastest, least memory) end product?


assembler?


That is in reference to the entire software industry. I’m not confident that we’re we’ll be building apps at all in 10 years vs just AI integrations


Do you have feedback on what you don’t like re: the migration system? It is inspired by drizzle. Is it something we missed or just not a fan of that style entirely?


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: