Live data from Hacker News

Viewing profile — dcreager

dcreager

HN member
Joined
Mon, Mar 26, 2018, 2:15 PM UTC
HN karma
856
Public activity
118 items

About dcreager

[ my public key: https://keybase.io/dcreager; my proof: https://keybase.io/dcreager/sigs/qAdDFd-q6TDjesY0__JJ6GnOrnO0mRcDVpvmhC1958M ]

Recent public activity

  1. comment
    Comment #47445998

    Does that not also suggest (cautious, make sure we back it up with our actions) optimism about this acquisition? We're not breaking up the band. These tools will be in the same han…

  2. comment
    Comment #47441673

    The parser is not the hard part. The hard part is doing something useful with the parse trees. They even chose "oh is that all?" and a picture of a piece of cake as the teaser imag…

  3. comment
    Comment #47439974

    I've been in the industry for similarly long, and I understand and sympathize with this view. All I can say is that _right now_, we're committed to maintaining our open-source tool…

  4. comment
    Comment #47439091

    > I hope this means the Astral folks can keep doing what they are doing, because I absolutely love uv (ruff is pretty nice too). That is definitely the plan!

  5. comment
    Comment #47401943

    > My understand is Astral's focus for ty has been on making a good experience for common issues, whereas they plan for very high compliance but difficult or rare edge cases aren't …

  6. comment
    Comment #47400653

    Can you elaborate what you mean by decorative? If you run a type checker like ty or pyright they're not decorative — you'll get clear diagnostics for that particular example [1], a…

  7. comment
    Comment #47400564

    There have been some early proposals to add something like that, but none of them have made it very far yet. As you might imagine, it's a hard problem!

  8. story
  9. comment
    Comment #46327393

    There was a hang/performance bug [1, 2] that was reported just after the beta release, which we've since fixed [3]. You might try seeing if we get through your entire project now? …

  10. comment
    Comment #46302293

    Yes, we love TypeForm! We plan to support it as soon as the PEP for it lands. Under the covers, we already support much of what's needed, and use it for some of our special-cased f…

  11. comment
    Comment #46302208

    And the PEPs are now collated into a larger single typing spec [1], even hosted on a python.org subdomain. (Previously it was hosted on readthedocs) [1] https://typing.python.org/e…

  12. comment
    Comment #45645377

    Stepping away from Forth in particular, one of the benefits of a stack-based / concatenative language is that it's easy to implement on constrained hardware. uxn [1] is a great exa…

  13. comment
    Comment #44900526

    > competing with PyPI pyx doesn't compete with PyPI; it's a private registry that companies can use e.g. to host internal-only packages, or to provide curated views of things like …

  14. comment
    Comment #44810908

    The Open Firmware bootloader also used a Forth as its command-line interface. That was used on PowerPC Macs before Apple switched over to Intel. (So, you know, two processor archit…

  15. comment
    Comment #44169388

    That's okay, it's a fun thing to do!

  16. comment
    Comment #44130797

    I think that's a genuine error, since as you say, `None` is a possible value for `b` according to your signature. To handle this you would need to use "narrowing" to separately han…

  17. comment
    Comment #44116753

    Well ours is not yet implemented, so it's too early to say whether they're compatible. :-) But less snarkily, we do talk to them often (and the authors of other tools like mypy and…

  18. comment
    Comment #44110946

    The current plan is that they will remain separate tools, but will work together nicely if you are using both. For instance, we want to add type-aware and multi-file lints to ruff …

  19. story
  20. comment
    Comment #44110335

    It really helps in our mdtests, because then we can assert that not-implemented things are currently wrong but for the right reasons!

  21. comment
    Comment #44109716

    I don't know that I'd want the scripting language to be compiled, for reasons that are outside the scope of this reply. So removing that constraint, the coolest thing I've seen in …

  22. comment
    Comment #44109074

    ty is definitely not ready to be a pyright replacement yet. But it is usable as an LSP for simple things like go to definition, and deeper LSP features are on the roadmap for the e…

  23. comment
    Comment #44109043

    > I hope I didn't come off as angry or anything, I was just very surprised by the behaviour Not at all! :-) Just wanted to clarify for anyone else reading along

  24. comment
    Comment #44109024

    > Gradual typing means that an implicit "any" (unknown type) anywhere in your code base is not an error or even a warning. Even in critical code you thought was fully typed. Where …

  25. comment
    Comment #44108954

    [ty developer here] We are happy with the attention that ty is starting to receive, but it's important to call out that both ty and pyrefly are still incomplete! (OP mentions this,…