the issues related to that macro still exist, but the author seemed to call it out and link to an article about it (which doesn’t seem disingenuous at all to me).

That’s fair, I stand corrected and I overreacted a bit.

I stumbled on the unintended cancellation a few times, but I’m used to select! paradigm from the other languages (and not used to how differently it behaves). I suppose I just expect the examples of its usage to be explicit and actually show what it takes to make select! behave in a way that doesn’t abruptly drop your async function after only going though half of it.

What I find slightly dishonest is bits like

This way of using select in a loop could potentially cause issues regarding cancellation of futures (although in this case it’s fine)

The select example is pretty straightforward and comparable to such in other languages, even to Go’s switching on channels. But rust hides an extra bit of complexity with the cancellation concerns that people don’t want to talk about unless absolutely necessary, and it is necessary in so many cases!

There were quite a few games using the same formula (and improving on it), to the point where I feel Desperados would be my favorite in that genre, not Commandos itself.

I still remember having to reparation my drive and reinstall windows, upgrading from fat16, because commandos wouldn’t fit on either partition.

I don’t think your question relates to the language as much as to the platform. The language of choice is somewhat irrelevant and what you care about is what actually happens under the hood.

For the likes of java and go you want to have some understanding of what runtime does for the memory allocations and how their GCs work. For python you sometimes end up in the spots where you need to understand what limitations the GIL imposes (even more important now that they are trying to get rid of it). When you run C (or C++ or Rust) on the embedded hardware it really helps to understand what exactly bit flipping does in specific registers and what DMA means for how you write your code.

You don’t really have to know it all. You can absolutely write code without caring about anything of that and I know plenty software engineers that do. Some people write amazing functional things in java without ever questioning what it does to the machines and what resources you need to run it.

If you start questioning it, that will only expand your understanding. It’s not a lateral move from e.g. C to Rust where you need to learn a lot to write your code in a memory-safe way, it’s a movement deeper into the stack and what you learn there will be applicable to any language you use for this stack.

Answering your question: I always feel bad about not understanding some low-level concept. I have stacks of MCU reference docs lying around, printed, highlighted; I have archives with sample code, and hand-annotated CMSIS reversing notes. Embedded world is hard because you can’t just know C and be done with it. You have to know the hardware, too.

Here’s my advice for you. Make notes of things that you learn from people smarter than you. Create a web of those notes and see where your gaps are. Then, work on learning something in those gaps in particular and see if you can make a blog post or something of your own. When you share what you learn you become one of those people with deep understanding that others look up to. There’s always someone struggling with something that you either know or know how to figure it out.

given time in lieu

after squadron 42 ships*

So here’s the thing. This year I fell in love wih clojure, it’s an absolute pleasure to program in. It’s also a hosted language that runs on java (primarily) or javascript (or a bunch of marginalized things). And honestly, I feel like I can make the java backend run more resource-effecient than the JS one.

I replayed it the other week after not touching it since the original release. Was fun. I managed to forget a bunch of puzzles, and the new graphics made it fun to just explore the Ages.

You mentioned failing to find the github markdown specs. Those are the specs.

There you go!

Why would you need specifically “cloud” logging for that? Spinning up grafana and loki is rather trivial in the modern containerized world and that’d cover 90% of what you want from logs. Neither is a resource hog, too, it’s so much better that e.g. the ELK stack for logs that you only look through occasionally.

It’s more of a chat-to promotion than a useful list. “Use firewalls?” No shit!

from the left screen edge towards right.

FWIW Sourcegraph chrome extension adds a neat “open in Sourcegraph” to github pages and SG is just superior. Why would you use Github’s mediocre search either way ¯\_(ツ)_/¯

IANAL and you really should ask a lawyer about this. The answer very much depends on your work contract and country of residence (the latter due to the fact that some generic contracts’ statements might be legally unenforceable in specific jurisdictions).

I’ll throw in a random fact: the contract might say that whatever you write as a programmer is still company’s property even off the clock and it will be legal in some US states.

Not an answer, but a clarification. You seem to be messing up two things. DoH is basically encrypted DNS, i.e. no one other than your DNS provider can see what domains you ask for. It’s orthogonal to ad blocking; there are various service that provide one, or another, or both.

Streaming JSON parsers are a thing, e.g. pdjson for C. It’s, of course, a different approach and it’s generally slightly trickier to work with those, but that’s what you would use of you have unbound document size and you can process it in chunks.

Hetzner machine in that article is bare metal. It’s much harder to extract the certificates from a running server without anyone noticing.

Unreal Tournament and Deus Ex both come to mind. Alexander Brandon was involved in both and his work is absolutely amazing.

If we talk specific singles, though, it’s Morrowind (Nerevar Rising), Control (Take Control), and, recently, Baldur’s Gate 3 (Raphael’s Final Act). Morrowind’s tune is so ingrained in my mind that it’s my to-go whenever I get my hands on a keyboard.

I’m the same and I studied every nook and cranny during my first playthrough because FOMO was real. Guess what, I still missed enough things to make a second run no less entertaining―especially if you play a polar opposite of your original character. This game accommodates to pretty much every stupid decision you can throw at it and it’s amazing.

That’s somewhat similar to how apple private relay works.