Not mad about an estimated usage bill of $8k per month.
Just hire a developer
towerful
joined 2 years ago
24 yaml files for config. The single src folder
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.
That's it re-stoking the internal combustion engine. It's perfectly fine
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.
I dunno why that didn't work. It worked so well for geopolitics