Had they limited CI/CD depending on the project "community" (whatever that means), that would be a reasonable take. Instead they ban something tangential to the discussion.
I can publish human slop and use loads of their resources without any LLM use.
Maybe but your brain is not running 24/7 capable of outputting thousand if not millions of tokens per hour, all while having ingested nearly the entire internet.
If yours do that, maybe we can redefine what copyrighting and patenting means for humans
Gotta start somewhere. Plus foxconn only abandoned 1 DC build out during Covid, a bit different from TSMC investing billions to build multiple, of which they already built 1.
You indeed need to pay someone if you take their copyrighted materials and regurgitate it. Ask DJ's and producers how they need to include royalties for samples used in their tracks.
> Did anyone interpret that as the team insulting TypeScript itself?
No because Go and Typescript have wildly different use cases, and they explained in details the rationale for migrating the compiler, and why Go versus Rust. Their rationale makes sense, and did not throw Typescript under the bus (obviously).
I didn't know it was impossible to build businesses without inserting to Meta/Google/others ad SDK to spy on all my users. Maybe we should stop normalizing these behavior.
Snarky comment aside, Python is definitely *not* a "live system". If you had worked with such system before you'd know the world of difference between a version release of "stable" software versus a live platform that cannot fail.
Indeed these voices will drive some sales away, but unless other options are competitive with Bambu's offer, they still sell some of the best price-performance-reliability ratio printers on the market, and that's really attractive for the average buyer.
Most commenters here will value the openness of Prusa, but most lambda users will have limited budgets that Prusa does not cover. The U1 is a great attempt at taking on BambuLab head front, with interesting features at a reasonable price point.
In the end, a lot of people (including here) are using an iPhone even though it's locked down to a higher degree. Some people like a walled garden, some don't care.
I'm not against rewriting it in Rust because I believe it really may help in certain class of bugs, but indeed it should not be replacing the old version instantly for that reason. Both could co exist, even tho you still need some guinea pigs to test it out and find issues.
Other than security, Rust brings major improvement to the tooling and may help bring fresh members that wouldn't want to contribute to C code. I understand why some projects go that route
How many CVEs in coreutils over the years? The project has the advantage of being old enough for them to be fixed. Call me when the rust rewrite has been there that long and still has more CVEs than the GNU counterpart.
I can publish human slop and use loads of their resources without any LLM use.