What is your point? Logic bugs can occur in any language. If you decrease amount of other bugs that can happen (like memory safety bugs) then you can focus more on "logic" bugs.
And it fits the category of "rewrite it in rust for the sake of rewriting it in rust. Is it at least as good as the original ? No, but at least it's in rust".
It reminds me of the recent article on hn talking about rewriting sqlite in rust. Simply put, the point is that even if sqlite is written in C and may have small memory leaks, it works perfectly, being tested and fixed over 20+ years. By rewriting it in rust, OK you'll be memory safe, but you will have logic corner edge cases nasty bugs that will appear, and no one wants that. So sqlite will stay in C.
Made for myself to mass remove notification for all your subscribed channels. Sharing with you all to enjoy the peace of the bell icon showing nothing for the first time.
No, the inference/training algorithms, being math, are not copyrightable. OP just wrote another implementation. What's copyrighted are the models, which OP did not train from scratch (having neither the training material nor the compute to do that).
Is upstream dependency licensure necessary to establish copyright? For example, I Need a Haircut was still a unique work regardless of the rights to sample Alone Again.
I mean, if you take a match to a blank CD-ROM, or shoot neutrinos at a USB drive, there is a very small chance that you get the SD weights stored on them
The code outlining the network vs. the resultant weights. (Also vs. any training, inference, fine tuning, misc support code, etc.)
The theoretical diagram of how the code networks and modules are connected is math. But an implementation of that in code is copyrightable.
Afaik, the weights are still a grey area. Whereas code is code and is copyrightable.
Weights are not produced by humans. They are the result of an automated process and are not afforded copyright protection. But this hasn't been tested in court.
If OpenAI GPT 4o weights leak, I think the whole world could use it for free. You'd just have to write the code to run them yourself.
I'm curious how Tauri causes different views on different platforms because Tauri frontends are websites and if websites function same way on platforms so should the apps. If websites use something to hide browser differences so should the app developer on Tauri.