rgoulter

13 ms·

151.
by rgoulter 1y ago
It's funny to see Helix mentioned, without kakoune being mentioned. Helix is a really nifty terminal editor. It aims to be nice out-of-the-box, to have good LSP support, DAP support, and Tree-Sitter support. Compared to vim's &quo
152.
by rgoulter 1y ago
With chess, there are some pathological cases where humans outperform the computers. I recall seeing an example where the position was almost completely deadlocked. With the weaker engines that run on browsers, you'll still catch cases
153.
by rgoulter 2y ago
Right. This is one case where I've found writing code with LLMs to be effective. With some unfamiliar tool I don't care about too much (e.g. GitHub Actions YAML or some build script), I just want it to work, & then focus on ot
154.
by rgoulter 2y ago
The 1 million token context window also means you can just copy/paste so much source code or log output.
155.
by rgoulter 2y ago
> I honestly wonder why there are such divergent opinions between say git and Nix? Nix is: 1. difficult & different, where similar-ish tools are straightforward & familiar, (e.g. cloud-init, ansible, vs NixOS; or devcontainers us
156.
by rgoulter 2y ago
> preferrably with 36 or less keys. I think it's worth emphasising that these small keyboards bring the full functionality of the keyboard to within reach of the hands resting on home row. They aim to increase comfort by reducing ha
157.
by rgoulter 2y ago
To an extent, Vim and Emacs have a similar issue, especially if you spend time customising these. Often, the benefits from using an improved tool outweigh the costs of it being non-standard.
158.
by rgoulter 2y ago
> I can’t really relate to “I need to type faster!” programmer optimizations, nor complaints about things like static typing slowing people down because it’s a few more characters... One common loop in programming is "hypothesize, t
159.
by rgoulter 2y ago
The best value-for-effort upgrade to keyboards for coders would be to get a keyboard where each thumb can use two-three keys each (rather than just being able to use a single giant spacebar). Stenography looks like 'high effort, high r
160.
by rgoulter 2y ago
> I invite anyone making that claim to find me an "advanced amateur" (as the article says of the LLM's level) chess player who ever makes an illegal move. Anyone familiar with chess can confirm that it doesn't really
161.
by rgoulter 2y ago
A quick search does bring up this page, which mentions an observational study where people who drank more diet soda gained more weight. https://www.webmd.com/diet/features/diet-sodas-and-weight-ga... But, again, &
162.
by rgoulter 2y ago
The article doesn't lay out a good argument for why "ultra-processed" is a more significant comparison than considerations like "too much sugar is bad", "too much salt is bad". "too much sugar is bad&
163.
by rgoulter 2y ago
Tig looks like a wonderful tool for all kinds of git interaction. I'm not too familiar with tig, but it looks like it does a lot of what Emacs' magit does. AFAICT, there are some things I find useful in magit that tig doesn't
164.
by rgoulter 2y ago
Jupyter Notebooks can be useful for more than small snippets of code. A Ruby Jupyter kernel would be useful if you've got a Ruby codebase, and want to run a Notebook using some of that code.
165.
by rgoulter 2y ago
> for a full system ... does nix still make sense? In many ways, Nix is often "second best at everything". -- Since Nix can be difficult to deal with, it may often be a better choice to use some other tool for any particular us
166.
by rgoulter 2y ago
> I've seen a lot of complaints about the language, but a lot of praise and love of the idea I think when people say they like the idea of nix, they're referring to how it builds packages from programmatic package formulae into
167.
by rgoulter 2y ago
Just over a month ago there was a flashpoint in community tensions, as some expressed their concerns over the project's governance. https://news.ycombinator.com/item?id=40107370 As a quick summary, they were concerned
168.
by rgoulter 2y ago
"write code" isn't a uniform task. Sometimes writing code involves having built a good mental model of the domain problem & parts of the codebase. Sometimes writing code involves fairly straightforward manipulation of too
169.
by rgoulter 2y ago
> Other than safety and the like. I think these are some good points: https://github.blog/2023-08-30-why-rust-is-the-most-admired-... On the one hand, "safety" avoids the "use after free" or other bug
170.
by rgoulter 2y ago
> I tried to use them but haven't really stuck with it. I think it's domain dependent. It's easy to recall things you encounter frequently, and difficult to recall things which are rarely encountered. Failing to recall som
171.
by rgoulter 2y ago
> ...idempotent, or at least stateless... Even for a Makefile, "start", "test", "install" are likely to be phony (and not literally refer to files with those names). The execution of a "start" task
172.
by rgoulter 2y ago
File dependencies are useful as part of a build system. But often tasks are a step removed from that. Targets like "all" and "clean" are good examples of useful tasks to have, even if they're unrelated to files. A &
173.
by rgoulter 2y ago
e.g. Google's Gemini's output had some rather embarrassing biases in its outputs; to the point where asking it to "draw a 1943 German soldier" resulted in images of women and black soldiers. https://www.nytime
174.
by rgoulter 2y ago
> I'm done with [Ubuntu], now Debian only with no regrets or downsides so far. There's no OS in the world which has both of "requires no maintenance" and "receives all upgrades forever".
175.
by rgoulter 2y ago
> Nix can handle it, but can the user? Learning how to write Nix in order to get it to do what you want can be tough, yeah. https://www.tweag.io/blog/2024-05-02-right-words-right-place... In this recent post discuss
176.
by rgoulter 2y ago
Plus, Nix allows for installing the same versions of those programs everywhere you're using Nix.
177.
by rgoulter 2y ago
> No, but it does define how (and where) I will write that code. I don't follow your rationale here. e.g. many people write packages for their own "nix user repository". https://github.com/nix-community&#x2
178.
by rgoulter 2y ago
> much better to say how it's better than the thing that came before it. I thought the mention of Rust, and versioning the language itself (like what Rust does) covers this. That, and, the last few NixCpp revisions apparently had so
179.
by rgoulter 2y ago
This is partly fair and partly unfair. I think it's reasonable to say that the nixpkgs codebase is a behemoth that can be quite difficult to understand. I think "nix and multiple versions of a package" is more nuanced. In tha
180.
by rgoulter 2y ago
> What's the goal here? ... Am i missing something? Forks tend to be for social reasons, rather than technical. e.g. NeoVim was forked out of frustration relating to a complicated changeset being rejected. Or OpenTofu over licensing

More ›