Live data from Hacker News

Viewing profile — Flowdalic

Flowdalic

HN member
Joined
Mon, Feb 25, 2013, 4:59 PM UTC
HN karma
264
Public activity
57 items

About Flowdalic

No profile information was provided.

Recent public activity

  1. comment
    Comment #49121402

    You are not alone. Java remains unfairly tethered to a reputation forged over 20 years ago. Human psychology reveals a reluctance to update our worldview: once a collective consens…

  2. comment
    Comment #44732745

    > The standardization process comes into play when you think you have found a good solution, which should be adopted by THE standard respectively the ecosystem. Na, the standardiza…

  3. comment
    Comment #44731995

    I am not sure if I would phrase it that way. (Seemingly) conflicting extensions are another consequence of the loosely coupling between standardization and implementations. In addi…

  4. comment
    Comment #44731583

    > Personal speculation but I blame the "everything is an extension" model - it was meant to reduce fragmentation and allow clients with different featuresets to interoperate I coul…

  5. comment
    Comment #36498497

    The kernel usually just needs to know which binary to execute as init, which is often provided as kernel command line argument by the bootloader.

  6. comment
    Comment #34188534

    > Even if the application is making 50 byte sends why aren't these getting coalesced once the socket's buffer is full? Because maybe the 50 bytes are latency sensitive and need to …

  7. comment
    Comment #34180521

    The problem does not seem to be that TCP_NODELAY is on, but that the packets are sent carry only 50 bytes of payload. If you send a large file, then I would expect that you invoke …

  8. comment
    Comment #34115619

    It should be possible to install meson via pip --user. Even though I prefer system-wide installations, I believe this weakens your argument for user defined functions in your situa…

  9. comment
    Comment #32055047

    QUIC does a lot more than "the one for TCP". While I also believe that modern TCP consists of more than just one RFC (which you already hinted at). I guess the art in protocol desi…

  10. comment
    Comment #31500877

    Smack uses an XML pull parser and non-blocking I/O. It does so by splitting the XMPP stream top-level elements first and only feeding complete elements to the pull parser.

  11. comment
    Comment #31496891

    I get your confusion. But keep in mind that it is not only about just picking the library that shows as first result of your Google search. My naive self thinks that a million doll…

  12. comment
    Comment #31496753

    > One of the harder things with XMPP is that it is a badly-formed document up until the connection is closed. You need a SAX-style/event-based parser to handle it. That is a common…

  13. comment
    Comment #31493104

    It appears that Gloox, a relative low-level XMPP-client C library, rolled much of its Unicode and XML parsing itself, which made such vulnerabilities more likely. There maybe good …

  14. story
  15. comment
    Comment #31223933

    It is not an RFC, it is an I-D (Internet Draft).

  16. story
  17. comment
    Comment #29264165

    Using XML is one of XMPP its biggest strengths. XML is well designed, good documented and has a rich set of supporting libraries. XML documents can be composed of other XML documen…

  18. comment
    Comment #29264125

    I wonder why people jump fast to conclusion that to "let XMPP die", when the protocol can also be iteratively improved. Presence is not required in XMPP, its an optional feature. E…

  19. story
  20. comment
    Comment #24799256

    I wouldn't be sure that this is authentic, i.e. actually from John Nagle.

  21. comment
    Comment #22189936

    It still shows sign of ongoing development though: https://github.com/psi-im/psi/graphs/contributors?from=2016-...

  22. comment
    Comment #21945450

    1. Concurrency platforms finally help to utilize multiple cores of a system, as result we will see many-core architectures with plenty simple cores 2. The consequences of quantitat…

  23. comment
    Comment #21564103

    > Less standards, less use-cases - for example I don't think xmpp should take care of vcards, nickname and tons You mean you just want to use RFC 6120/6121? That's fine, just do it…

  24. comment
    Comment #21563291

    > I think it started to die when Google decided the XMPP spec was not good enough for them and deviated from it It was my impression that Google dropped XMPP support not because of…

  25. comment
    Comment #19112706

    Link to his stackoverflow answers sorted by votes: https://stackoverflow.com/users/254279/thomas-pornin?tab=ans...