Tim van der Lippe

@TimvdLippe

Software engineer . Former team intern. core developer. Completed Master Computer Science at TU Delft

Joined January 2013

Tweets

You blocked @TimvdLippe

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @TimvdLippe

  1. Pinned Tweet
    5 Apr 2018

    With a little delay, the video of my presentation "When to use webcomponents" at the conference has now been published on Youtube!

    Undo
  2. Retweeted
    Jan 30

    TIL CSS can check for a font installed locally before fetching it remotely! Shout out to Dank Mono, my favorite ligature featured coding font

    @font-face {
  font-family: Dank Mono;
  src: 
    /* Full name */
    local(Dank Mono),
    /* Postscript name */
    local(Dank-Mono), 
    /* otherwise, download it */
    url(//...a.server/fonts/DankMono.woff);  
}

code {
  font-family: Dank Mono, system-ui-monospace;
}
    Show this thread
    Undo
  3. Retweeted

    This is some of the lovely syntax you can ship to 90% of browsers using <script type="module>. (transpile for the other 10% and drop in <script nomodule>)

    Undo
  4. Retweeted
    Jan 30

    Unpopular opinion: React is the wrong tool for building content websites (blogs, marketing sites, documentation, etc.) today. SSR is not good enough. You end up downloading the content twice: once in the HTML, and again in the JS for hydration. How did this become so common? 😱

    Show this thread
    Undo
  5. Retweeted

    Puppeteer v2.1.0 is out! 🔥 ➡️ Chromium 80 ➡️ puppeteer.launch({product: 'firefox'}) Puppeteer can now talk to a real, unpatched Firefox binary. You no longer need to install puppeteer-firefox separately!

    `puppeteer.launch` now accepts a `product` option which can be set to `'firefox'`.
    Undo
  6. Retweeted
    Jan 25

    It is really hard to sell programmers on doing less stuff. It's like we're trained to seek solutions instead of negating the conditions of our problems.

    Undo
  7. Retweeted

    Incredible overview of non-standard web platform features that debuted in Trident, the engine behind good ol’ Internet Explorer: by

    Undo
  8. Jan 23

    We are migrating to and found some blockers. Very pleased to see quick resolution and fixes in the TypeScript compiler, making future JS -> TS easier! Hopefully we can provide guidance when we are finished, for others who want to do the same.

    Undo
  9. Jan 21

    To clarify: It's the Tuesday before, not after, they originally estimated the package would arrive.

    Show this thread
    Undo
  10. Jan 21

    Amazon: You can pay 5 pounds extra and we deliver it on Wednesday. Me: Nah, I am good. I am not in a hurry. Amazon: Okay no problem. You will receive your package on Thursday. I received the package today. On Tuesday.

    Show this thread
    Undo
  11. Retweeted
    Jan 19

    ⏲️ As of today, we have about eighteen years to go until the Y2038 problem occurs. But the Y2038 problem will be giving us headaches long, long before 2038 arrives. I'd like to tell you a story about this.

    Show this thread
    Undo
  12. Jan 19

    "Your code doesn't have to be perfect, and it won't, it just has to be good enough to solve your current problem properly."

    Undo
  13. Retweeted

    ICYMI, Chrome has changed course from earlier this week and will not freeze the major version number in the UA, such that detecting Brand and Major Version will still work while still improving security! Thanks for taking the feedback and finding a good compromise!

    Undo
  14. Jan 16

    We are doing some refactoring work on and this sounds like a great feature to integrate in our workflow!

    Undo
  15. Retweeted
    Jan 15
    Undo
  16. Jan 15

    Note that I have nothing against JSDom and I am not claiming it is lacking features. However, we would like to run our tests in the environment the actual production code runs in. By only running in JSDom, we would miss subtle differences between different browser implementations

    Show this thread
    Undo
  17. Jan 15

    Does anyone have experience with modifying Jest to run in a browser instead, similar to how Karma works?

    Show this thread
    Undo
  18. Jan 15

    Time and time I would like to use Jest as our testing framework, only to realize we can't use it as it does not run tests in actual browsers: We can't not run our tests in actual browsers, due to the subtle differences between JSDom and the browser.

    Show this thread
    Undo
  19. Jan 15

    "To call the Python 3 transition disruptive and distracting for the project would be an understatement. As a project maintainer, it's natural to ask what we could have accomplished if we weren't forced to carry out this sideshow."

    Undo
  20. Retweeted
    Jan 14

    I've sent out a couple of intents that outline a plan to provide an alternative to the User-Agent string and then slowly kill it. Let me know if you have Opinions™

    Undo
  21. Retweeted

    This could not be more stark... Compare These 20 Headlines To See How Differently Royal Reporters Treated Kate Middleton And Meghan Markle via

    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·