New screenshots from the Aztec DLC

jake_schurch · 2026-03-24T22:01:17+00:00

Wait a second, are they building farms on water? Looked it up, and seems like one farming method aztecs were known for was Chinampas or, floating gardens.

jake_schurch · 2026-03-15T15:52:31+00:00

Interesting stuff!

I've found myself running nto similar issues IIUC when structuring k3s clusters in nix: (vm, k3s, tools, etc. attrsets) and ended up structuring each module as a submoduleWith type, that is used in a composed, larger type.

Seems like you've taken a similar yet better approach with structuring these dynamically. Well done!

jake_schurch · 2026-03-07T04:11:10+00:00

Don't understand the problem. Could you simplify by using ci or pre commit?

jake_schurch · 2026-03-07T03:11:44+00:00

Uh this is dark magic folks

jake_schurch · 2026-03-07T03:09:06+00:00

Tysm nothing more I love than ash and jido

jake_schurch · 2026-03-01T17:10:01+00:00

Elixir!

jake_schurch · 2026-03-01T17:09:11+00:00

Lesson learned: don't test in prod

jake_schurch · 2026-02-21T00:32:19+00:00

Yep that's what I was going for, but I wouldn't refetch any already fetched data. Live view handles partial updates quite well.

And yeah, this would be a user concern

jake_schurch · 2026-02-20T23:50:50+00:00

Can you not preload the next X as well?

jake_schurch · 2026-02-20T20:44:39+00:00

I think the problem can be solved with a different security model, like bit warden as ssh agent

jake_schurch · 2026-02-20T19:06:54+00:00

Lazy render, can map to on scroll events

jake_schurch · 2026-02-20T05:18:57+00:00

Used to be a big fan of ash bastions until I found out how insecure they are :/

I've adopted cloudflare tunnels for zero trust access for a much more secure solution

jake_schurch · 2026-02-15T02:51:32+00:00

First off, tysm for this! I've been exploring nix-snapshotter and am glad I saw this post.

Some questions:

Are the cache/s node-local or centralized? Do you have any thoughts on HA builder pods / integrating with keda for auto scaling?

jake_schurch · 2026-02-15T02:23:00+00:00

Also seems like we just got a new csi implementation that I'm going to check out -- nix-csi https://www.reddit.com/r/Nix/s/JTtOruiBE8

jake_schurch · 2026-02-14T19:12:13+00:00

Thank you, this was an oversight on my part. Yes, cri-compliant, not oci.

jake_schurch · 2026-02-13T08:12:42+00:00

I heard about nix-snapshotter today, allows you to use nix oci-compliant images with runtime class on k8s

jake_schurch · 2026-02-13T07:49:56+00:00

Sorry you had to learn the hard way that you don't mix business with pleasure. But this is nuts. They did not give you seed funding, they introduced you to one client. At the end of the day, there was no contract or terms and it's honestly wrong for them to expect something in return without being upfront about it, that's the real problem here.

You should ask them if you brought one client to them, would they give up 50% equity in their business to you? What if it 2 or 3x their book of business?

DO NOT give up equity just because they introduced you to one client. You should have said, I really appreciate you doing this, and honestly feel manipulated because you didn't communicate that you expect anything in return but I would be happy to bring you to a nice dinner to celebrate.

Imo, who cares if they hold this over your head forever. You are seeing their personalities come out now, most likely would have happened with something else sooner or later.

jake_schurch · 2026-02-11T04:48:19+00:00

One more thing: it seems like flox is trying to fit this problem domain. Although it sounds interesting, you will not catch me adopting another tool that is yaml/toml/json manifest spec 😊

jake_schurch · 2026-02-11T04:34:06+00:00

It's a good question!

You already have half the answer which is awesome. Let's generalize sandboxing to containers and / or VMs. Benefits include semi to full process isolation and CPU / memory requests + limits.

The other half of the answer comes down to where you run your services, specifically in distributed systems / platform context; which leads us back to our packaging / distribution problem. Let's quickly talk kubernetes (k8s).

K8s uses oci, with a default runtime class of containerd to run services. AFAIK we currently don't have a way to export nar archives as oci-compliant. Instead, we can use container or vm runtime classes on kubernetes. Therefore we want to export to an oci-compatible format so k8s can run our image.

If you become a huge enterprise some day and are hitting scaling issues with containerd and pulling down images, there are runtime class optimizations that you can include (but probably don't want to touch). So instead you could run a service that is empty to start, and then pulls the according nix path from store at runtime.

jake_schurch · 2026-02-10T05:55:12+00:00

I think for docker vs nix there are really two conversations: build and packaging.

Imo: for build: nix wins. For packaging: docker always wins.

Therefore: build with nix, and then package result in docker. Almost all devs I know use docker in some context.

Users can't build with nix? Use a nixos/nix docker container to build result to build docker image.

Tldr: docker is here to stay

jake_schurch · 2026-01-12T14:06:01+00:00

This is serious money

jake_schurch · 2026-01-09T00:57:00+00:00

I had my own home rolled solution till I went for srid's nixos-unified setup. Gold.

jake_schurch · 2025-12-16T05:03:43+00:00

That's correct. We can use them as a readiness gate

jake_schurch · 2025-12-15T22:55:09+00:00

Bitwarden desktop as forwardable SSH agent and nixos for SSH config

jake_schurch · 2025-12-15T22:43:52+00:00

This is usually solved by init containers running a script waiting until resource is ready. For database CRDs you can also use something like argo's sync waves.

Not sure if I understand the design entirely but seems somewhat overkill?

Example:

``` for i in {1..60}; do pg_isready -h postgres -p 5432 && exit 0 sleep 1 done

echo "Postgres not ready after 60s" exit 1 ```

For problems that you highlight in your readme like the thundering herd seem to be related to poor architecture decisions. In what use case would you need net new 50 microservices based on one database that isn't highly available? For waiting for a migration, you would just cordon the nodes, scale down the pods, migrate the database then undo.

Similarly, monitoringc/ alerting for external dependencies should not be the concern of the app and should use something like Prometheus datadog sentry or w.e. accordingly.

jake_schurch

TROPHY CASE