Live data from Hacker News

Viewing profile — jstimpfle

jstimpfle

HN member
Joined
Thu, May 21, 2015, 7:34 PM UTC
HN karma
4,190
Public activity
3,515 items

About jstimpfle

http://jstimpfle.de

Recent public activity

  1. comment
    Comment #49190227

    Are you saying there is cache thrashing because callers often sercice rheid own requests themselves? If you don't want to service requests in the same thread, doesnt it mean you ha…

  2. comment
    Comment #49181831

    > I at least showed you cppreference so you can look up the data structures and their guarantees. Why do you show this to me??? Don't you think I know it? > But you did blame the S…

  3. comment
    Comment #49180749

    Actually, not half a dozen, more like hundreds if you count all the tiny ad-hoc stuff too (many of them similar or the same).

  4. comment
    Comment #49179723

    At this point, what isn't much of an estimation anymore is that you are here to explain things that nobody's asked for, and like to assume people around you have been waiting for y…

  5. comment
    Comment #49179085

    > I gave you great information "Great" is quite debatable. In any case, nothing I hadn't already known. > You aren't going to notice all your concurrency bugs without threads. True…

  6. comment
    Comment #49174963

    Serious question, are you an AI programmed to be annoying? > This isn't a problem with the standard library because a std::dequeue or any other core data structure doesn't make any…

  7. comment
    Comment #49170652

    You have repeatedly proven, and continue to do so, also by way of your exchanges with other commenters, that you're not asking out of curiosity. After all the previous comments we'…

  8. comment
    Comment #49165395

    Try harder, Sherlock. You're very close to proving that I assumed the STL was "thread safe". You've almost got me.

  9. comment
    Comment #49162048

    Why don't you read again what I said instead of continuing to make implications?

  10. comment
    Comment #49156707

    Where did I imply that I am expecting any part of the STL to be thread safe?

  11. comment
    Comment #49155357

    You are insufferable. Get lost.

  12. comment
    Comment #49055744

    Javascript

  13. comment
    Comment #49045177

    I've found that RAII and the stuff you have to buy into in order to use RAII come with more downsides than upsides once you scale beyond high level programs that try to get done a …

  14. comment
    Comment #49037521

    I understand C++ as well, or better, than most (or all) of my peers, and certainly betters than people on here thinking they need to explain to me how RAII works. Do you want to ar…

  15. comment
    Comment #49035061

    You don't understand even the first things of what I say. That's because you apply beginner level concepts and understand to argue, and are not looking for nuance or deeper underst…

  16. comment
    Comment #49035012

    You don't get it. That's because you still don't understand some basic things about the language. There is no method call here on a pointer expression. There is only a call on a va…

  17. comment
  18. comment
    Comment #49034970

    Well, the best way to prevent mistakes is to make everything super complicated and damn hard to do. The best way to prevent mistakes is to approach it to do the essential stuff and…

  19. comment
    Comment #49034508

    How about you do the following two Google (or AI) searches "Please give me examples of great systems software written in plain C or C style procedural C++" "Please give me examples…

  20. comment
    Comment #49034260

    > I don't think you did, I think you just said it has downsides over and over. Show evidence of your claim. > Don't ask for basic knowledge then get upset when you get it. Where di…

  21. comment
    Comment #49033273

    Pretty much all the C++ features I've used are good enough to write some toy code snippet, but it's hard to use them to good effect at scale without causing massive problems. Even …

  22. comment
    Comment #49033234

    Well that's a lie. I've long been back to raw pointers and it's by far the easiest way to do it. All of Pimpl, unique_ptr, and whatever other clever mechanism (I'm not even looking…

  23. comment
    Comment #49033065

    > It's your claim that destructors are harmful so the burden of proof is on you. I have given a variety of arguments why I think the C++ RAII specifically has downsides. You can ac…

  24. comment
    Comment #49016927

    You keep "asking" for evidence but the only evidence presented by yourself is that you have merely surface-level understanding of the subject matter, and are looking for arguments,…

  25. comment
    Comment #48979653

    I asked you what's wrong with pool destructor function pointers. You gave a reason what's wrong and I refuted it. So no, I'm not saying that storing a function pointer is special, …