When building gcc from sources, it first builds itself once, then uses the result to rebuild itself (twice, actually).'nIn the process it gives a lot of warnings about how bad its own code is.
Uncategorized
1
Posts
1
Posters
4
Views
-
When building gcc from sources, it first builds itself once, then uses the result to rebuild itself (twice, actually).
In the process it gives a lot of warnings about how bad its own code is. I suppose we'll take its word for that!
-
undefined oblomov@sociale.network shared this topic on
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@cancel from reading the report from the copy right office it sounds like it is less of a matter of was a computer involved and more whether the human author did anything at all.
-
Current* conditions near Alpena, MI:
-
@res260 Sadly a likely observation :\
So many people just giving up on their craft.
-
@cwebber things sure are changing fast. code quality for example. and the ability of developers to write or recognize good code. now the direction of change isn't great, but...
-
@cwebber I'm hanging out there a lot and yes there is a lot of vibecoding. However, they don't seem to vibecode more than the average paid software dev.
In 2024, I'd say about 20% of my friends vibecoded. Today the number looks more like 90%. This is not specific to atproto, my understanding is that most people vibecode nowadays.
-
(Reposted as unlisted to not pollute my instance's discovery with slop-related content)
The US Supreme Court has declined to hear the AI copyright case. So, the new Copyright Office guidance that says the output of prompting systems that produce art, sound, text, etc., cannot be copyrighted, no matter how many times the human re-prompts or iterates the system, is upheld: https://www.theverge.com/policy/887678/supreme-court-ai-art-copyright
(Guidance from Copyright Office: https://copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf )
So, unless I'm misunderstanding something…
1) If your corporate codebase is written with AI, and it leaks to the public, too bad -- no copyright protections. People can take it and use it.
2) AI generated code is incompatible with GPL and GPL-like projects, because GPL requires copyright to be assigned in order to enforce the license. (Edit: only a problem if the project is 100% AI, since public domain can be mixed into GPL without problem.)
Is that really what's happening? Am I misunderstanding something here?
-
Trump si conferma come il Presidente che ha ucciso più statunitensi in patria e all’estero.
From: @peacelink
https://sociale.network/@peacelink/116165350333099284
-
@aeva I would assume the output of a procgen thing would not be copyrightable, yeah. But the code that generates the thing would be.
