| Time | Room 1 | Room 2 | Room 3 | Room 4 |
|---|---|---|---|---|
| 11:30 | JavaScript Performance Tooling (Jaroslav & Benedikt) | Development workflow and rebasing (?) | ||
| 12:00 | Future of Rollup JS (Lukas) | Play with git (Carsten) | Solutions with RxJS (Adrian) | |
| 12:30 | Web Animations API + book signing (Rachel) | React Native case study (Adam) | What can Webpack learn form Rollup (Tobias) | |
| 13:00 | Lunch | |||
| 14:00 | TC39 Inclusion and feedback (Daniel) | WebGPU WASM integration (Nidin) | Living your style (Kathrin) | Brainstorming problems webpack values (Tobias) |
| 14:30 | JS operators ` | >and?.` (Daniel) |
Programmable Money (Florian) | Aspect oriented programming: JS (?) |
| 15:00 | V8 parses your JS up to 50% better (Marja) | GraphQL REST in peace? (Robert) |
Slides to Postillon presentation and how it was/is built.
Using Google Sheets as a database for posts?
Maybe Cloudflare Free plan with caching could be used without running in their limits?
Static site generators -> GitHub Pages which is probably not working out for that many page views.
Google App Engine?
Lukas is the new maintainer, Rollup should be used for bundling libraries.
Slides?
The discussion of this session seemed to continue a lot longer as I joined late. There were concerns whether it really is a good thing to pump out new features as they might incur a runtime overhead and whether TC39 looks into that during the stages.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent