Yossarian is kind of a whiny bitch, but it’s because he’s trying to cover up his exhaustion and terror with anything that will keep him out of harm’s way. What I liked about it was all of the silly jokes that come back to hit hard in the second half of the book.

Oh hey, I’m reading The Martian right now! Also loved Project Hail Mary by the same author, Andy Weir. It’s a bit more fantastical and just a great read.

Paradox seemed like the ones to do it, what with publishing Cities Skylines, but unfortunately their life sim was canceled.

Paralives is still going strong in development, though, with a pretty constant stream of updates. Really hoping that one sees the light of day. They’ve already got a pretty impressive building system working, but they’ve got some big ambitions, particularly when it comes to adaptive interactions with character heights.

We’re committed to not only our existing slate of games but also expanding our presence in the interactive space as we continue to look for opportunities to take a more integrated approach to linear and interactive storytelling across film and TV, gaming, and theatre.

Annapurna’s no slouch when it comes to TV/Film publishing, but if I had to speculate, I’d say there was probably some friction between the film and game sides of things as far as goals and culture go. It’s possible that the film side management was being a little too controlling of Interactive with all the Alan Wake and Control IP plans, leading to the request to split.

Annapurna Interactive has published some real bangers, especially when it comes to truly small team indie devs. If they do reform as a new company, hopefully they can pick up that legacy and bring more stuff to market.

Anyway, that’s all to say… go play Outer Wilds.

Okay, but even if that’s the case, what do we do about the very real consequences for trans people?

I guess the question is, what happens to the kernel when all the people who learned on C are gone? The majority of even the brightest new devs aren’t going to cut their teeth on C, and will feel the same resistance to learning a new language when they think that there are diminishing returns to be had compared to what’s new and modern and, most importantly, familiar.

I honestly get the hostility, the fast pace of technology has left a lot of older devs being seen as undesirable because the don’t know the new stuff, even if their fundamental understanding of low level languages could be a huge asset. Their knowledge of C is vast and valuable, and they’re working on a project that thrives because of it. To have new people come to the project and say “Yeah, we could do this without having to worry about all that stuff” feels like throwing away a lot of the skill they’ve built. I’m not sure what the solution is, I really don’t think there are enough new C developers in the world to keep the project going strong into the future though. Maybe a fork is just the way to go; time will tell which is more sustainable.

Permissive licenses mean faster and more widespread adoption, it’s up to project maintainers if the tradeoff is worth it. Ideally a company would realize that an open source part of their project probably isn’t radically going to affect their revenue stream, but you don’t just have to convince devs, you have to convince the suits and lawyers, and they will tell you to just build your own rather than give up any precious IP.

The most heinous thing is lack of required sick time. And who is it that’s least likely to get paid sick time? Customer service, of course, the ones coughing and sneezing all over your clothes and food.

Just make sure you actually do get a payout, had a friend screwed over by that recently.