固定されたツイート
Not sure how this works yet, but I think this is useful information for some: @tvanderlippe@fosstodon.org
English
Tim van der Lippe
5.8K posts
Tim van der Lippe
@TimvdLippe
Development Tooling engineer @AdyenDevs. @MockitoJava core developer. Former @ChromeDevTools, @Polymer. Completed Master Computer Science at TU Delft
参加日 Ocak 2013
136 フォロー中1.7K フォロワー
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: @tvanderlippe@fosstodon.org
English
Tim van der Lippe がリツイート
@sundress Yyyaaaayyy!!! Great match, so glad to hear you stay on the web. We are lucky to have you!
English
Tim van der Lippe がリツイート
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. github.com/microsoft/Type…
English
Tim van der Lippe がリツイート
Tim van der Lippe がリツイート
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...
English
Tim van der Lippe がリツイート
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.
Cory House@housecor
React 2014: Simple, but limited. React 2022: Powerful and remarkably flexible, but intimidating and fragmented. A massive number of compelling options to consider. The hardest part is keeping up with the churn and choosing between multiple compelling options.
English
Tim van der Lippe がリツイート
✎ LET'S TALK ABOUT WEB COMPONENTS: bradfrost.com/blog/post/lets…
Web components are part of the web. They are good for the web. We should be rooting for them.
English
Tim van der Lippe がリツイート
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.
English
A community member fixed it. After a couple of iterations, they came up with the simplest and most maintainable solution! Team work :D
github.com/mockito/mockit…
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: github.com/mockito/mockit…
English
Private class fields are now even faster 🎉 And ESLint can also detect unused class fields: eslint.org/docs/latest/ru…
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 🎉 v8.dev/blog/faster-cl…
English
@alosii @MockitoJava It would be a breaking change for our users. We still support Java 8+
English
@TimvdLippe @MockitoJava Do you know why moving to Java 11 is not the way?
English
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: github.com/mockito/mockit…
English
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: adyen.com/landing/events…
English
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.
English
@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.
English
Tell me your strong opinions about web components. Your enthusiasm. Your skepticism. Stencil vs Lit. SSR. Framework integration. Etc.
English
Tim van der Lippe がリツイート
@notessensei @MockitoJava We don't officially support it yet. If you have any issues, can you please open a ticket?
English
@MockitoJava Is Java19 already supported? Seems there are some Gremlins to fight?
English
Tim van der Lippe がリツイート
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⚡️
marvinh.dev/blog/running-1…
Marvin Hagemeister ⚛️@marvinhagemeist
Running all 1002 tests for @preactjs takes ~1s. This means new ideas can be tested instantly due to the short feedback loop. Makes it much more enjoyable to try out new ideas. Super glad that we invested early on into a fast test setup.
English