Came here to say that. I’d rather spend 4 days automating my local development environment than spend half an hour every time figuring out why my deps are mismatched, or what is the correct env var to put over there.

If everyone on the team wastes 10 minutes on random BS every day, it is thousands of money compounding over months.

That was mean as heck though. One can be correct and approachable at the same time.

My sibling in craft, docs are not “boilerplate”, they are the main freaking sauce. That is why they should be written by a human who understands stuff. I genuinely believe you are missing the point of the practice.

What’s so bad about the Rust compiler? I know it’s slow, but given all the analysis it’s doing, it makes sense. And, from my own experience, setting correct optimization levels for dependencies along with a good linker makes incremental builds plenty fast.

I have been toying with the idea of forking Servo to make a scriptable keyboard-driven browser, like Nyxt but with something else instead of Lisp.

Probably too huge of a project for one hooman though.

Cactus - Cacti Sarcophagus - Sarcophagi Octopus - Octopi Campus - Campi Mouse - Mice House - Hice

I’ve been using Git professionally as a software developer for 15 years, and I think it sucks quite hard. There is always a dosen ways to do the same thing, it occupies tons of hardware space, it’s log is unstructured data that has to be parsed. Git CLI is an incomprehensible mess of bloat and misnomers, so no matter what team/project you are working on, there is always going to be 1-5 Git commands they’ll tell “you are NEVER supposed to use”.

I’ve completed my courses on Git, I’ve worked with CI/CD, onboarded younger developers, read “Git Koans”, and I haven’t seen even a theoretically convenient VCS until someone showed me Pijul.

Git is mess, it sucks that we are stuck with it, and every time someone says it’s the best VCS we have, it saddens me.