Live data from Hacker News

Viewing profile — eyelidlessness

eyelidlessness

HN member
Joined
Fri, Sep 12, 2008, 5:39 AM UTC
HN karma
12,249
Public activity
5,793 items

About eyelidlessness

https://eyelidlessness.github.io/

Recent public activity

  1. comment
    Comment #48749093

    I worked on a project a couple years back that would have benefited greatly from this approach. I look forward to giving it a spin when I have an opportunity. I’m curious how much …

  2. comment
    Comment #48748836

    I generally agree. But FWIW it does feel fairly idiomatic in terms of code written with Effect/API design in the Effect ecosystem. (Disclaimer: my Effect usage so far has been most…

  3. comment
    Comment #48664484

    Thanks! From what you say here and what I see in the docs, it looks like everything is much simpler and more robust than when I was exploring the space. I’m happy to see that, and …

  4. comment
    Comment #48662515

    I’m surprised to see this using a `--require` hook (rather than `--import`). Maybe something’s changed significantly since I was looking into building some similar functionality… b…

  5. comment
    Comment #48594228

    A trivial counter example to the intuition one might have that compilers likely produce deterministic output. It’s directly responsive to the exchange between Aoi and Numa above, w…

  6. comment
    Comment #48588717

    I’m not sure kindness is the best framing. At least, not in terms of being nice to any particular person who might commit unwanted files by mistake. It’s one of several tools a pro…

  7. comment
    Comment #48223227

    Well before the LLM explosion I would often preface my answers with some form of praise for the question. It depends a lot on audience of course, but it’s amazing how many people t…

  8. comment
    Comment #47426719

    I agree. And I think this also distills down to Rob Pike’s rule 5, or something quite like it. If your design prioritizes modeling the domain’s data, shaping algorithms around that…

  9. comment
    Comment #47413692

    It’s a muscle you can exercise, and doing so helps you learn what to focus on so it’ll be successful. IME a very successful approach is to focus on interfaces, especially at critic…

  10. comment
    Comment #46616961

    The point of a type system isn’t ever that you don’t have to check the things that make a value represent the type you intend to assign it. The point is to encode precisely the thi…

  11. comment
    Comment #46613044

    > But let’s dissect that last suggestion; suppose I do modify the type to encode that. Suddenly pretty much every field more or less just because Maybe/Optional. Once everything is…

  12. comment
    Comment #46580032

    It’s not a hack, but you may find more documentation for the equivalent preload values expressed as a tag. There is (near) parity between that and the HTTP Link header. The values …

  13. comment
    Comment #46237069

    Disclaimer: I’m a strong advocate for static typing. I absolutely see the connection. One of the advantages of static typing is that it makes a lot of refactoring trivial (or much …

  14. comment
    Comment #45989296

    It’s quite common, although I probably see it used more frequently to invoke other (non-shell) scripting languages.

  15. comment
    Comment #45968667

    You might want that, I might too. But it’s outside the constraints set by the post/author. They want to establish immutable semantics with unmodified TypeScript, which doesn’t have…

  16. comment
    Comment #45861520

    Marko’s compiler is designed for partial hydration (by default, without any special developer effort), which performs quite well. IIRC they were also looking at implementing “resum…

  17. comment
    Comment #45782526

    This is a fantastic way to put it, thank you for adding it!

  18. comment
    Comment #45782522

    I don’t agree with your characterization that anyone is “pretending”. The whole point of abstraction is convenience of reasoning. No one is fooling themselves or anyone else, nor t…

  19. comment
    Comment #45774704

    But there isn’t anything hilarious about that. It’s a clear-minded and deliberate approach to reconciling principle with pragmatic utility. We can debate whether it’s the best appr…

  20. comment
    Comment #45772941

    > Sometimes they even fail to even realise that it's what they are doing. Because that’s not what they’re doing. They’re isolating state in a systemic, predictable way.

  21. comment
    Comment #45765383

    To some extent you’ve answered this yourself: TypeScript (and/or linting) is the way to be warned about this. Aside from the points in sibling comment (also correct), adding these …

  22. comment
    Comment #45761007

    This is a matter of choice, not something with an objectively correct answer. Every possible answer has trade offs. I think consistency with the underlying standard defining NaN pr…

  23. comment
    Comment #45686130

    It’s not even safe if you’re 100% sure the types are compatible, unless you’re also 100% sure nothing will change that fact. The reason it’s unsafe is because it suppresses the typ…

  24. comment
    Comment #45519155

    Thank you for clarifying. (I think?) I think what confused me is the passive language: "everything gets converted" sounds (to me) like the runtime or some aspect of language semant…

  25. comment
    Comment #45518148

    Right, but I’m not clear on what gets converted to an array. Do you mean more or less what I said in my previous comment? That it requires you (your code, or calling code in genera…