turboponyy

13 ms·

31.
by turboponyy 2y ago
nix develop
32.
by turboponyy 2y ago
You shouldn't pass invalid values to a function. If a function can return some sensible value for some input, then the input is not invalid - even if the return type is an error by name. Ideally, you can constrain the set of inputs to
33.
by turboponyy 2y ago
Containerizing an application is far easier than packaging an application for Nix - I think most avid Nix users would agree with that. The reason why Nix users "refuse" to containerize is that Nix packages and their associated eco
34.
by turboponyy 2y ago
There's always the escape hatch of marking a derivation as impure. However, most tests should really have no reason to be impure by design. And tests that do depend on side effects might as well be re-evaluated every time.
35.
by turboponyy 2y ago
Nix solves this as a byproduct (as it does with many things) of its design. You can have your tests be a "build", where the build succeeds if your tests pass. Any builds can be cached, which means you're essentially caching t
36.
by turboponyy 2y ago
That summary is nearly identical to the abstract of the paper...
37.
by turboponyy 2y ago
The thing is, Nix is not Yet Another Tool, it is the tool.
38.
by turboponyy 2y ago
Except the completion of the preparation of various nodes may have to be synchronized to that of other nodes - i.e. the steps can not be parallelized in the general case. Some nodes expire, experience changes in temperature or moisture dist
39.
by turboponyy 2y ago
Um, my session with GitHub never expires - weird.
40.
by turboponyy 2y ago
This is literally just a skill issue
41.
by turboponyy 2y ago
This is inherently a Hard Problem™, since completions may require evaluating arbitrary derivations (e.g. building a custom Linux kernel). For "what symbols are available", the nil LSP implementation[1] works for anything in scope
42.
by turboponyy 2y ago
What's so bad about it? Putting aside the poor typing (the lack of proper typing is a shame, so valid criticism), I actually really like the language - it's genuinely a great DSL for the particular problems it's supposed to h
43.
by turboponyy 2y ago
Somewhat related: https://github.com/nix-community/NixOS-WSL
44.
by turboponyy 2y ago
I love how the rules imply that not providing these proofs and applying them is against the rules.
45.
by turboponyy 2y ago
Not to be dismissive, but because I like it - it just sits right with me.
46.
by turboponyy 2y ago
Neither have I; and no, I don't - I misinterpreted what you said. But I don't see why LSP servers shouldn't support this, still. I'm not sure if the LSP specification allows for this as of current, though.
47.
by turboponyy 2y ago
I like them because it reinforces the idea that functions are just values like any other - having a separate keyword feels like it is inconsistent.
48.
by turboponyy 2y ago
There's no reason they have to work one symbol at a time - that's just a missing feature in your language server implementation. Some language servers support modifying the symbols in contexts like docstrings as well.
49.
by turboponyy 2y ago
Magit is possibly one of the best pieces of software ever written. Its discoverable and intuitive interface makes complex operations trivial and trivial operations blazingly fast and frictionless. The interface you use does matter. Magit
50.
by turboponyy 2y ago
More notably, then you'd have to use Ansible.
51.
by turboponyy 2y ago
Minecraft was immensely popular before you could starve, but I agree.
52.
by turboponyy 2y ago
I empathize with this point of view - if not in any other way then in principle. However, as a counterpoint, I'd suggest that encoding all known invariants as types may be prohibitively cumbersome and time-consuming - to the point wher
53.
by turboponyy 2y ago
As with anything Haskell, one could simply reply with "here's the formal definition." But in easily digestible terms, it's a way to narrow your view over a collection to a subset that satisfies some property, and perhaps
54.
by turboponyy 2y ago
Agreed. For PR commits, appending the PR number (e.g. `#8`) to the short message is fine, but the short message should still contain a summary of changes. For issues, having something like "Fixed #8" in the commit message body is
55.
by turboponyy 2y ago
You realize that commits can be changed, right?
56.
by turboponyy 2y ago
Nix is completely orthogonal to whatever tech you use to build the resume - it's nice as a build tool + to provide dev environments for however you're going to realize your resume.
57.
by turboponyy 2y ago
Direnv and Nix are related in the sense that direnv has a `use flake` command that you can put in your .envrc to load the devShell defined in the project's flake.nix file. It's essentially just an automatic entry to the project&#x
58.
by turboponyy 2y ago
On the other hand, it's only an order of magnitude faster
59.
by turboponyy 2y ago
Why not integrate a Lua LSP instead of reimplementing all that language support?
60.
by turboponyy 2y ago
Emacs is whatever you want it to be, and it has wonderful modal editing packages such as evil-mode[1] - which surpasses the editing system from vi that it is based on - and Meow[2] 1. https://github.com/emacs-evil/evil

More ›