What is not hacky then in a language design?
bitfucker
That's... what I'm saying. Clean room implementation is legal. You accidentally arrive at the same conclusion independently. And yes, it is tedious to do it but it is legal.
How so? People come up with the same idea all the time independently of each other. When doing clean room implementation (the ideal best case), you are not liable if what you create at the end matches 1-1 with the original. You never know anything about the implementation detail of the original. Academia also acknowledged independent discovery and publication of many things. Why would clean room implementation be different?
"But officer, all of this media that I have is for AI purposes. I swear I did not read/listen/watch/play it for myself too!"
I prefer appwrite if I could choose. Check them out of you don't need all the bells and whistles of supabase
Maybe like Open Policy Agent (OPA) but with Yaml instead of Rego?
Isn't it to keep the copyright notice and not the license itself? I.e, you may redistribute it with a different license term and conditions but the copyright notice must be retained. I don't know how different it is tho in legal speak. Maybe they are equivalent.
I always see people with the argument that the developer labour is somehow being exploited. But have you never thought that maybe, just maybe, the person in question does not care? He just wanted to publish his creation and be done with it. He does not care if people are using it. That's my case. I don't care if people want to use my piece of cryptographic library. Just be aware that I am just some random dude, providing no support nor warranty. I make the library for my use cases and it works fine.
Oh he is crazy alright. Just look at his videos making guitar hero... USING GUITAR!
Not really, you can charge for GPL software, but you must always provide the source and anyone may redistribute those
Ahh, yes. I read the official installation and it is indeed written in bold. AMD hardware with NVME drive targeted towards handheld. Yeah, would be nice for generic desktop too for living room PC.
I don't understand. What do you mean by deciding what the code should do in the context of language design? Can you give a concrete example? I am confused because the "main" function is required when you make an executable. Otherwise, a library will not contain any main function and we could compile it just fine no? (Shared library)