I'd say, I'm primarily a very low volume gamer, so I don't play a lot of games, and if I do, I don't play them for long. And that certainly makes it easy to look at the news of a game releasing and to think, yeah, that's probably neat, but if I'm buying another game then it'd be Undertale or Baba Is You or such, and it definitely doesn't look as neat as those...
Ephera
joined 5 years ago
Damn, how have I not heard of this before? I always thought it got dumped into landfills and eventually degraded to tiny particles. If it's released so directly, it feels a lot more viable to reduce exposure by avoiding plastics...
Huh, I practically only know Intel as having defects and vulnerabilities, but I didn't know this had such a long history...
Rust does an interesting thing in this regard. It does still have == for checking if two values are equal, but well, it actually doesn't have a traditional assignment operator. Instead, it has a unification operator, which programmers usually call "pattern matching".
And then you can use pattern matching for what's effectively an assignment and to some degree also for equivalence comparison.
See a few examples here: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=1268682eb8642af925db9a499a6d587a
I mean, it is good to be empirical about things, but it would fit well into the other evidence we have.
The warmer air means there's more energy kicking about in the atmosphere and, to my knowledge, we have pretty clear evidence that this causes more extrem weather events to occur. For example, hurricanes are more likely.
We'll probably see those on the weather radar to avoid them, but at that point it would be weird to me, if the occurrence of lighter winds wasn't also more likely in places we don't avoid.
I guess, a reduction of turbulence injuries might've taken place independently, because our instruments for predicting them are getting better, but then their frequency would've still increased.
You could use this crate to build a Rust program which uses the Qt GUI framework and therefore would feel rather 'native' in KDE.
But the vast majority of KDE applications continue to be implemented in C++.
Ah, "pop like popcorn" was maybe a bit misleading. I mainly meant that it jumped out of the pot violently. It didn't turn inside-out like maize popcorn does.
So, the taste was essentially unaltered. The seed had burst open, though, so maybe that would help, if you wanted to make a sauce more spicy.
Lil Gator Game is a charming, somewhat smaller game with very similar gameplay to BotW.
"Infrastructure as code" is what the strategy is typically called. You use one of the many tools for orchestrating configuration of hosts (Ansible, OpenTofu, Puppet, Saltstack, Chef, etc.). These allow you to provide configuration files and code for setting up your hosts in a central place. This place is typically a Git repo, allowing you to keep track of when which change was made.
Depending on the tool you use, you trigger applying the configuration on your dev PC, or there's a hosted CI/CD server which automatically rolls out the changes when a new commit is pushed.
Did you know that when you fry mustard seeds, they pop like popcorn?
Well, I didn't, so I hadn't put a lid on.
I was still finding the little fuckers several months after the incident, in all kinds of corners of my kitchen.
For a project called "Potato Peeler", I'll put it into a structure like this:
~/Projects/Tools/Potato-Peeler/potato-peeler/
Tools/ is just a rough category. Other categories are, for example, Games/ and Music/, because I also do gamedev and composing occasionally.
Then the capitalized Potato-Peeler/ folder, that's for me to drop in all kinds of project-related files, which I don't want to check into the repo.
And the lower-case potato-peeler/ folder is the repo then. Seeing other people's structures, maybe I'll rename that folder to repo/, and if I have multiple relevant repos for the Project, then make it repo-something.
I also have a folder like ~/Projects/Tools/zzz/ where I'll move dormant projects. The "zzz" sorts nicely to the bottom of the list.
Ah, interesting. In my current setup, I dump the auxilliary files into a folder above the repo, but it can certainly make it a bit messy to find the repo in there then...