Robin Marx

@programmingart

Developer with particular interests in Games, Networking, Performance and Security. Currently working on a PhD in Webperf/HTTP3/QUIC

Hasselt, Belgium
Vrijeme pridruživanja: lipanj 2009.

Tweetovi

Blokirali ste korisnika/cu @programmingart

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

  1. Prikvačeni tweet
    13. lip 2018.

    The video of my ": In theory and practice" talk is now online: . I discussed the problems QUIC is trying to solve and how it aims to do that, as well as why The Flash is superior to Superman.

    Prikaži ovu nit
    Poništi
  2. proslijedio/la je Tweet
    prije 3 sata

    Thanks everyone who joined us at the devroom on Feb 1st, it was a blast! For those who want to catch up, all the videos are available here: Thanks again to our awesome speakers 🎤

    , , i još njih 3
    Poništi
  3. 2. velj

    The video for my talk on and resource prioritization is already online at ! In it, I explore why broccoli tastes bad and why you should eat your fries last. And also a little bit about .

    Poništi
  4. 31. sij

    All ready for my tasty talk on HTTP/2 and HTTP/3 prioritization tomorrow. Follow the whole web performance track live at , starts at 3PM Brussels time, my talk is at 5PM. Sneak preview:

    Poništi
  5. 29. sij

    Are there any (HTTP Archive) stats about actual usage of >>>Progressive<<< JPEGs on crawled pages in the wild? Can't seem to find them in Web Alamanac or forums...

    Poništi
  6. 28. sij

    I'm doing a presentation on HTTP/2 and HTTP/3 resource prioritization on Saturday and I'm having some trouble fixing the scope of the talk... Please tell me what aspects you think I should definitely include. Talk will be on YouTube, so worth your effort ;)

    Poništi
  7. proslijedio/la je Tweet
    27. sij

    The QUIC working group suggests updating the charter to (among other things) remove the milestones that say the group should've been done in July 2019. (The proposed update has no dates at all.)

    Poništi
  8. proslijedio/la je Tweet
    25. sij

    I've just released a blog post that I started way back last year and that got longer and longer and longer. Initially I wanted to release it on January 15th, but I missed the mark. Solution: I backdated it! :) Here it is: Today, the Trident Era Ends

    Poništi
  9. proslijedio/la je Tweet
    24. sij

    Come on February 11th to hear me talk about a brief history of HTTP/3, how it compares to HTTP/2, and some practical advice to help get you started testing, debugging and web performin'

    Poništi
  10. proslijedio/la je Tweet
    22. sij

    Holy smokes! comes flying into the ring with Puppeteer-on-12-cups-of-coffee — Playwright does native browser automation on Chromium, WebKit, and Firefox. 🤯🤯

    Poništi
  11. proslijedio/la je Tweet
    22. sij

    Been using Firefox's profiler quite a bit lately. The FlameGraph (or chart as I described it to someone the other night) aggregates the output from the profiler and really helped get to the bottom of a client issue really quickly

    Prikaži ovu nit
    Poništi
  12. proslijedio/la je Tweet
    20. sij

    I have written up my experiences on getting to run on embedded boards: Towards Securing the Internet of Things with QUIC. Lars Eggert. Proc. NDSS Workshop on Decentralized IoT Systems and Security (DISS), San Diego, CA, USA, February 23, 2020.

    Poništi
  13. proslijedio/la je Tweet
    22. sij
    Poništi
  14. proslijedio/la je Tweet
    22. sij

    Proposal for a new metric: The Moon Unit, or "moo", which is equal to 2.71321035034 seconds, the maximum ping time to the moon. It's a measure for web technologies, like Google Drive, which regularly takes around 4.5moo to list the first 50 files in a directory.

    Prikaži ovu nit
    Poništi
  15. proslijedio/la je Tweet
    20. sij

    HTTP/2 priorities are complicated, used very differently by servers and clients alike 🤷‍♂️ And now HTTP/3 is trying to fix this 💪 Hear all about HTTP priorities with in an in-depth tour on Feb 1st in Brussels at the web perf devroom:

    Poništi
  16. proslijedio/la je Tweet
    17. sij

    Educational slide. Run bleeding edge h3 with a browser! (those are the canary + nightly logos)

    Poništi
  17. proslijedio/la je Tweet
    16. sij

    Cows make milk. They milk themselves. Other cows check the milk (for free). Cows - get this - PAY THE FARMER to take the milk away. Then the farmer (you won't believe this, honestly) sells the milk *back to the cows.*

    Prikaži ovu nit
    Poništi
  18. proslijedio/la je Tweet
    16. sij

    This is going to have some interesting consequences if/when all of the bits ship. Particularly the separate socket pools and TLS resumption per context. Preconnecting for frame-loaded resources or cross-domain page navigations may stop being useful (much more than just caches).

    Poništi
  19. proslijedio/la je Tweet
    16. sij

    Rant time... I *really* like the QUIC protocol. Yes, it's complex but overall it's really nice to work with. HTTP/3 is a completely different matter. Question: How many QUIC streams are required to exchange a *single* HTTP/3 request and response? The answer may surprise you...

    Prikaži ovu nit
    Poništi
  20. proslijedio/la je Tweet
    15. sij

    Super happy to have been appointed as 3rd chair of the IETF QUIC Working Group today. I've worked with various shapes of QUIC since 2015. Seeing it progress in the IETF, from the BoF(s) to Internet-scale running code, has been amazing. I'm excited to see what the future holds.

    Poništi
  21. proslijedio/la je Tweet
    15. sij

    The majority of endpoint compromises involve web browsers — by putting space between users’ devices and where web code executes, browser isolation makes endpoints substantially more secure.

    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:

    ·