Live data from Hacker News

Viewing profile — tatterdemalion

tatterdemalion

HN member
Joined
Thu, Jul 31, 2014, 10:00 PM UTC
HN karma
2,029
Public activity
418 items

About tatterdemalion

https://github.com/withoutboats

Recent public activity

  1. comment
    Comment #17242652

    The same code with `await` :) let (reader, vec) = await { io.read_until(reader, b'\n', Vec::new() }?; if vec.len() == 0 { return Err(Error::new(ErrorKind::BrokenPipe, "broken pipe"…

  2. comment
    Comment #17241674

    The user specifically asked about stackfull coroutines, which is not the direction we're going. But I think the pain point the user talked about (futures right now are difficult to…

  3. comment
    Comment #16570939

    The RFC supports it, eddyb's list of milestones in the compiler just don't get you all the way there.

  4. comment
    Comment #16433041

    Signal's use of SGX was to increase users' trust in Signal - OpenWhisperSystems couldn't log your contacts even if they wanted to. Its up to potential users to decide if they think…

  5. comment
    Comment #16227574

    My apologies if I misunderstood you - I read your comment as suggesting that safe abstractions are "leaky" and therefore create additional responsibilities for users to validate th…

  6. comment
    Comment #16227546

    Proving the correctness of unsafe code is totally different from what you talked about, which was composing different abstractions with unsafe internals together. Users of safe Rus…

  7. comment
    Comment #16227510

    There is a conflation happening here. What is the nature of this bug when you compose these two libraries together? If it is a violation of Rust's safety guarantees, then at least …

  8. comment
    Comment #16227043

    Its possible that I misread the comment; it seemed to state that this problem extended into safe Rust, which it definitely does not.

  9. comment
    Comment #16226861

    > The major difficulty here is that in general, unsafe pieces of code cannot be safely composed, even if the unsafe pieces of code are individually safe. This allows you to bypass …

  10. comment
    Comment #16202305

    Rust is consciously designed for large code bases. shrug

  11. comment
    Comment #16202285

    - We are directing material resources (as in, hours of paid work) to improving compiler performance. We consider this a serious problem, and "the compiler performance is always imp…

  12. comment
    Comment #16202269

    What we could do better than we do today - and your comment about ergonomics alludes to our work to improve this - is ease the onboarding of that complexity we have to be "honest" …

  13. comment
    Comment #16202253

    This is not my experience using Rust. I had six months of programming experience when I first tried Rust. I definitely got confusing errors at first, but I grasped the system withi…

  14. comment
    Comment #16202243

    Do you stay away from all type systems? This would be an accurate negative framing for any type system, which all necessarily reject some correct programs.

  15. comment
    Comment #15973317

    I understood your point. As my comment alluded to, the criticisms of tokio this blog post is attempting to address have to do with the implementation complexity - abstractions do n…

  16. comment
    Comment #15973092

    There's another reason Rust's ecosystem uses futures (as opposed to having some library-based greenthreading system): each future is like the stack of a userspace thread, but perfe…

  17. comment
    Comment #15973045

    What's missing here is that Go has a userspace scheduler and greenthreads. Despite presenting the user with something that looks like old school blocking IO, because you are only b…

  18. comment
    Comment #15973028

    There are various criticisms of tokio, coming from different directions. Some have to do with the fact that some abstractions in the futures ecosystem are leaky today and that make…

  19. comment
    Comment #15933569

    I think this was a very bad move, because Mozilla installed adware in all of its browsers. The fact that it was installed through an add on, though, seems irrelevant. Mozilla devel…

  20. comment
  21. comment
    Comment #15720960

    Or Rust. ;-)

  22. comment
    Comment #15425301

    Similarly, this automobile is well built despite having every design decision be wrong. There's some distinction between the architecture and the craftmanship - a poorly crafted an…

  23. comment
  24. comment
    Comment #15325662

    Upthread there are quotes from other physicists chiding Slotin because what he was doing was extremely dangerous. It was known at the time.

  25. comment
    Comment #15316121

    The PARTNER study studied 767 serodiscordant couples, with the HIV positive partner undetectable. All participating couples did not use condoms at least some of the time. They foun…