This is what I use as well, although it was primarily out of laziness. Works well enough. I would say the Gluetun solution is a better recommendation, more robust and scalable, but the haugene container basically just works.

Buckshot Roulette is fun. Not a lot to it, really, but a fun loop that I got a decent number of hours out of.

I bought Arctic Eggs after seeing a little bit of a playthrough but haven’t actually played it yet. Seems weird, which I like.

IIRC New Zealand returned to actual normal, as in COVID was a relative non-issue, faster than many other countries. Their restrictions were more severe and weren’t lifted very quickly, but when they were lifted things were actually fine.

Places like the US and much of Canada dropped restrictions while things were still pretty bad in terms of infection rates and strain on health care systems, and really they hardly enforced them to begin with. You could see this as a return to normalcy since restrictions were gone, but in Alberta they lifted restrictions when we were still dealing with plenty of deaths, severely impacted health care, and on top of that we were still figuring out the implications of the whole long COVID thing. That’s not a return to normal, I don’t think, it’s pretending things are normal when they’re not.

I find pan frying them works best if they’re leftovers, the dough fries up better after it’s boiled and then dried out a little. It’s a very good option for sure.

Potato and cheese is classic, and honestly it hits the spot better than you might expect. Toss with butter after boiling. Keeps them from sticking and tastes great.

Commonly topped with sour cream, green onions, other onions, and/or bacon depending on what you have handy. A nice fatty sour cream with grilled yellow onions is my favourite, especially served with a nice hunk of garlic sausage.

I’m always excited to see Yaddle in something until I SEE Yaddle in something. Yoda with long hair is just super concerning to see.

Foddy is a game developer with a history of making games with frustrating control schemes. He originally got notoriety for QWOP, where you use the QWOP keys to control the runner’s left and right knees and feet and run as far as you can. Lately he’s better known for Getting Over It, a rage platformer where you play as a guy in a cauldron who moves by using a hammer to drag/throw himself around.

The description and comments on the video 100% confirm multiplayer. Honestly I’d be excited for the game either way, but I have a lot of fun playing crafting/survival games with friends so it’s appreciated.

On our trip a few years back we got some simple pastries, sandwich supplies, and snacks from Bonus to save money and I never felt like we were missing out on good food. Even as a discount grocer everything we got from there was super good.

I think it’s complicated a bit by the fact that this was said on stage at one of their shows. I think canceling the tour is a gross overreaction, but with the current political climate (even ignoring the assassination attempt) I can understand some hesitancy to proceed if anyone is going to be associating them with calls for political violence.

All that said… based birthday wish, fully agree with Gass’s joke.

This sounds much more like the reason. 12pm-3pm, plus some time before and after to prep and commute and stuff, plus these things often run long in my experience… It easily becomes most of the afternoon. If you have anything else you need to do that day it becomes a fairly big deal.

It’s been almost a decade since I used C++ and had to verify, but after some quick searching around it looks like it hasn’t changed a ton since I last looked at it.

You can use smart pointers, and certainly you should, but it’s a whole extra thing tacked on to the language and the compiler doesn’t consider it an issue if you don’t use them. Using new in C++ isn’t like using unsafe in rust; in rust your code is almost certainly safe unless marked otherwise, whereas in C++ it may or may not be managed properly unless you explicitly mark a pointer as smart.

For your own code in new codebases this is probably fine. You can just always make your pointers smart. When you’re relying on code from other people, some of which has been around for many years and has been written by people you’ve never heard of, it becomes harder to be sure everything is being done properly at every point, and that’s where many of these issues come into play.

C and C++ require more manual management of memory, and their compilers are unable to let you know about a lot of cases where you’re managing memory improperly. This often causes bugs, memory leaks, and security issues.

Safer languages manage the memory for you, or at least are able to track memory usage to ensure you don’t run into problems. Rust is the poster boy for this lately; if you’re writing code that has potential issues with memory management, the compiler will consider that an error unless you specifically mark that section of code as unsafe.

Honestly? Bash. I tried a bunch a few years back and eventually settled back on bash.

Fish was really nice in a lot of ways, but the incompatibilities with normal POSIX workflows threw me off regularly. The tradeoff ended up with me moving off of it.

I liked the extensibility of zsh, except that I found it would get slow with only a few bits from ohmyzsh installed. My terminal did cool things but too slowly for me to find it acceptable.

Dash was the opposite, too feature light for me to be able to use efficiently. It didn’t even have tab completion. I suffered that week.

Bash sits in a middle ground of usability, performance, and extensibility that just works for me. It has enough features to work well out of the box, I can add enough in my bashrc to ease some workflows for myself, and it’s basically instantaneous when I open a terminal or run simple commands.

If the bad guy hears rumours about someone asking the question, does anything change?

When a clock fills in these contexts that should indicate that something needs to happen, and that something likely requires PC response. So if it isn’t going to significantly impact the PCs until the third clock, it may as well be one big clock with stuff happening in the background as it fills. But if each clock has an impact and the PCs can do something to impact future clocks, stacking makes sense.

Regarding handling the consequence: it definitely depends. I’ll sometimes use a clock if they’re trying to overcome some major obstacle, so filling it means that they have less to deal with and that’s probably going to be an RP exercise. But most of the time it’s going to result in a change in position, or a need to resist something, or even a material change in their crew’s territory that requires some response. In the example above, especially for such a large clock, I’d probably have the consequence be something like the bad guys invading their territory targeting the PC asking questions, which requires more than a mere change in position to resolve. That could involve a full-on heist to thwart.

Is that the damage formula based on, uh, circumference?

Haven’t actually read the book, thankfully, but I recall hearing that was a thing.

There’s been some controversy around the governance structure and culture with NixOS that has a number of people unhappy. I’m honestly not sure of the details but it’s ptesumably less about the software than the people.

Logseq is a great alternative. It’s very much not a clone, though. It has a different paradigm on how it views notes and the functionality isn’t exactly 1:1.

It’s tricky for sure. The plain text is great, and all the functionality is built off of plain text (even the canvas!), but replicating the functionality isn’t trivial by any stretch of the imagination. Migration is easier because of the text files, but will it be as easy to see the links between notes? Or query all the notes I need more detail in? Or map it all out visually?

I think reimplementing the core obsidian functionality in a FOSS clone would be fun… except I already have a queue of projects and not a lot of time, so here I am complaining instead 🤷

It’s a good philosophy, to be sure. It doesn’t take many migrations to realize that keeping your files in open, easy to read formats is preferable.

I also use obsidian, but I do sometimes worry that the linking and metadata will be difficult to work with in the future when the software goes away. It’s all there in the files, but my vault is slowly linking together in interesting ways that rely on obsidian functionality.