Live data from Hacker News

Viewing profile — samprotas

samprotas

HN member
Joined
Mon, Sep 18, 2017, 11:04 PM UTC
HN karma
60
Public activity
17 items

About samprotas

[ my public key: https://keybase.io/samprotas; my proof: https://keybase.io/samprotas/sigs/O9UlWsZ8efGwQw6D_rp30bzM_7RAYo1Nw5k1TCb8oTQ ]

Recent public activity

  1. comment
    Comment #30003865

    I’ve worked on systems in the past that had different levels of ip geolocation data precision. When the precision was low, they would pick the midpoint of the known area (maybe a w…

  2. comment
    Comment #26516660

    It’s also very directly related the to “effectively standard” (but not included) async library in Haskell. https://hackage.haskell.org/package/async The package description at the …

  3. comment
    Comment #26403027

    Zulip is another interesting point in the design space IMO. I think it’s worth a look for its take on the identified problem. https://zulip.com/

  4. comment
    Comment #25919452

    Having executed several "no-downtime" cutovers between systems via DNS updates, I will warn you that a surprising number of clients never re-resolve DNS, so the TTL is effectively …

  5. comment
    Comment #24863625

    Protobuf supports "oneof" which is also cumbersome to implement in these same languages but all of them support it (with some extra LOC and no exhaustiveness checking watching your…

  6. comment
    Comment #24862339

    I agree that having multiple different types of "object values" share one JSON key with no explicit "type" tag is asking for trouble with extensibility and conflicts. That said, I …

  7. comment
    Comment #24860464

    The number of comments here specifically upset with this part of the current design is a bit discouraging, but not necessarily surprising. Yes, many mainstream languages have near-…

  8. comment
    Comment #23044405

    A agree with this sentiment from my professional experience writing Go. This article has some nice specific examples of "Simple" APIs that push the complexity onto the programmer. …

  9. comment
    Comment #22192809

    I believe it’s a reference to the dot operator: . The parens around it are Haskell notation for using an operator in prefix position, which is often how operators are displayed in …

  10. comment
    Comment #21158648

    https://tech.channable.com/posts/2017-02-24-how-we-secretly-... FWIW they have this post from almost 3 years ago about adding Haskell to their stack. I'm guessing the time for your…

  11. comment
    Comment #20754395

    FWIW he is listed here https://www.postgresql.org/community/contributors/

  12. comment
    Comment #20560298

    This is a good point. So maybe my concern is more a verboseness issue rather than expressiveness. That said, it would be nice if there was some commentary on whether an implementat…

  13. comment
    Comment #20558475

    So I am a bit unclear on this from the proposal. Composing contracts is a slightly more verbose fix for allowing multiple contracts for a given type (just make a composed contract …

  14. comment
    Comment #20557731

    "Although functions may have multiple type parameters, they may only have a single contract." Anyone else find this limitation a bit disappointing? Seems like a somewhat arbitrary …

  15. comment
    Comment #18982232

    I find it kind of odd that there are all these comments claiming the article glosses over nuance and therefore its conclusion is baseless when the counterpoints have even less data…

  16. comment
    Comment #18677330

    This exact same thing happened at DuPont about 5 years ago. I believe there were roughly 80k employees at the time. There was essentially no real work email for most of the day unt…

  17. comment
    Comment #15810802

    For low utilization low cost continuous applications (think a web socket listener with not much to do) this lowers the entry level cost below a t2.nano it looks like. That’s a win …