towerful

Yeh, KDE plasma

I use EndeavourOS (which is arch).

Most of my programming is web stuff. So it builds to containers and using VS Codes dev containers takes care of all issues relating to arch's rolling release (IE needing a specific version of a language).
Ie, I work in containers and I build to container and I run containers for all my code (except ESP32 platformio. Unfortunately I haven't migrated that away from windows. So I dual boot)

If I was doing GUI desktop apps, I imagine I would need something other than dev containers.
But that's not what I do. Considering all I do is docker, k8s, linux admin, web frontend/backend that is platform agnostic (but ultimately runs on Linux)... I'm not tied to any OS.
Windows is annoying, I am not a fan of osx nor Apple, I use Linux everyday... So my OS might as well be Linux.
And Arch & EndeavourOS are nice and just work.
For a VPS/server, I use Debian (or Talos OS for k8s). But that's all headless.

I'm lucky in that I freelance and the companies I work for are good companies.
I've never had to cancel anything because of EndeavourOS, it's never broken on me (I've only had windows break the EFI partition, which it can do to any distro - until you disable fast boot and stuff), it's never gotten in my way (or if it has, it's lead to a better solution - like VS Code dev containers). It's been really really enjoyable.

I'm sure that I could use any distro in my position, tbh.
So, probably not helpful overall.

Ayyy, remember how Canada capitulated on the digital service tax.
https://www.bbc.co.uk/news/articles/c62553ywn77o
https://www.canada.ca/en/department-finance/news/2025/06/canada-rescinds-digital-services-tax-to-advance-broader-trade-negotiations-with-the-united-states.html

Then trump threatens new tarrifs?
https://www.bbc.co.uk/news/articles/cvg819n954mo

(I'm struggling to find new sources,. cause everything is about dropping the DST to allow further trade talks. Not the timeline of DST dropping and the further US tariffs. Maybe these are coincidental, maybe there was always gonna be more Canadian tariffs. Either way, it doesn't matter. Canada got more blanket tariffs regardless of what they did. Speaks volumes to everyone else dealing with trump)

Trump is destabilising international trade. This doesn't benefit the US. At all.

Huh, ai++ appears

I really wish there was a way to enforce transparency of docker env vars.
I get that it's impossible to make it a part of docker, env vars get parsed by code and turned into variables. There is no way that docker can enforce it, cause a null/undefined check with a default value is all that would be needed to subvert checks by docker, and every language uses a different way to check env vars (eg .env files, environment init scripts, whatever).
And even then, the env var value could be passed through a ridiculous chain of assignments and checks.
And, some of those 'get env var' routines could be conditional. Not all projects capture all env vars during some initial routine.

I've spent hours (maybe days) trawling through undocumented env vars trying to figure out their purpose, in order to leverage them in docker/k8s stacks.
I wish there was something.

Thankfully, a bit of time spent with a FOSS project and reviewing the code does shed light on hidden env vars.
And a PR or 2 gets comments and documentation updated.
Open source is awesome

To Our 12 Million Fellow Subnauts,

— Inevitable Leadership Change Driven by Project Abandonment–Despite Holding 90% of Earnout for Themselves

First and foremost, we sincerely thank you for your continued support, passion, and unwavering dedication to Subnautica. We wish to provide clarity on the recent leadership changes at Unknown Worlds, a creative studio under KRAFTON.

Background of Leadership Change

KRAFTON deeply values Subnautica’s unique creativity and immersive world-building. To provide fans with even better gaming experiences, we acquired Unknown Worlds, fully committed to supporting Subnautica’s future success. We collaborated closely with the studio’s leadership, who were central to the creation of the original Subnautica, to foster the optimal environment for a successful Subnautica 2.

Specifically, in addition to the initial $500 million purchase price, we allocated approximately 90% of the up to $250 million earn-out compensation to the three former executives, with the expectation that they would demonstrate leadership and active involvement in the development of Subnautica 2.

However, regrettably, the former leadership abandoned the responsibilities entrusted to them. Subnautica 2 was originally planned for an Early Access launch in early 2024, but the timeline has since been significantly delayed. KRAFTON made multiple requests to Charlie and Max to resume their roles as Game Director and Technical Director, respectively, but both declined to do so. In particular, following the failure of Moonbreaker, KRAFTON asked Charlie to devote himself to the development of Subnautica 2. However, instead of participating in the game development, he chose to focus on a personal film project.

KRAFTON believes that the absence of core leadership has resulted in repeated confusion in direction and significant delays in the overall project schedule. The current Early Access version also falls short in terms of content volume. We are deeply disappointed by the former leadership’s conduct, and above all, we feel a profound sense of betrayal by their failure to honor the trust placed in them by our fans.

KRAFTON’s Full Support for the Dedicated Development Team

To uphold our commitment to provide you with the best possible gaming experience, we made the difficult yet necessary decision to change the executive leadership. Subnautica 2 has been and continues to be actively developed by a dedicated core team who share genuine passion, accountability, and commitment to the game. We deeply respect their expertise and creativity and will continue to provide full and unwavering support, enabling them to focus solely on delivering the exceptional game you deserve.

KRAFTON’s Commitment to its Promises in Rewarding Employees

Additionally, KRAFTON has committed to fair and equitable compensation for all remaining Unknown Worlds employees who have continuously and tirelessly contributed to Subnautica 2’s development. We believe that the dedication and effort of this team are at the very heart of Subnautica’s ongoing evolution, and we reaffirm our commitment to provide the rewards they were promised.

Fans will always remain at the center of every decision we make at KRAFTON. Moving forward, we promise transparent communication and continued efforts to sustainably develop and expand the beloved Subnautica universe.

Honoring your trust and expectations is a core tenet at KRAFTON. We are committed to repaying your patience with an even more refined and exceptional gaming experience.

Sourced from a popup on their homepage krafton.com

It's going to be an interesting lawsuit.
I didn't know the 250m bonus was 90% for execs.
But I still don't trust krafton

One of the best robot chicken scenes.
I was in tears the first time I saw it

Interesting, I might check them out.
I liked garden because it was "for kubernetes". It was a horse and it had its course.
I had the wrong assumption that all those CD tools were specifically tailored to run as workers in a deployment pipeline.

I'm willing to re-evaluate my deployment stack, tbh.
I'll definitely dig more into flux and ansible.
Thanks!

Oh, operators are absolutely the way for "released" things.

But on bigger projects with lots of different pods etc, it's a lot of work to make all the CRD definitions, hook all the events, and write all the code to deploy the pods etc.
Similar to helm charts, I don't see the point for personal projects. I'm not sharing it with anyone, I don't need helm/operator abstraction for it.
And something like cdk8s will generate the yaml for you to inspect. So you can easily validate that you are "doing the right thing" before slinging it into k8s.

Everyone talks about helm charts.
I tried them and hate writing them.
I found garden.io, and it makes a really nice way to consume repos (of helm charts, manifests etc) and apply them in a sensible way to a k8s cluster.
Only thing is, it seems to be very tailored to a team of developers. I kinda muddled through with it, and it made everything so much easier.
Although I massively appreciate that helm charts are used for most projects, they make sense for something you are going to share.
But if it's a solo project or consuming other people's projects, I don't think it really solves a problem.

Which is why I used garden.io. Designed for deploying kubernetes manifests, I found it had just enough tooling to make things easier.
Though, if you are used to ansible, it might make more sense to use ansible.
Pretty sure ansible will be able to do it all in a way you are familiar with.

As for writing the manifests themselves, I find it rare I need to (unless it's something I've made myself). Most software has a k8s helm chart. So I just reference that in a garden file, set any variables I need to, and all good.
If there aren't helm charts or kustomize files, then it's adapting a docker compose file into manifests. Which is manual.
Occasionally I have to write some CRDs, config maps or secrets (CMs and secrets are easily made in garden).

I also prefer to install operators, instead of the raw service. For example, I use Cloudnative Postgres to set up postgres databases.
I create a CRD that defines the database, and CNPG automatically provisions all the storage, pods, services, config maps and secrets.

The way I use kubernetes for the projects I do is:
Apply all the infrastructure stuff (gateways, metallb, storage provisioners etc) from helm files (or similar).
Then apply all my pods, services, certificates etc from hand written manifests.
Using garden, I can make sure things are deployed in the correct order: operators are installed before trying to apply a CRD, secrets/cms created before being referenced etc.
If I ever have to wipe and reinstall a cluster, it takes me 30 minutes or so from a clean TalosOS install to the project up and running, with just 3 or 4 commands.

Any on-the-fly changes I make, I ensure I back port to the project configs so when I wipe, reset, reinstall I still get what I expect.

However, I have recently found https://cdk8s.io/ and I'm meaning to investigate that for creating the manifests themselves.
Write code using a typed language, and have cdk8s create the raw yaml manifests. Seems like a dream!
I hate writing yaml. Auto complete is useless (the editor has no idea what format the yaml doc should take), auto formatting is useless (mostly because yaml is whitespace sensitive, and the editor has no idea what things are a child or a new parent). It just feels ugly and clunky.

Google has a "search tools" drop down menu (on mobile it's at the end of the list of images/shopping/news etc).
It's default set to "all results". I believe changing it to "verbatim" is closer to the older (some would say "dumber", I would say "more predictable") behaviour

If a God were to appear and demonstrate all kinds of supernatural activity and capability, I think I'd have to renounce my atheism.

I would also renounce my atheism and become fully anti-theism.
The god is clearly not benevolent, not kind, not caring. The god can go fuck themselves.

Trumps track record over the past decades cannot be forgiven