Show more

I've talked about this before, but let me do it again.

The US is more or less run by the entertainment industry.

Creating your own music, art, movies, books, videogames, podcasts, and stage plays within the US is an act that robs the established power structures of attention.

Making media is an act of radicalism, of protest, and of outright rebellion.

Support local music. Go to a community theater. get a bunch of weird nerds together in a basement and film a talkshow.

Fight back.

If I've learned anything from my short stint on the pkgsrc-security rotation so far (which involves filtering out CVEs and advisories to find anything relevant to pkgsrc), it's to avoid Adobe products and Wordpress plugins like the plague.

I've written more C in the last year than in the rest of my life up to that point. I'm reflecting a bit on why I feel so productive in C.

- Small core language. Easy to keep a lot of it in my head.
- Small standard library; easy to keep an "info" window open and find what I need.
- Few distractions created by the ecosystem/tools.
- Lightning fast builds.

Managing names and changes in both .h and .c files is a pain, and my biggest gripe about C. But it's really my only major one right now.

For resource utilization, container orchestration in some form probably is the future, especially if you're pushing your enterprise architecture toward microservices and Twelve-Factor apps. But I'd like to see something more KISS than K8s be the ultimate answer to the question of how we do orchestration.

Someone will tell me I'm not thinking about the scale these tools are designed to operate at. You're really talking about two things: infrastructure-as-code and resource utilization. For the first, again, package manager and smart scripting. Fight me.

Not only are K8s and OCP *not* easier to use in a nominal case, but if they fall over they're orders of magnitude more complex to debug. I spent hours over the weekend chasing an issue running Minikube that came down to a conflict with my nftables config.

After spending the weekend playing around with Minikube and researching best practices for using full-blown Kubernetes, after several months of working with OpenShift Container Platform (still in progress), I'm still not convinced these tools are any easier to use than a package manager and some smart scripting.

I’ve been out of the macOS game for a couple years, but it seems like Homebrew has become the de-facto standard package manager for devs. Everyone just assumes it’s already installed. Is this true?

My issues were due to conflicts with my nftables config on my laptop. Flushing the rule set fixed it.

Container orchestration seems like a cool idea until you try it. Then you realize it’s a complex system held together with tape and glue.

So minikube is supposed to be the “simple” Kubernetes environment to install and get running? Seriously?

You know what? Never mind.

Watching How Go Train Your Dragon with my children. I didn’t know Viking culture was basically just Scottish.

@djmoch can also use the env variable
XZ_OPT="--threads=0"

Looks like adding -T 0 to $COMPRESSXZ in /etc/makepkg.conf should do the trick

Could makepkg on be improved to use all available cores when compressing the tar.xz? 🤔

our meme generation neural network student is getting towards the end of his masters thesis and the results are absolutely a riot

Show more
Mastodon

A private Mastodon instance