Live data from Hacker News

Viewing profile — baggiponte

baggiponte

HN member
Joined
Thu, Aug 19, 2021, 6:31 PM UTC
HN karma
123
Public activity
101 items

About baggiponte

No profile information was provided.

Recent public activity

  1. comment
    Comment #45074794

    I’m afraid you missed a bit the mark :( This is the equivalent of LSP but for coding agents. So any editor does not have to rebuild an interface to support each and every new one.

  2. comment
    Comment #45074233

    Really hope for this to get traction so I’m not bound to the usual IDE

  3. comment
    Comment #44985927

    i think it's good to let them experiment! cargo (and go?) offers this already, so why not.

  4. comment
    Comment #44985912

    uv ruffy sounds funny

  5. comment
    Comment #44864403

    Wow I never realized how much mistral was “disconnected” from the ecosystem

  6. comment
    Comment #44856185

    How’s this different from xml?

  7. comment
    Comment #44846951

    Yeah. The docs tell you that you should build it yourself, but…

  8. comment
    Comment #44819667

    Litestar is really underrated but deserves much more usage! I’ve been meaning to try it for at least a year now, but always felt a bit scary to tell the team “hey let’s deviate fro…

  9. comment
    Comment #44307249

    Yeah they might be good but the marketing is really bold and, to a certain extent, arrogant if not outright disgusting.

  10. comment
    Comment #44109076

    BasedPyright is much better than pyright! Must use.

  11. comment
    Comment #44014574

    That’s not true, they have been developing it as red knot for a good while :)

  12. comment
    Comment #43901162

    You basically pay databricks a “fee” to choose the more appropriate and modern stack for you to build on, and keep it up to date. Never used it, but it handles with lots of the adm…

  13. comment
    Comment #43768011

    This looks so dope!

  14. comment
    Comment #43749700

    sqlalchemy doesn’t really accepts strings - if you do, you need to pass them into a “conn.execute(text(…))”, so end users should not face a breaking change.

  15. comment
    Comment #43749680

    Type checkers to the rescue ahaha I think db.get could also raise if the type does not match?

  16. comment
    Comment #42869290

    OpenAI coping so hard

  17. comment
    Comment #42868332

    he's coping so hard.

  18. comment
    Comment #42314900

    Oh you maintain PyTorch right?

  19. comment
    Comment #42191409

    Absolutely. No second thoughts.

  20. comment
    Comment #41995686

    also a whole bunch of new features (--script mode), speed of development, a stacked team.

  21. comment
    Comment #41995677

    Yes but only for linting (the flake8 rules etc). The end goal is to have proper type checking and, I think, proper LSP refactoring capabilities.

  22. comment
    Comment #41995666

    they are working on it! the internal name is currently red-knot (you can see it in their GH History and in the discord). First thing is a type checker, I think, then the renaming c…

  23. comment
    Comment #41584025

    Super interested. Do you have an equivalent of vLLM? Did you have to rewrite batching, paged attention…?

  24. comment
    Comment #41583939

    Uuuh can you tell a bit more about wasabi, the Python LSP? Saw a post years ago and been eager to see whether it’d be open sourced (or why it wouldn’t).

  25. comment
    Comment #41571151

    Have you seen two “prototypes” of standard for LLM telemetry? One is openllmetry, maintained by the folks at TraceLoop. Seems the more popular. The other one is openinference IIRC,…