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.
Nancy Pelosi and Fakebook’s Dirty Tricks https://www.nytimes.com/2019/05/26/opinion/nancy-pelosi-facebook-video.html
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.
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.
'Snapchat Employees Abused Data Access to Spy on Users'
Could makepkg on #ArchLinux be improved to use all available cores when compressing the tar.xz? 🤔