@julia@eepy.moe People can have their cute little platformer 123 for what I care, but don't use children as an excuse to justify it when consumer rights are eroded left and right, especially if those children are then gonna grow up into this world get a serious reality check
Just because a kid wants it doesn't absolve you of your parental responsibility, and don't use them as a shield when justifying a purchase. Children might be a little impressionable but they're not gullible. You knowingly made the purchase so take the moral responsibility for it whatever the implications are. Them having one racing game is not gonna end the world of course, but don't come complaining to me about the company being full of shit
@julia@eepy.moe We didn't really care about the thread until the "As long as children keep asking their parents for their products, it won't end." take really
I just believe parents should take their children's future into account, and a kid might take a proper discussion about this at an early age much better than grow up in denial about the status quo
A child won't hate their parents for having a genuine discussion about this stuff and choice-making
@navi@social.vlhl.dev@wyatt8740@tech.lgbt Mmm not saying Cargo can't be blamed for issues, but many things Rust lacks to be used for aforementioned stuff like dynamic linking, Cargo isn't the limiting factor, and hating on it for areas where Rust is simply undercooked doesn't solve the underlying issues of the ecosystem that need work first, and since it has this vendoring paradigm, obviously it's hard to bend it to do stuff where dependency resolution is entirely different
@navi@social.vlhl.dev@wyatt8740@tech.lgbt What Cargo does is pretty good in terms of development experience, but unless we have the tooling and abstractions for high-quality native library interoperability, we're doing this approach
@navi@social.vlhl.dev@wyatt8740@tech.lgbt I mean yeah we know about the Fish thing, but I'd say it's valid to use something else for places where it is wrapping around complex native stuff, especially when many such quirky things are often C libraries with a safe Rust wrapper. Fish porting the platform-dependent stuff to Rust was bound to be a bumpy road
But once you wrap the quirky stuff, you can essentially stick to doing these simple binaries just fine, and Cargo gets that done. Which is sort of the main point of Rust, isolating the dirty stuff in a box and using that box without having to know the insides of it
@wyatt8740@tech.lgbt If you're gonna do systems or embedded, of course you'll prefer having more control, but hating on Cargo is misplaced if portable binaries, memory safety, and correct abstraction are not the goal to begin with :floofWoozy: