turboponyy

5 ms·

1.
by turboponyy 3mo ago
Not really. If I'm using a linter, I go and configure the strictest possible ruleset, and only disable rules when justified on a need-by-need basis. It's just a matter of discipline.
2.
by turboponyy 8mo ago
I guess the Gnome-specific part is that Gnome comes with the Nautilus file browser, and the instructions add a script for Nautilus. But yea, this will work as long as you have imagemagick and Nautilus installed.
3.
by turboponyy 8mo ago
I'm currently using niri (was previously using Hyprland). Having used dwm-like tiling window managers for most of the time, I don't really care for the scrolling or dynamic workspace aspects of niri at all - in fact, I kinda disli
4.
by turboponyy 9mo ago
Exactly. "GitHub actions bad" is a valid take - you should reduce your use to a minimum. "My build failed because of GitHub actions couldn't install a dependency of my build" is a skill issue. Don't use GitHub
5.
by turboponyy 9mo ago
Samesies - need a Majjit before I can consider trying it out.
6.
by turboponyy 10mo ago
> If Vizo never licensed the software to you under the GPL [...] That may be true. > [...] you can't say they violated the GPL. That does not necessarily follow. If they used GPL-licensed code in their product, they may be obliga
7.
by turboponyy 10mo ago
No, you really don't have to. Partially complete software can have a lot of value too. Anyone can fork it and quickly add the i18n (or just translate into a different language) for their own purposes. People will likely want to contr
8.
by turboponyy 10mo ago
I have the same disagreement. TypeScript with its structural and pseudo-dependent typing, somewhat-functionally disposed language primitives (e.g. first-class functions as values, currying) and standard library interfaces (filter, reduce, f
9.
by turboponyy 10mo ago
It is unique and looks cool. When it comes to providing an enjoyable blog post reading experience, it really does creep into the "fuck off" territory for me, though.
10.
by turboponyy 10mo ago
Even better is "" since it's not really adding anything
11.
by turboponyy 11mo ago
`for` loops are a superfluous language feature if your collections have `map` for transformations and `forEach` for producing side effects
12.
by turboponyy 1y ago
It's quite nice for the following reasons: - Image previews (for file management with dired/dirvish) - PDF viewing - In-buffer images (e.g. profile pictures in git log with Magit) - Browsing simple HTML pages (e.g. API docs) There
13.
by turboponyy 1y ago
You only need that much protein if you're trying to build muscle. The amount needed for a generally healthy diet is much lower.
14.
by turboponyy 1y ago
If that's something you care about, then don't define your CI build in terms of GitHub Actions steps. Instead, call your build that takes care of using whichever version of Node you want in CI.
15.
by turboponyy 1y ago
I actually completely agree with both the article and your point that your code should directly communicate your intent. The angle I'd approach it from is this: recording whether an email is verified as a boolean is actually misguided
16.
by turboponyy 1y ago
I have Emacs set up like VSCode. I feel it surpasses VSCode, even because it's Emacs.
17.
by turboponyy 1y ago
Can you edit commits by adding on only parts of your "staging" area? Because that's my workflow. I produce a few focused and semantically coherent commits that I'd like to apply to the codebase, where each keeps the code
18.
by turboponyy 1y ago
> While I can jump through hoops to compile JavaScript into a binary, such wouldn't feel "solid". And the very point of writing a native program in the first place is to make it feel solid You can use Bun to compile to nat
19.
by turboponyy 1y ago
Or, in a browser that's presumably displaying the website: btoa("Hello World")
20.
by turboponyy 1y ago
"Look what they need to mimic a fraction of our power" - some Emacs user, probably
21.
by turboponyy 1y ago
> It turns out that there’s a way to test this experimentally. Do a double blind experiment, just like in science. If you can tell which monitor is 240hz more than randomly, then it matters. Ditto for the pointer updates. You can easily
22.
by turboponyy 1y ago
Yes, because the visual feedback on your client matters as well (faster reaction times). Also, it means each frame is more recent. Also, higher refesh rates reduce the mean variance between the timestamps of rendered frames offered by the G
23.
by turboponyy 1y ago
Yea, the examples are wrong, and I'd interpret them the same way. The principle is something I agree with and try to abide by, though.
24.
by turboponyy 1y ago
The modeness of vi does add friction in some cases, but it's a minor gripe, really. Vi is incredibly well-suited and ergonomic for text editing, and switching between the modes is efficient, since often times you want to begin typing t
25.
by turboponyy 1y ago
> It's better to say that some functions like "does this program halt?" simply don't exist. Let f : (p: String) -> Boolean equal the function that returns True if p is a halting program, and False otherwise
26.
by turboponyy 1y ago
Glossing over some details, the build artifact and build definition are equivalent in Nix. If you know the build definition, you can pull the artifact from the cache and be assured that you have the same result.
27.
by turboponyy 1y ago
You can do this in newer versions of Java (not sure since which), for what it's worth.
28.
by turboponyy 2y ago
Once you try a rolling-release distro you realize it's actually a very good idea
29.
by turboponyy 2y ago
Docker can be used to create reproducible environments (container images), but can not be used to reproduce environments from source (running a Dockerfile will always produce a different output) - that is, the build definition and build art
30.
by turboponyy 2y ago
Yes. GitHub actions can be just a thin wrapper to call any Nix commands that you can run locally. > How do you automate running tests You just build the Nix derivation that runs your tests, e.g. `nix build #tests` or `nix flake check` in

More ›