JS Kongress Munich #DeepTrack
Don’t wait to reserve your seat at JS Kongress – the event sells out every year.
Register your seat at JS Kongress 2020
Who is it for? What's the plan?
How to contribute
Unlike traditional conferences as it is on the main track, the schedule for the #DeepTrack is decided and created by the participants. Before the conference days, everybody is invited to introduce his session on our GitHub repository. For submitting your contribution open a new issue at the JS Kongress Github Repository. The idea is to give an introduction to your topic, tell the people about what they can expect and have a place for communication about the topic before, during and after the conference.
We strive for interactive sessions. Contributions where you want to discuss, where you want to work with others together, where you want feedback for are gladly seen. The final format is depending on the contributors wish and the number of participants to the individual proposals. This could be an unconference with a lot of participants or round tables and office hours with less participants. The topics from 2017 can be used for orientation:
- What's coming in TC39? We want your help!
- V8 startup snapshot
- Good, predictable performance
- Making sure that a new Chrome version does not break your website
Note: This is not a CFP, everybody from the community who owns a ticket has the opportunity to contribute to the Deep Slot.
On both days of the JS Kongress we have reserved the west part of the Alte Kongresshalle, the so-called flat construction. There we have different rooms with different capacities. Based on the number of interests and participants the format and rooms will be assigned.
For getting a common understanding about the topics “Unconference”, “Round Tables”, “Office hours” Unconference An unconference is a participant-driven meeting. The agenda is created by the attendees at the beginning of the meeting. Anyone who wants to initiate a discussion on a topic can claim a time and a space. Unconferences typically feature open discussions rather than having a single speaker at the front of the room giving a talk, although any format is permitted. The participants pitch their topic ideas and define the schedule based on their interests. A facilitator will guide through the whole process. Round Tables Round table is a form of academic discussion. Participants agree on a specific topic to discuss and debate. It’s common to define timeboxes for that. Each person is given equal right to participate, as illustrated by the idea of a circular layout referred to in the term round table. Office Hours At Office Hours you’ll find experts and speakers ready to chat, help you with projects and answer questions. This is a timeboxed format. E.g. 1h per speaker/expert.
Impressions - Recap of JSK 2017 and JSK 2019
For getting a better impression of the Deep Track, take a look on what happened on the first deep-track in 2017 and the second edition in 2019. Here's an overview about the Teams and the topics discussed in the deep-track:
- Google V8 Team: @v8js (Benedikt Meurer, Marja Hölttä, Michael Hablich, Mathias Bynens, ...)
- Google (Martin Splitt)
- webpack Core Team Members (Tobias Koppers and Johannes Ewald)
- TC39 (Daniel Ehrenberg)
- Mozilla (Lin Clark)
- Rust lang Core Team–former npm Inc, nodejs, mozilla (Ashley Williams)
- Microsoft (Brian Terlson)
- Google Dev Expert—Formerly W3C, MSFT. INFJ (Rachel Nabors)
- Founder of compose.us (Joern Bernhardt)
- Bloomberg (Lilit Darbinyan)
Topics discussed in 2019
Here are some topics which have been discussed on JS Kongress 2019:
- Plugins and extension systems
- TC39 -- AMA
- TC39 -- Immutable values, operator overloading, and custom numeric literals
- TC39 -- What's coming with classes?
- [v8 team proposal] AMA on V8 with @verwaest and @bmeurer
- Untangling crash stacks with pasta
Topics discussed in 2017
Here are some topics which have been discussed on JS Kongress 2017:
- Roll it up, shake it out: The future of Rollup.js
- [V8 Team Proposal] The future of WebAssembly: Discuss current threading proposal
- [V8 Team Proposal] The future of WebAssembly: Current thinking on integration with the DOM/JS
- [V8 team proposal] The future of WebAssembly
- [V8 team proposal] V8 startup snapshot
- [V8 team proposal] Good, predictable performance
- [V8 team proposal] Making sure that a new Chrome version does not break your website
- What's coming in TC39? We want your help!
- [webpack team proposal] WASM from developer-perspective
- [webpack team proposal] ESM in browsers vs bundlers
- [webpack team proposal] Webpack build time improvements
- [webpack team proposal] Is it a good idea to overload require()/import?
- WebVR corner
- [webpack team proposal] How to share non-JS stuff on NPM