@TimvdLippe

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

Joined January 2013
  • Tweets5.8K
  • Following135
  • Followers1.6K
268Media
Not sure how this works yet, but I think this is useful information for some: @tvanderlippe@fosstodon.org
2
1
2
Installed the Mastodon PWA (super polished) and will uninstall this PWA. See you on the other side!
Tim van der Lippe@TimvdLippe
15 Nov 2022
Not sure how this works yet, but I think this is useful information for some: @tvanderlippe@fosstodon.org
2
Tim van der Lippe retweeted
Chris Coyier
@chriscoyier
10 Nov 2022
This is what HTML classes are now.
68
102
27
1,200
Tim van der Lippe retweeted
Jake Bailey@andhaveaniceday
2 Nov 2022
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/TypeScr…

Convert the codebase to modules by jakebailey · Pull Request #51387 · microsoft/TypeScript

This is it; the PR that converts the TypeScript repo from namespaces to modules. TL;DR: The TypeScript compiler is now implemented internally with modules, not namespaces. The compiler is now 10-25...

github.com
30
210
42
1,946
Tim van der Lippe retweeted
Wes Bos
@wesbos
1 Nov 2022
They are catching on
37
145
57
1,745
Tim van der Lippe retweeted
Sam Saccone
@samccone
30 Oct 2022
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...
3
3
1
21
Tim van der Lippe retweeted
Jack Franklin@Jack_Franklin
30 Oct 2022
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
30 Oct 2022
Replying to @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.
2
1
10
Tim van der Lippe retweeted
Brad Frost@brad_frost
21 Oct 2022
✎ 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.

Let's talk about web components

I'm Brad Frost, an independent creator, web designer & developer, teacher, speaker, writer, musician, and artist based in Pittsburgh, PA.

bradfrost.com
11
67
14
279
Tim van der Lippe retweeted
Brad Frost@brad_frost
21 Oct 2022
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.
1
3
14
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/mockito/p…

Possible fix #2765: Add task to download package-list file from java as element-list by andrepasc...

I think these changes could a fix, or at least part of, for the issue #2765. Checklist Read the contributing guide PR should be motivated, i.e. what does it fix, why, and if relevant how If p...

github.com
Tim van der Lippe@TimvdLippe
15 Oct 2022
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/mockito/i…

JavaDoc warning is blocking all pull requests · Issue #2765 · mockito/mockito

Starting with #2758, our JavaDoc build has been erroring because of a change on Oracle's side. There's more information in #2759, but the gist of it is that Oracle removed the element-list ...

github.com
2
Private class fields are now even faster 🎉 And ESLint can also detect unused class fields: eslint.org/docs/latest/rules…

no-unused-private-class-members - ESLint - Pluggable JavaScript Linter

A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.

eslint.org
Joyee Cheung@JoyeeCheung
21 Apr 2022
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-class-fea…
1
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/mockito/i…

JavaDoc warning is blocking all pull requests · Issue #2765 · mockito/mockito

Starting with #2758, our JavaDoc build has been erroring because of a change on Oracle's side. There's more information in #2759, but the gist of it is that Oracle removed the element-list ...

github.com
1
3
1
11
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/nl/…
6
The most important reason why we switched to web components in @ChromeDevTools
Tim van der Lippe@TimvdLippe
11 Oct 2022
Replying to @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.
1
2
Tim van der Lippe retweeted
Passle@passle_
5 Oct 2022
You should really look at your build output
1
1
1
20
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-100…

Running 1000 tests in 1s

Most code doesn't require the amount of test isolation modern test runners apply by default. If you only opt into the amount of isolations you need, you can easily run 1000 tests in 1s.

marvinh.dev
Marvin Hagemeister ⚛️@marvinhagemeist
28 Sep 2022
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.
7
27
4
189
Tim van der Lippe retweeted
Cory LaViska
@claviska
29 Sep 2022
Gather 'round, it's story time. A number of years ago, I was hired by a company to rebuild a component library for their design system. The one they were replacing was built with AngularJS, but AngularJS was old and rickety and nobody wanted to use it anymore. 👇
17
54
7
193
Turns out, running a lot of tests in a real browser doesn't mean they are slow.
Marvin Hagemeister ⚛️@marvinhagemeist
28 Sep 2022
For the curious: This is what it looks like. There is no caching and no concurrency involved. Just a single process running all tests.
3
12
For yesterday's Mockito Javadoc issue: our build breaks with Java 8. However, since Mockito 4 still supports Java 8, we want to publish using that infrastructure. I guess we have to switch to Java 11 soon...
Tim van der Lippe@TimvdLippe
26 Sep 2022
Replying to @bcrow @BriceDutheil
Aha! So the culprit is the fact that we still support Java 8, hence we build our artifact on Java 8 as well. Thus the Javadoc command uses the "wrong" file. I am not sure if we can upgrade to Java 11 already. That would be a breaking change, solely for our Javadoc
1
The CI build of @MockitoJava is failing and it took me a while to understand why: we validate our JavaDoc generation (as we take great pride in writing meaningful documentation) and all warnings fail the build. We didn't change anything on our side, so it is an external change.
2
2
more replies
In the process, I spotted we linked to the Java 6 documentation (yeah, that's old) and attempted to update to Java 11: github.com/mockito/mockito/p… Sadly, it fails with the same problem, as the `element-list` page for Java 11 redirects to the index HTML page.

Update Javadoc deeps link to Java 11 by TimvdLippe · Pull Request #2759 · mockito/mockito

We currently use Java 6 to deeplink to the JDK and the URL no longer shows the necessary element-list, which is why it currently fails the build: https://github.com/mockito/mockito/actions/runs/310...

github.com
1
Does anybody know an alternative on how you can deeplink to the official JDK javadoc? It seems like we are following Oracle's guidelines, yet it fails. Is it maybe a recent regression on their end? Or a temporary glitch in their webserver?
1
1
Load more