Tim van der Lippe

Development Tooling engineer @AdyenDevs.
@MockitoJava core developer. Former @ChromeDevTools, @Polymer. Completed Master Computer Science at TU Delft

[Tim van der Lippe @TimvdLippe]

Not sure how this works yet, but I think this is useful information for some: @[email protected]

[Tim van der Lippe @TimvdLippe]

Installed the Mastodon PWA (super polished) and will uninstall this PWA. See you on the other side!

[Tim van der Lippe @TimvdLippe]

Not sure how this works yet, but I think this is useful information for some: @[email protected]

[Chris Coyier @chriscoyier]

This is what HTML classes are now.

[Tim van der Lippe @TimvdLippe]

@sundress Yyyaaaayyy!!! Great match, so glad to hear you stay on the web. We are lucky to have you!

[Jake Bailey @andhaveaniceday]

After months of work (and years before me!), I've just sent the PR that converts TypeScript itself to modules. The compiler is 10-25% faster, the package is 43% smaller, and more. https://t.co/TYmT0apnSv

[Wes Bos @wesbos]

They are catching on

[Sam Saccone @samccone]

On Oct 25 around noon we saw a significant spike
in test failures running in our physical (phone) device labs.

Why did this happen .... Turns out even though our devices have wifi off and no sims there is still a vector of non-determinism...

[Jack Franklin @Jack_Franklin]

I find this interesting because the longer my career goes, the more I prefer simple and limited (not referring to React, just generally).

Context is everything in software so hard to define hard rules but I like simple because generally it means fewer footguns.

[Brad Frost @brad_frost]

✎ LET'S TALK ABOUT WEB COMPONENTS: https://t.co/RGTNHhJOMH

Web components are part of the web. They are good for the web. We should be rooting for them.

[Brad Frost @brad_frost]

Because web components are native to the web, they can travel to any web-based environment. They can be plugged into a WordPress/Drupal/Contentful/whatever site or integrated into a React/Vue/Angular/whatever app.

Of course reality is more complicated than that rosy picture.

[Tim van der Lippe @TimvdLippe]

A community member fixed it. After a couple of iterations, they came up with the simplest and most maintainable solution! Team work :D

https://t.co/JcT740FdUi

[Tim van der Lippe @TimvdLippe]

Currently, all PRs to @MockitoJava are blocked because of a Java 8 build issue. Are you looking to contribute to an open source project? I would be delighted to help you out. Some instructions and options are listed here: https://t.co/cxzMuceNwR

[Tim van der Lippe @TimvdLippe]

Private class fields are now even faster 🎉 And ESLint can also detect unused class fields: https://t.co/70OweYmZyF

[Joyee Cheung @JoyeeCheung]

I wrote a blog post about the optimization of new class features in @v8js that has also been included in the recent @nodejs 18.0.0 release 🎉 https://t.co/fc2FwFwq13

[Tim van der Lippe @TimvdLippe]

@alosii @MockitoJava It would be a breaking change for our users. We still support Java 8+

[Tim van der Lippe @TimvdLippe]

Currently, all PRs to @MockitoJava are blocked because of a Java 8 build issue. Are you looking to contribute to an open source project? I would be delighted to help you out. Some instructions and options are listed here: https://t.co/cxzMuceNwR

[Tim van der Lippe @TimvdLippe]

On my way to the @AdyenDevs Tech Event 2022! At 17:00 I will give my talk on "How to use mocks effectively in tests". Part of the event is publicly available as well via livestream: https://t.co/CoudRHopFt

[Tim van der Lippe @TimvdLippe]

The most important reason why we switched to web components in @ChromeDevTools

[Tim van der Lippe @TimvdLippe]

@brad_frost Web components are the only sustainable and non-risky way to crawl out of a framework and migrate to a new stack, one component at a time. Doesn't need to rewrite in one go or at all. Can also switch new development and let the rest sit to rest.

[Tim van der Lippe @TimvdLippe]

@brad_frost Web components are the only sustainable and non-risky way to crawl out of a framework and migrate to a new stack, one component at a time. Doesn't need to rewrite in one go or at all. Can also switch new development and let the rest sit to rest.

[Passle @passle_]

You should really look at your build output

[Tim van der Lippe @TimvdLippe]

@notessensei @MockitoJava We don't officially support it yet. If you have any issues, can you please open a ticket?

[Marvin Hagemeister ⚛️ @marvinhagemeist]

A recent tweet about running 1000 tests in 1s for @preactjs got a little attention. Here's a blog post diving into all the tricks and optimizations we applied to achieved that⚡️

https://t.co/8hO8gzzYfW