2,388 karma · joined November 4, 2014
Flakes are not great however, they're what happens when you "overdo it", sadly the momentum is behind flakes because some UX/DX improvements came along with them (lockfile in repo).
I think the stdenv being built on bash is worse than Nix language.
Module system errors can be very hard to troubleshoot because of lazy eval, sadly I can't see a reasonable solution without worse tradeoffs :(
"Our review of the account(s) and/or content named in your report has concluded. We have determined that one or more violations of GitHub’s Terms of Service have occurred and have taken appropriate action in response."
It took 2h40m, genuinely impressed how quick the turnaround was :)
https://github.com/Lillecarl/lix/commit/9ac72bbd0c7802ca83a9...
I'm not ashamed to use AI if it improves my output, people draw the line of "acceptable use" differently just like drug addicts talk shit about each other's drugs to justify their own. I think honesty is more important than cleanliness.
In high school CAD/CAM we used various CAD programs for designing (sculpting?) things and then imported them into CAM to generate g code programs, set tool constraints and such
That one time when an AZ goes down and your infra successfully fails over to the other two isn't worth it for a lot of my scale companies, ops consultants seem to be chasing high cloud spend to justify their own high cost. I also factor in that I live in Sweden where most infrastructure outages are exceptionally rare.
Ofc it depends on what kind of company you are and what you're providing.
I wrote a tool called "easykubenix" that works in a similar way, render the chart in a derivation, convert the YAML to JSON, import JSON into the Nix module structure and now you're free to override, remove or add anything you want :)
It's still very CLI deploy centric using kluctl as the deployment engine, but there's nothing preventing dumping the generated JSON (or YAML) manifests into a GitOps loop.
It doesn't make the public charts you consume any less horrible, but you don't have to care as much about them at least
Old is new again :)
Just speculation though, it's more likely they just paid the right people off.
This is not the same as surveillance, that's internal affairs. This is external affairs.
Chinese Teslas had higher standards early on, panels aligned and such.
https://en.wikipedia.org/wiki/List_of_countries_by_carbon_di...
Do more with the shit you have is a good idea, this bike isn't.
Configure the init flags to disable all controllers and other doodads, deploy them yourself with Helm. Helm sucks to work with but someone has already gone through the pain for you.
AI is GREAT at K8s since K8s has GREAT docs which has been trained on.
A good mental model is good: It's an API with a bunch of control loops