Only buy a game if you're happy with the current release being the last release. Regardless of the size of the company putting it out, you just never know what's going to happen.
And even worse, "preordering" digital games before even a review is out is just a moronic form of gambling.
Sad to see a new bluetooth device coming out that doesn't support LE Audio, the new audio standard introduced in Bluetooth 5.2.
Also no support for the various high-quality proprietary A2DP codecs you tend to see on Android like AptX Adaptive, AptX Voice, LDAC, etc.
Only supports AAC and SBC.
If you're on iPhone you probably have Apple's buds. If you're on Android you have high-quality, feature-rich options from actual audio companies for about the same price.
It's cool to have replaceable batteries but the device is already outdated technology-wise. You're going to really have to want to vote with your wallet for this to make sense.
That's exactly the behavior of enum classes in C++ (since C++11).
It is absolutely not the behavior of enum classes, switch, or the combination of the two in C++, though compilers may generate warnings. See example for the problem pattern matching solves.
I agree that in general the Rust community has a tendency to argue from a place of tribalism rather than experience. I don't view this as a problem specific to Rust, but moreso newbies succumbing to confirmation bias or choice-supportive bias and parroting opinions they heard from experts without understanding any of the nuance.
Indeed, it's less "impressive technology ahead of its time" and more "nice idea ahead of the technology".
They were likely counting on AI catching up quickly to avoid having that labor all together. Get the cost of AI mistakes down to less than the cost of labor and you win.
It's probably less specifically about enums and more about pattern matching.
In C++ your enum has 5 possible values. Somewhere in your code you have a "switch" and need to check all possible values. Add a new enum value and you won't get a compile error.
In Rust you use "match", which will cause a compile error if there are any possible values that you aren't handling. Add a new enum value, and on next compile you'll get a nice list of places that need to be updated.
She's not wrong about propaganda being more technically advanced and dangerous than ever. I wasn't commenting on that.
I do think she should just stay away from politics near election times. There is always going to be someone more appropriate to say this, who won't add an agenda trying to blame her embarrasing loss on it.
Look, I voted for her.
Her campaign was full of meaningless "it's her time" messaging. The DNC literally conspired to help her win the primary, with Debbie Wasserman Schultz resigning after evidence was leaked and then immediately joining Hillary's campaign. As a progressive, I really disliked Hillary.
When she finally faced off against Trump, half the time she just didn't seem to know how to react, and the rest of the time she'd just smile and act "above it all" rather than tackle him head-on. What have we learned since that election about how conservatives react to being looked down on?
Yes, there's been a ridiculous amount of shit flung at her. Biden's been getting the same treatment. But it's not why she lost. That she still comes up for air every now and then just to repeat this dilusion is insane. She was a bad candidate.
60Hz is perfectly fine for most gaming. It is even ok for shooters, as most players are kidding themselves about any differences higher rates make, although for a few exceptional players a higher FPS rate may make a small difference.
It's about quality. The quality difference between 60hz, 144hz, and 280hz are all noticable. Yes, I play at 280hz and occasionally Windows would fuck up and drop to 144hz and I'd notice it instantly upon launching a game. It may or may not make you a better player, but gaming at 60hz is awful once you've gone higher.
I don't understand why people pretend 60Hz is fine. I'm honestly convinced these people either don't game or have some disability in their visual system.
It's obvious that Boeing has some incredible and perhaps criminal quality control issues, but it seemed like the tire incident was more likely to be some maintenance staff didn't replace a tire correctly.
I feel like having a hair trigger to blame Boeing for things like this risks diluting the seriousness of the claims actually attributable to them.
"All the people are so happy now, their heads are caving in. I'm glad they are a snowman with protective rubber skin" -- They Might Be Giants
