Tweetovi

Blokirali ste korisnika/cu @kleshney

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @kleshney

  1. 2. velj

    All programming abstractions that we invented are crutches for our monkey brains

    Poništi
  2. proslijedio/la je Tweet
    23. sij

    What idiot called it “when the tech bubble bursts” and not “when shit hits the FAANG”?

    Poništi
  3. 19. sij
    Poništi
  4. proslijedio/la je Tweet
    17. sij

    who called it writing a macro instead of intermittent ast-ing

    Poništi
  5. proslijedio/la je Tweet
    2. sij
    The drake meme where drake is disgusted by option one but likes option 2. The right side is blank
    Poništi
  6. proslijedio/la je Tweet

    1. The payoff for anything more complex than sum types, parametric polymorphism and basic dispatch (type classes, ML modules, whatever) is low. 2. Decent SQL is more important than language choice most of the time anyway.

    Poništi
  7. 30. stu 2019.
    Poništi
  8. 20. stu 2019.
    Poništi
  9. 19. stu 2019.

    Great article about thread pool implementations and lock-free code (code examples are in rust but it is applicable for other langs as well)

    Poništi
  10. 16. stu 2019.
    Poništi
  11. 26. lis 2019.

    It took me 117 turns to reach room 8 in normal mode, but then I starved exhausted.

    Poništi
  12. 25. lis 2019.

    K3sup looks interesting. I'm gonna try it for my home cluster:

    Poništi
  13. 24. lis 2019.

    Lost 2 hours of my life fighting with Rust module system. Frustrated to the max. Can't imagine which trade-offs led to current design.

    Poništi
  14. 2. lis 2019.
    Poništi
  15. 24. ruj 2019.
    Prikaži ovu nit
    Poništi
  16. 24. ruj 2019.

    * the only way to get accurate info is to parse gc logs * You may want to run your IDE with Shenandoah to reduce memory footprint (esp.when you are not using it) * Newer JDK contains TONS of improvement. If low latency is important you must upgrade

    Prikaži ovu nit
    Poništi
  17. 24. ruj 2019.

    * atomics, VarHandle, j.u.concurrent.* help to avoid gc overhead * what JVM reports as gc pauses is not the full duration of a pause, use -Xlog:safepoint * String.intern() is dangerous, roll your own string cache/dedup if you need it * You can control safepoint frequency

    Prikaži ovu nit
    Poništi
  18. 24. ruj 2019.

    Random notes: * lots of threads leads to long gc pauses (still!) * deep call stacks -> long pauses * typically threads from thread pool are parked with very shallow stacks (which is great) * Many locks with contention -> longer gc pauses

    Prikaži ovu nit
    Poništi
  19. 24. ruj 2019.

    Shenandoah GC Part II by

    Prikaži ovu nit
    Poništi
  20. 11. ruj 2019.
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·