Don’t believe me? It’s all in the numbers.

If it worked anything like the GLOO Cannon from Prey, I would have been satisfied even if it were the only major innovation in the episode.

The downfall began when Ubisoft abruptly wrote Lucy out of the story after Kristen Bell asked for more money. Then they killed off the literal main character one game later, and nowadays you’d be excused for forgetting Desmond ever even existed given how little the modern day matters to the plot.

User tagging was what I was waiting for to try Voyager again (I prefer tagging users over blocking them), but per-user vote tracking was the killer feature I wanted an app to have.

I guess this is goodbye, Boost. Time to write a user tag import script!

Unsurprisingly, non-goblins tended not to bother with goblin currency.

Until one of your players invents currency speculation and gets rich. Though that could lead to a cool arc where the bankrupt goblin clans come after them for revenge.

I think that’s just Trump’s insecurity acting up because Musk gets nearly as much worship from his fans as he does. Hence him trying to mar Musk’s reputation and knock him down a few pegs.

It’s too bad they didn’t make the Moonlight Butterflies in the Crystal Caves hostile. Imagine the player tears after having to navigate narrow invisible walkways while dodging laser spam.

there were once Romans there

If Valve’s Employee Handbook is to be believed, they don’t use a formal project structure with static teams. Instead each developer works on whatever project interests them, and one of Valve’s current goals is to improve game performance on Linux/AMD by contributing to upstream open source projects.

Valve is as close as we’ve gotten to someone paying a bunch of industry veterans to contribute to open source. It’s amazing what happens when all innovation isn’t black-boxed in an internal repository and forgotten about.

Hopefully it doesn’t get stuck as a glorified cache drive due to cost and forgotten like Intel’s Optane was.

The crash I referenced was caused by having the scrollbar enabled IIRC, and it was fixed earlier this year. It made it impossible to launch the main activity without crashing if you’d enabled that setting, so users were sharing workarounds to launch directly to the settings screen without loading any communities so they could disable it.

Sync has had serious issues in the past such as an easily triggered, reproducible, guaranteed crash on open, with the dev not putting out a fix for months. This neglect goes back several years, to back when Sync was a Reddit client. Most infamously he disappeared for over a year when his UI refresh wasn’t well received.

The app is great (I’m only on Boost due to user tags requiring a paid subscription in Sync), but his response time to issues is glacial. And it doesn’t help that it’s by far the most expensive client if you want it ad-free, and features that used to be free now require an even more expensive subscription to use on top of that.

At least orcas don’t do to whales what they do to sharks - eat their liver and leave them to die in agony.

It boggles the mind that any language - let alone a systems programming language that most of the world’s infrastructure is built upon - wouldn’t adjust their specification to eliminate undefined behavior wherever possible. And C++'s all seem to be in the worst possible places, too.

Control shares the same universe and is more actiony, from what I’ve heard. It might be worth checking out if you haven’t already.

Or when someone read two sections and the teacher didn’t stop them.

Knowing a construction worker’s usual sense of humor, I’d be afraid of one giving the guy sitting next to them a solid slap on the back as a joke. Especially if they had just expressed a fear of heights.

Google started work on Carbon due to the difficulty of getting the C++ standards committee to accept any real, fundamental changes to the language. If Google, a grandmaster at manipulating standards committees, couldn’t get something passed, I don’t foresee this proposal getting anywhere.

Null safety is orders of magnitude simpler than memory safety. Kotlin is a null safe language by default. Java is infamously not. Anyone who has worked on a mixed-language Kotlin project can tell you how quickly null safety becomes a pain once guarantees break down - and that’s in a language where these issues are flagged instantly and you can “fix” the problem in a couple of characters! Mixed memory safe/unsafe codebases would be a nightmare in comparison.

Also, C++'s ecosystem consists of deeply entrenched libraries with ancient codebases. Safe C++ might be useful in a decade or two if library maintainers could be pushed to make the switch (good luck with that, if it’s half as much of a paradigm shift as Rust), but by then there will probably be multiple competing language features that claim to solve the same problem. It’s the C++ Way™.

Or the nightshade family, which matches mushrooms when it comes to range. It contains staple foodstuffs such as tomatoes, potatoes, eggplants, peppers, and more. It also contains deadly nightshade/belladonna and a host of toxic or psychedelic plants.