diarrhea

6 ms·

31.
by diarrhea 10mo ago
> git on the command line is the power tool. The VS Code plugin is the training wheels version. I don't disagree with your underlying point, but git is perhaps the worst example. It is a horrible tool in several ways. Powerful yes
32.
by diarrhea 10mo ago
All IDEs including VSCode have fuzzy-finding for files, and fuzzy-finding for symbols as well. Between these, I never find myself using the file tree, except when it's the best tool for the job ("what other files are in this direc
33.
by diarrhea 10mo ago
No thank you... One of the primary things shells are supposed to excel at is file system navigation and manipulation, but the experience is horrible. I can never get `cp`, `rsync`, `mv`, `find` right without looking them up, despite trying
34.
by diarrhea 10mo ago
> just another kind of complex? To some extent yes. If all you have is 2 GitHub Actions YAML files you are not going to reap massive benefits. I'm a big fan of CUE myself. The benefits compound as you need to output more and more ar
35.
by diarrhea 11mo ago
The OS is my GC. It's why I segfault liberally.
36.
by diarrhea 11mo ago
A similar problem applies to Go, just inverted. Take iteration. The vast majority of use cases for iterating over containers are map, filter, reduce. Go doesn't have these functions. That's very simple! All Go developers are align
37.
by diarrhea 11mo ago
Good question. For fds their Drop implementation closes them, yes. Rust Mutexes will be poisoned on panic (not unlocked). Not sure about futexes.
38.
by diarrhea 11mo ago
> This is a non sequitur. Both Rust and Zig and any other language has the ability to end in an exception state. There are degrees to this though. A panic + unwind in Rust is clean and _safe_, thus preferable to segfaults. Java and Go ar
39.
by diarrhea 1y ago
It might indeed be more difficult to push obsolete technology ever further.
40.
by diarrhea 1y ago
A DB action and audit emission have to run transactionally anyway. So on cancellation, the transaction times out and nothing is written. Bad but safe. The problem is the same on other platforms. For example, what if writing to the DB throws
41.
by diarrhea 1y ago
Great to see this land. When I set up n8n last year I was thoroughly confused at the lack of state management. I ended up storing as JSON in a remote blob “database”, a horrible hack.
42.
by diarrhea 1y ago
Not the OP but I’m a big fan of this pattern as well. At work we generate both k8s manifests as well as application config in YAML from a Cue source. Cue allows both deduplication, being as DRY as one can hope to be, as well as validation (
43.
by diarrhea 1y ago
Note that the study is just n=13 and on subjects without ADHD.
44.
by diarrhea 1y ago
Go on. I respect your hourly rate.
45.
by diarrhea 1y ago
I have not, thanks for the suggestion though. A second challenge with the particular setup I’m trying is peer authentication with Postgres, running bare metal on the host. I mount the Unix socket into the container, and on the host Postgres
46.
by diarrhea 1y ago
One challenge I have come across is mapping multi-UID containers to a single host user. By default, root in the container maps to the user running the podman container on the host. Over the years, applications have adopted patterns where co
47.
by diarrhea 1y ago
Perhaps the best terse summary of Kafka I have come across yet.
48.
by diarrhea 1y ago
$ golangci-lint linters | wc -l 107 That is a long list of linters (only a few enabled by default however). I much prefer less fragmented approaches such as clippy or ruff. It makes for a more coherent experience and sure
49.
by diarrhea 1y ago
> Now if only Go was consistent about methods vs functions This also hurts discoverability. `slices`, `maps`, `iter`, `sort` are all top-level packages you simply need to know about to work efficiently with iteration. You cannot just `it
50.
by diarrhea 1y ago
Yes, Python is massively ahead there. The largest wart is that types can be out of sync with actual implementation, with things blowing up at runtime -- but so can Go with `any` and reflection. Python, for a number of years at this point, h
51.
by diarrhea 1y ago
Using SQLite in Go is also not for the faint of heart either.
52.
by diarrhea 1y ago
> massive linter framework I wonder why that ended up being necessary... ;)
53.
by diarrhea 1y ago
> Rust has multiple ways of handling Strings No, none outside of stdlib anyway in the way you're probably thinking of. There are specialized constructs which live in third-party crates, such as rope implementations and stack-to-heap
54.
by diarrhea 1y ago
> colorless Functions are colored: those taking context.Context and those who don't. But I agree, this is very faint coloring compared to async implementations. One is free to context.Background() liberally.
55.
by diarrhea 1y ago
Go is not thread safe. It even allows data races in its own runtime. Go 1.25 fixed a nil-checking error that has been sitting in the runtime for two years. Generally, Go will let you compile just about anything when it comes to channels, mu
56.
by diarrhea 1y ago
One of my favorite features of jj is file watching. Once set up, jj will snapshot the repo on every filesystem event. This means on every file save, you get a git commit! It provides arbitrarily fine-grained commit history, and works across
57.
by diarrhea 1y ago
In colocated repos, running both git and jj commands is supported. I use it in release workflows which require git tags, which jj does not support creating. However, jj will pick up ("import") on git-created tags just fine after
58.
by diarrhea 1y ago
One problem remains: jj makes it a breeze to parallelize work, but descendant changes will then end up with multiple parents. But PRs cannot target multiple target branches at once - so you cannot point them at both at once. cf. https:&#x2
59.
by diarrhea 1y ago
Interesting! What made you opt for DBOS over Temporal?
60.
by diarrhea 1y ago
This is extremely alarmist. If you are on Mac, developing anything at all with Python, those are going to be your tools. If you randomly guessed at developer setups, that is going to be one of the most common setups as well. What's nex

More ›