So because you don't understand it, everything it does should be legal?
It's not rare maths. There are trns of thousands of AI experts. And most CS graduates (millions) have a good understanding on how they work, just not the specifics of the maths.
Yeah, they're not selling a copy, they are just selling a subscription to a copying machine loaded with the information needed to make a copy. Totally different.
I should start a business of printers and attach a USB with the PNG of a dollar bill. And of course my printers won't have any government mandated firmware that disables printing fake money.
I'm not printing fake money! It's my clients! Totally legal.
Yeah, making sandwiches also costs money! I have to pay my sandwich making employees to keep the business profitable! How do they expect me to pay for the cheese?
EDIT: also, you completely missed my point. The money making machine is the AI because the copyright owners could just use them every time it produces copyright-protected material if we decided to take that route, which is what the parent comment suggested.
If the solution is making the output non-copyrighted it fixes nothing. You can sell the pirating machine on a subscription. And it's not like Netflix where the content ends when the subscription ends, you have already downloaded all the not-copyrighted content you wanted, and the internet would be full of non-copyrighted AI output.
Instead of selling the bee movie, you sell a bee movie maker, and a spiderman maker, and a titanic maker.
Sure, file a copyright infringement each time you manage to make an AI output copyrighted content. Just run it on a loop and it's a money making machine. That's fine by me.
I'll train my AI on just the bee movie. Then I'm going to ask it "can you make me a movie about bees"? When it spits the whole movie, I can just watch it or sell it or whatever, it was a creation of my AI, which learned just like any human would! Of course I didn't even pay for the original copy to train my AI, it's for learning purposes, and learning should be a basic human right!
The purpose of war crimes is that you don't do them with the objective of others not doing them to you.
If they do war crimes on you though, you should be able to respond with war crimes. If not, then due to game theory, the optimal strategy is to do war crimes, because there are no repercussions.
To be fair, mechanic items, and especially electronic ones were far more repairable back then.
You could see, desolder and solder components without issue. Nowadays most of the electronics are inside chips, and only the components that need to be physically big (like those responsible for the power supply) are human sized. Sure, there are some small SMD that can be manually diagnosed and replaced, but even then you often need a lot of skill and equipment.
The good thing about Box::leak() is that it returns a raw *mut pointer. So you need unsafe{} to dereference it. Might as well: let my_ref = &mut unsafe{*ptr}; while you are at it, so you have a perfectly normal rust reference, so the function signatures don't need any change.
The problem with Rc is that it would also require a RefCell most of the time. So the whole thing would be filled with Rc<RefCell
<T>
>. With the required .borrow_mut(). It would both do a pain to do and undo.
And of course I want to undo it, because RC is a shitty GC.
I've re-thought about the problem and I think for prototyping I should just Box::leak() and work with raw pointers.
This approach also doesn't allow you to not learn the borrow checker, since leaking everything is not a good memory management strategy, but might be fine for rapidly iterating on a design.
EDIT: maybe use a leak!() Macro that does Box::leak(Box::new()) in debug mode but panics on release (as long as you execute once in release it should be fine).
Another user already proposed Odin, but no one yet Jonathan blow's unnamed programming language (people call it jay). Those are the 2 programming languages that came to mind when I think of game development.
I haven't tried either so I don't know if they fit you, but they are new languages so they should avoid java's and C++'s pitfalls.
Interfaces (traits in rust) are the best imo. Way better than raw structs in C or the mess that is inheritance.
What I don't like about go's interfaces is that they're implemented implicitly. I much prefer java's and Rust's way to implicitly say which classes/structs extend/implement which interfaces.
Using "clever" ways to disable the borrow checker is one of the few things I don't like about rust. I much rather it having a "borrow checker version" and a "garbage collector version". That way we could rapidly iterate through design choices with the GC, and once the design has proven good, apply lifetimes and such to use with the borrow checker. The only downside to this I can think of is that most would just leave it in the GC version and not bother to move to borrow checker. But that's fine by me, rust has many other features to take advantage of. As long as no GC libraries are allowed in crates.io, it should be fine.
So because you don't understand it, everything it does should be legal?
It's not rare maths. There are trns of thousands of AI experts. And most CS graduates (millions) have a good understanding on how they work, just not the specifics of the maths.
Yeah, they're not selling a copy, they are just selling a subscription to a copying machine loaded with the information needed to make a copy. Totally different.
I should start a business of printers and attach a USB with the PNG of a dollar bill. And of course my printers won't have any government mandated firmware that disables printing fake money.
I'm not printing fake money! It's my clients! Totally legal.