You are browsing a read-only backup copy of Wikitech. The primary site can be found at

User:Pablo Grass (WMDE)/conferences/IJS2019 Munich

From Wikitech-static
Jump to navigation Jump to search

IJS2019 Munich was a JavaScript conference in October 2019, run in a venue shared with IPC2019 (PHP).

The conference was structured into two workshop days (Mon, Fri) and three days (Tue - Thu) of talks given in a single or two tracks. I attended Monday through Thursday.


The program had huge keynotes and more intimate sessions.

There was some overlap with the program of the co-hosted International PHP Conference which inspired openness for "front end" and "back end" aspects in discussions.

Topics reached from team culture and domain driven design to things more specific to the front end layer like type-safety around redux stores, design systems' place in the development workflow, and notorious convenient ways of setting up popular frameworks all the way to visions like offloading heavy-duty tasks to WebAssembly.


It was marketed as International JavaScript Conference and visitors and speakers alike seemed to originate from many European countries, some even as far as Australia. Talks were conducted in English. Promotion happened but was dimmed down to a comfortable level.

To me the variety of topics offered a great possibility to evaluate "where I (and my employer) stand" with regards to knowledge about and adoption of technology and methodology. This gave some reassurance (we are not too far off of where the majority are headed) but also acted as inspiration to further explore some of the interesting things mentioned (listed as "todo" in the notes and in the "takeaways").

Key takeaways

  • anyone who still recommends to start new JavaScript projects without TypeScript is just out of the loop and attention should be paid to them accordingly
  • 'redux-starter-kit' sets the bar high and vuex will have to catch up
  • storybook (or - in smaller numbers - its competitors) has become a part of "everyone's" tool chain
  • visual regression testing for the component library sounds incredibly useful and should be quite stable (as opposed to when done on apps). Integrate into CI and use resulting information to broadcast changes (to non-devs, too).
  • lighthouse (cf. fresnel) with a budget which is consciously adopted should be part of our workflow (CI)
  • navigator.onLine looks like a no-brainer to augment all kinds of save buttons
  • using service worker as API proxy is a nice vision to reality check in a contained project


In this Userspace:

User talk: