The proof is in the pudding, though. In my experience, working across Go codebases in open source and in multiple closed-source organizations, errors are nearly universally wrapped and handled appropriately. The same is not true of Rust, where in my experience ? (and indeed even unwrap) reign supreme.
It’s odd that the .unwrap() hack caused a huge outage at Cloudflare, and my first reaction was “that couldn’t happen in Go haha” but… it definitely could, because you can just ignore returned values.
But for some reason most people don’t. It’s like the syntax conveys its intent clearly: Handle your damn errors.
> As much as I’d like this change to happen, it’s too soon. This change would kill off projects like Bazzite entirely right as Fedora is starting to make major headway in the gaming space.
> I’m speaking as it’s founder, if this change is actually made as it is written the best option for us is to just go ahead and disband the project.
Now, whenever you would've actually shut down the project is a different story, but your messaging was very clear.
The messaging was very clear that the upstream change would make Bazzite almost untenable.
It was a criticism of Fedora, not a threat to quit.
Is the idea to weaken the UK? To what end?
Also, if it’s being done to us, surely we’re doing it back? The CIA and MI6 are no stranger to destabilising regimes, and yet surely it would be more common knowledge if we were employing people to post anti-Putin propaganda on Russian forums?
This is an interesting thing I've noticed about game dev, it seems to sometimes live in a weird space of optimisation requirements vs hackiness. Where you'll have stuff like using instruction data as audio to save space, but then forget to compile in release mode or something. Really odd juxtaposition of near-genius-level optimisation with naive inefficiency. I'm assuming it's because, while there may be strict performance requirements, the devs are under the pump and there's so much going on that silly stuff ends up happening?
The longer it’s not released for sale, the more debt you’re incurring paying the staff.
I’ve worked with a few ex-game devs and they’re always great devs, specifically at optimising. They’re not great at the “forward maintainability” aspect though because they’ve largely never had experience having to do it.
Neither of those things are control flow, and yet again I’m reading a pro-Zig text taking a dig at Go without any substance to the criticism.
Also funny having a dig at goroutines when Zig is all over the place with its async implementation.
However, the Steam Frame Controllers do. Seems weird they would add them on the Frame wands but not the actual controller replacing the controller that does have them.
Here, Checkout has been the victim of a crime, just as much as their impacted customers. It’s a loss for everyone involved except the perpetrators. Using words like “betrayed” as if Checkout wilfully mislead its customers, is a heavy accusation to level.
At a point, all you can do is apologise, offer compensation if possible, and plot out how you’re going to prevent it going forward.
I used that to set things like boost in rocket League and it felt super intuitive.
Like you, I also used this for boost on Rocket League and it was surprisingly intuitive. You can map it to the triggers lowest threshold to emulate it but without the tactile bump to rest against it just won't work.