This repository collects all session proposals for the #DeepTrack at JS Kongress Munich. See you again in 2021! Take a look on our website for more details.
Home Page: https://js-kongress.com
Session Title:
WebVR corner
Session Abstract:
Let's talk all things WebVR!
Wanna see how to get started? Have a problem with a project of yours? Let's do it!
Approximate Duration:
60 minutes
Your Name:*
Martin Splitt
Your Twitter handle:*
g33konaut
Requirements:
[ ] No
[x] Yes => A power socket and table would be helpful
Complexity:
[ ] Advanced
[ ] Intermediate
[x] Beginner
Other information:
WebVR is exciting yet intimidating to many. I want to host this session to help people get started and discuss their ideas, projects or problems with WebVR.
Hopefully this session will help get more people to build things with this wonderful new technology!
Session Title: Ask Me Anything
Session Abstract: Open-ended Q/A with people from TC39, including Dan
Approximate Duration: 60
Your Name:* Daniel Ehrenberg
Your Twitter handle:* littledan
Requirements:
[x] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Advanced
[ ] Intermediate
[x] Beginner
Other information:
Session Title:
Making sure that a new Chrome version does not break your website
Session Abstract:
This session describes on how to test your web application in advance in order to find out if future Chrome releases might "break" your web application. The earlier you discover problems, the higher the chance for Chrome and/or you to fix them without impacting your revenue stream.
Approximate Duration:
15–30 minutes
Your Name:
V8 team
Your Twitter handle:
v8js
Requirements:
[x] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Advanced
[ ] Intermediate
[x] Beginner
Session Title:
Session Abstract:
The trickiest part of learning ReactiveX is switching your mindset to reactive. With so many operators out there learning Rx on your own is often overwhelming. And no, marbles don't actually help.
But we are living in a reactive world and we can find examples everywhere around us.
In this talk, we will break down the ReactiveX to the basic ingredients and equip you with the approach that will make learning even the hardest operator a child's play.
Writing a reactive code, after all, is no more than telling a story.
Approximate Duration:
30-40 minutes, depending on the available slot
Your Name: Miroslav Jonas
Your Twitter handle: meeroslav
Requirements:
[X] No
[ ] Yes
Complexity:
[X] Advanced
[X] Intermediate
[X] Beginner
Other information:
The talk describes the common obstacles in learning RxJS and why the documentation is too technical for most of the people. By using metaphors from the world of cooking (or rather eating), it explains the complex concepts in a way everyone can understand. The purpose is to show the audience how complex topics can be made simple by avoiding the expensive buzzwords and using common language and objects that surround us.
Some more insights are available via blog post Cooking with RX or via talk at a local meetup Reactive Vuejs.
Target audience: beginners to experts in RxJS
Session Title:
JavaScript & SEO - opening up a black box
Session Abstract:
Is SEO a mystery to you? Do you fear that your JS web app isn't going to be findable via Google Search? Did our developer docs confuse you or weren't helpful? Join the session and talk to me!
I'm on the developer relations team for Google Search and I'm here to help you and learn from you, too! 😄
Approximate Duration:
30 minutes
Your Name:Martin Splitt
Your Twitter handle:g33konaut
Requirements:
[x] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Advanced
[ ] Intermediate
[x] Beginner
Other information:
I would like to give everyone an opportunity to talk about their challenges when working with SEOs or getting their web content indexed when JavaScript is involved. I would love to bust some myths and find out where I can help as part of the DevRel team for Google Search. Missing docs? Confused by something? Missing a tool to test or debug your code for search? Join the session and let me know!
This is probably going to be a mix of Q&A and brainstorming.
Session Title:
Is it a good idea to overload require()/import?
Session Abstract:
Webpack allows to overload the require() or import mechanism in order to load different file types. For instance, in webpack applications it is quite common to require() an image or a CSS file. The result of the import statement is determined by an external configuration (in webpack land by loaders). For instance, CSS files are translated into an object of CSS class names which makes it easier and safer to reference class names from JavaScript. Images are usually translated to a string that represents a URL. This can be useful if the application wants to leverage HTTP long-term caching via hashed filenames.
There has been a long discussion with members from the browserify community whether this is a good idea or not (webpack/webpack#378). The biggest argument against it is that this feature is currently proprietary to webpack and that there is no standard for configuration and consumption. With the upcoming WHATWG loader specification, however, things might change.
Approximate Duration:
30 minutes
Your Name:
Johannes Ewald
Your Twitter handle:
jhnnns
Requirements:
[x] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Advanced
[x] Intermediate
[ ] Beginner
Session Title: From an Angular app to an Universal app
Session Abstract:
Isomorphic apps are the best solution for SEO if you have an SPA web app. The isomorphic solution for Angular is Angular Universal. How ever, What happen if I already have an Angular app? How can I migrate an Angular app to an Universal app? What kind of thing I have to consider to do it?
In this session I'm going to answer all these questions
Approximate Duration:
60 min
Your Name: Adrian Ferreres Esteller
Your Twitter handle:* ardiadrianadri
Requirements:
[X ] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Advanced
[ X] Intermediate
[ ] Beginner
Other information:
It would be necessary a minimum knowledge of Angular to follow this talk
Session Title:
The future of WebAssembly
Session Abstract:
Discuss current threading proposal:
Current thinking on integration with the DOM/JS:
Approximate Duration:
30 minutes
Your Name:
Ben Titzer
Your Twitter handle:
v8js
Requirements:
[x] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Advanced
[x] Intermediate
[x] Beginner
Session Title:
JavaScript WeakRefs
Session Abstract:
WeakRefs are an upcoming language feature (Stage 2 at the moment); I'll explain how weak references work and demo the feature in Google Chrome.
Spec draft: https://weakrefs.netlify.com/
Approximate Duration:
30 min
Your Name:*
Marja Hölttä
Your Twitter handle:*
marjakh
Requirements:
[ ] No
[X] Yes => Please share what do you need.
Projector + adapter for connecting my laptop: Debian Linux, HDMI.
(Last year it was only possible to use the projector if you were at the back of the room; that doesn't work well!)
Complexity:
[X] Advanced
[X] Intermediate
[ ] Beginner
Other information:
This session might not happen if I can't make it to the conference (there's no backup).
Session Title:
WASM from developer-perspective: How make using WASM developer-friendly?
Session Abstract:
Approximate Duration:
30 minutes
Your Name:
Tobias Koppers
Your Twitter handle:
wSokra
Requirements:
[x] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Advanced
[ ] Intermediate
[x] Beginner
Other information:
Motivation: Figure out what's needed to make WASM more approachable.
Session Title:
Web Components - harmony and connection in the JS world
Session Abstract:
In this session, we will not just look at the theory behind Web Components but work through a set of Step By Step examples to build reuseable Web Components that have functionality like forms, data retrieval and communciation with pages and other Web Components.
Approximate Duration:
90 mminutes
Your Name:*
Craig West
Your Twitter handle:*
Requirements:
Complexity:
[ X] Intermediate
Other information:
Web Components enable not just reuseable code formation but also inter-operability between all the different frameworks. They enable larger apps to be split into micro-apps or micro-services.
Web Components & Micro Apps: Angular, React & Vue peacefully united? https://www.youtube.com/watch?v=1KJQurclLdw was the keynote session at iJS London 2018.
Session Title:
Webpack build time improvements
Session Abstract:
Building large web applications with webpack can be cumbersome because of long build times. We (the webpack team) have heard of build times between 2-3 minutes or even more. Airbnb, for instance, is struggling with a build time of about 3 minutes (webpack/webpack#5718). During this session, we can talk about the current bottlenecks and how it can improved.
Approximate Duration:
60 minutes
Your Name:
Johannes Ewald
Your Twitter handle:
jhnnns
Requirements:
[ ] No
[x] Yes => I think it would be helpful to inspect a flame graph of a webpack build to show/demonstrate the bottlenecks. So we would need a projector with HDMI jack.
Complexity:
[x] Advanced
[ ] Intermediate
[ ] Beginner
Other information:
Maybe more flame graphs from different projects?
Session Title:
ESM in browsers vs bundlers
Session Abstract:
Approximate Duration:
30 minutes
Your Name:
Tobias Koppers
Your Twitter handle:
wSokra
Requirements:
[x] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Advanced
[x] Intermediate
[ ] Beginner
Other information:
Session Title:
What's happening with Puppeteer?
Session Abstract:
An overview of what's been cooking in Puppeteer, the Node.js library for automated browser testing. We'll go over recent changes in Chromium/Blink and how they affect Puppeteer, and will walk you through how new features are implemented in the Chrome DevTools Protocol (CDP) and later in Puppeteer.
Approximate Duration:
30 min
Your Name: Mathias Bynens
Your Twitter handle:
mathias
Requirements:
[ ] No
[x] Yes: a way to present/cast to a screen
Complexity:
[ ] Advanced
[x] Intermediate
[x] Beginner
Other information:
Learn how Puppeteer works behind the scenes (beyond the JavaScript layer)
Session Title:
Chrome DevTools Office Hours
Session Abstract:
The Chrome DevTools Team offers to run office hours during the JSKongress, where interested folks can drop by, ask questions about Chrome DevTools, or chat about their favorite feature or worst pain point. We're interested to not only present what's going on in DevTools and what's coming next, but also to hear your feedback and learning from you how we can make DevTools even better.
Those of you who had been to Chrome DevSummit 2019 might remember the developer lounge, where we also ran a booth where you could drop by and chat about Chrome DevTools (and other Chrome related developer projects).
Approximate Duration:
Probably around 3-4 hours each day.
Your Name:
Chrome DevTools Team (@bmeurer, @natorion, @hashseed)
Your Twitter handle:
@ChromeDevTools
Requirements:
[ ] No
[x] Yes, a dedicated room (as discussed with @johannes-weber), power plugs, stable WiFi, and a preferably a screen we can use to run a slide show.
Complexity:
[x] Advanced
[x] Intermediate
[x] Beginner
Session Title:
Good, predictable performance
Session Abstract:
Approximate Duration:
30–45 minutes
Your Name:
V8 team
Your Twitter handle:
v8js
Requirements:
[x] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Advanced
[x] Intermediate
[x] Beginner
What's coming with classes?
We will discuss various class features that are at various stages of standardization in TC39, from early proposals and things shipping in browsers. This includes public fields, private fields, private methods, decorators, and more.
Approximate Duration: 60
Your Name:* Daniel Ehrenberg
Your Twitter handle:* littledan
Requirements:
[x] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Advanced
[x] Intermediate
[ ] Beginner
Other information:
Session Title:
AMA on V8 with @verwaest and @bmeurer
Session Abstract:
We'll try to answer whatever questions you have regarding V8. Specifically topics around performance and how V8 works under the hood.
Approximate Duration:
30 - 60 minutes
Your Name:
Toon Verwaest (@verwaest)
Benedikt Meurer (@bmeurer)
Your Twitter handle:
tverwaes and bmeurer
Requirements:
[ ] No
[x] Yes => Presenter with USB-C
Complexity:
[x] Advanced
[x] Intermediate
[ ] Beginner
Other information:
The motivation is to give you time to ask whatever question you have, and which might be interesting to others as well.
Session Title:
What's coming in TC39? We want your help!
Session Abstract:
Give an overview of some of the topics under discussion at TC39, where they are in the standards process, and (most importantly) feedback from everyone in the room about what they think. At the end, it would open up to open-ended discussion about what other features should be discussed
Approximate Duration:
90 minutes
(Yes, this is a bit long, but in previous meetings where I've just gone over just a meeting agenda with various other groups of intelligent engineers, even 90 minutes has not quite been enough time.)
Your Name:
Daniel Ehrenberg
Your Twitter handle:
littledan
Requirements:
[ x ] No
[ ] Yes => Please share what do you need.
Complexity:
[ x ] Advanced
[ x ] Intermediate
[ ] Beginner
Session Title:
V8 startup snapshot
Session Abstract:
Approximate Duration:
30 minutes
Your Name:
Yang Guo
Your Twitter handle:
hashseed
Requirements:
[x] No
[ ] Yes => Please share what do you need.
Complexity:
[x] Advanced
[x] Intermediate
[ ] Beginner
Session Title:
Surfacing JavaScript engine signals
Session Abstract:
The V8 and Node.js projects are looking into surfacing some relevant (internal) signals from the JavaScript engine that could be useful to developers, for example information about when optimization happens, what function was optimized, which functions got inlined, and so on.
We'd like to have more feedback regarding what information developers are generally interested in, and how we could surface them best. The intended channel for the information so far is the Tracing Protocol, which works in both Node.js and Chrome. We'd also like to discuss how potential tools could be built around this.
Exploration document: http://bit.ly/v8-tracing-signals
Approximate Duration:
30 - 60 minutes
Your Name:*
Benedikt Meurer
Your Twitter handle:*
bmeurer
Requirements:
[ ] No
[x] Yes => projector + USB-C adapter
Complexity:
[x] Advanced
[ ] Intermediate
[ ] Beginner
Session Title: Create a PWA template for instant and offline pages
Session Abstract:
In this code-along we will create a Progressive Web App that makes use of Service Workers, IndexedDB and the Web Manifiest file to create a PWA with a Native App UI and the ability to work offline in both GET and POST mode.
We will also look at how to set up Push Notifications and use many of the new APIs that are becoming available.
By the end of the session you will have a sophisticated PWA scaffold that you can then develop further.
Approximate Duration:
90 minutes
Your Name:* Craig West
Your Twitter handle:*
Requirements:
[ ] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Intermediate
Other information:
Boiler plate pages will be included and the level of JS is intermediate. It would help if you have a local web server to develop the PWA on your own system.
We will also see how PWAs can provide 'instant' pages.
Session Title:
Session Abstract:
It’s when your manager is telling you exactly what you have to do right now in order to achieve the results he or she wants. The micromanager doesn’t trust you and that’s why wants and needs to control every step you make. It’s annoying and unproductive, but it’s inevitable unless you have small tasks and a transparent and unambiguous system of rewards and punishment.
The question is how you can define an obvious and transparent motivational system. A number of options will be suggested.
Approximate Duration:
30-50 minutes
Your Name: Yegor Bugayenko
Your Twitter handle: yegor256
Requirements:
[x] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Advanced
[x] Intermediate
[ ] Beginner
Other information:
This would motivate listeners (both employers and employees) to use micromanagement and microtasking as a main working model. Also, I would like to be evaluated by the attendees and organizators - their opinion would create a substrate for innovations and solutions. Who knows, maybe we'll create a new management model! :)
Session Title:
Untangling crash stacks with pasta
Session Abstract:
Source code often gets modified one way or another before hitting production - through transpilation, minification, etc. Looking at the raw crash stack of generated code can be hard work. Here's a comparison of crash stacks for a sample file.
// sample.js
const penne = () => { throw Error(); }
const spaghetti = () => penne();
const orzo = () => spaghetti();
orzo();// **original** output // **compiled** output
Error Error
at penne (sample.js:2:33) at r (out.js:1:82)
at spaghetti (sample.js:3:25) vs at o (out.js:1:97)
at orzo (sample.js:4:25) at n (out.js:1:107)Today, source maps already provide the ability to produce accurate locations (filename, line number, column number) in a crash stack, but not enclosing function names. This hinders debugging and confuses automatic crash stack consolidation.
In this session, we will discuss an extension to the source map format that allows for accurate function name decoding, and we will show you how to use it yourself by demonstrating our solution, pasta.
Note: We are planning to publish pasta as open source in time for JSKongress.
Approximate Duration:
30 mins
Your Name:
Lilit Darbinyan
Your Company:
Bloomberg
Your Twitter handle:
lilitdarbinyan
Requirements:
[] No
[x] Yes => A projector and a USB-C adapter so I can show my supporting slide deck
Complexity:
[ ] Advanced
[x] Intermediate
[ ] Beginner
Session Title:
How to share non-JS stuff on NPM
Session Abstract:
NPM is not only a package manager for Node.js, it's the biggest JavaScript packager manager in general. As a consequence, developers want to also share web-related stuff, like CSS (including Sass or Less), HTML templates, images, fonts, etc. However, there is no way to package these things without making assumptions about the application build system/tool. For instance, there is no way how a JavaScript web component can reference a CSS file or an image without making assumptions about the build tool. These need to be added manually by the package consumer.
This question even becomes more important with the advance of WebAssembly. Will it be possible to have different programming languages on NPM, maybe even depending on each other?
During this session, we want to discuss with you how we can open up the biggest JavaScript ecosystem to other web-related code.
Approximate Duration:
60
Your Name:
Johannes Ewald
Your Twitter handle:
jhnnns
Requirements:
[x] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Advanced
[x] Intermediate
[ ] Beginner
Other information:
Session Title:
Roll it up, shake it out: The future of Rollup.js
Session Abstract:
Rollup is "the other JavaScript bundler" that has pioneered features such as "tree-shaking" and "scope-hoisting" and has been adopted by popular libraries such as React or Moment.js as their bundling tool. However in the past, tree-shaking has remained an unfulfilled promise in most real-world situations. This is changing now.
As the current main contributor of Rollup, I would like to talk with you about the following:
Approximate Duration:
60 minutes
Your Name:*
Lukas Taegert
Your Twitter handle:*
lukastaegert
Requirements:
[ ] No
[x] Yes => A projector and a USB-C adapter would help when talking about code samples
Complexity:
[ ] Advanced
[x] Intermediate
[x] Beginner
Other Information:
Due to time constraints on my side, this session can only take place on Tuesday morning.
Session Title: Immutable values, operator overloading, and custom numeric literals
Session Abstract: Discuss some extremely early ideas in TC39 about extending the language to support various aspects of custom types
Approximate Duration: 60
Your Name:* Daniel Ehrenberg
Your Twitter handle:* littledan
Requirements:
[x] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Advanced
[x] Intermediate
[ ] Beginner
Other information:
Session Title: Technical SEO clinic
Session Abstract: Come with your questions around technical SEO or submit your website & a question upfront (link TBA) to get a (public) analysis of what's going on.
Approximate Duration: 45 minutes
Your Name:* Martin Splitt
Your Twitter handle:* g33konaut
Requirements:
[ ] No
[x] Yes, projector would be useful
Complexity:
[ ] Advanced
[x] Intermediate
[ ] Beginner
Other information:
Session Title:
A blueprint for an ideal Continuous Integration (CI) & Continuous Delivery (CD) process in javascript projects
Session Abstract:
I would like to present the below topics as part of this session:
Approximate Duration:
40 minutes
Your Name:
Dr. Arash Gharibi
Your Twitter handle:
arash_gharibi
Requirements:
[ ] No
[x] Yes: a projector
Complexity:
[ ] Advanced
[x] Intermediate
[x] Beginner
Other information:
CI/CD concept has been around for couple of years but when it comes to JavaScript projects, there has been difficulties in fully implementing this process chain. This session will help you to (1) get to know the latest trends and technologies used for CI/CD process, (2) learn/refresh your mind about various CI/CD components and (2) shows you a blue print/best practice on how an ideal CI/CD process functions.
Session Title:
JavaScript plugin and extension systems
Session Abstract:
There are quite a few ways how to implement a plugin system in JavaScript for your own tool. I'd like to point out a few with some high-level pros and cons I could see while researching them. Maybe there are a few participants around for a good discussion around this topic who already built a system of their own or have experience working with some.
Approximate Duration:
60 minutes
Your Name:
Jörn Bernhardt
Your Twitter handle:
NarigoDF
Requirements:
Complexity:
Other information:
I want to add a plugin system to my own tool, so I'm currently researching about this topic. I hope there are some participants who can contribute ideas, point out issues they had when creating their own or can give some insights why the system was built the way it was built.
Update: Session is done. There are Session notes.
Session Title:
RxJS 8 and beyond
Session Abstract:
RxJS has been around for quite a while. Recently it got pretty quiet around RxJS, right?
With this talk, I am going to show the internals of the planned architecture for version 8,
which is highly WIP-ish. By comparing the current architecture with the new, one will see
the differences, but also the benefits everyone is supposed to gain.
Approximate Duration:
~ 30 minutes
Your Name:*
Jan-Niklas Wortmann
Your Twitter handle:*
niklas_wortmann
Requirements:
[x] No
[ ] Yes => Please share what do you need.
Complexity:
[x] Advanced
[ ] Intermediate
[ ] Beginner
Other information:
This talk aims to increase transparency about the stuff that is planned within the RxJS Core Team.
Additionally, this is (AFAIK) the first talk going through the new architecture. I hope to get some feedback about possible technical implications, but also help the community to prepare their applications.
Session Title:
Immutable data structures in JS? A deep dive in the Record & Tuple Stage 1 Proposal
Session Abstract:
In this session, you will get to discover a new JS proposal that is still being worked on by TC39. You will not only get to see a preview of that feature, but you'll get to play with it and try it. While doing this, we will be able to discuss the different advantages and limitations of the proposal and you will be able to give some thoughts and feedback directly to one of the author and champion of the proposal: Robin Ricard, a TC39 Delegate working for Bloomberg.
Outline of the presentation:
Approximate Duration:
60min
Your Name:
Robin Ricard
Your Twitter handle:
r_ricard
Requirements:
[ ] No
[x] Yes => HDMI to project computer's screen or a computer with a modern web browser capable of projecting on a screen
Complexity:
[ ] Advanced
[x] Intermediate
[ ] Beginner
Other information:
Session Title: JavaScript debugging with Chrome DevTools
Session Abstract:
Everything JavaScript in Chrome DevTools, including debugging and profiling. In particular we are interested in discussions and feature requests around the JavaScript Console and the recently introduced REPL mode.
Approximate Duration:
30 minutes
Your Name: Simon Zuend, Peter Marshall
Your Twitter handle: nimODota, hooraybuffer
Requirements:
[ ] No
[ x] Yes => a way to present/cast to a screen
Complexity:
[x] Advanced
[x] Intermediate
[ ] Beginner
Session Title:
Lifetime of a JavaScript language feature
Session Abstract:
This session describes what happens from the moment when a feature is proposed to ECMAScript to when it gets fully integrated into the VM.
Approximate Duration:
30 minutes
Your Name:
V8 team
Your Twitter handle:
v8js
Requirements:
[x] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Advanced
[x] Intermediate
[ ] Beginner
Session Title: Understanding Reactive programming in JS
Session Abstract:
Let's create our own implementation of the library RXJS... at least a small one. The objective are two:
Approximate Duration:
60 min
Your Name:* Adrian Ferreres
Your Twitter handle:* ardiadrianadri
Requirements:
[ X] No
[ ] Yes => Please share what do you need.
Complexity:
[ ] Advanced
[ ] Intermediate
[ X] Beginner
Other information:
Session Title:
Contribute a Feature to TypeScript! An example based on the ES Private Fields implementation
Session Abstract:
This talk is a quick guide to contributing a new JS feature to TypeScript, end-to-end. The goals are to:
Outline:
Approximate Duration:
45 minutes
Your Name:*
Max Heiber
Your Twitter handle:*
maxheiber
Requirements:
[ ] No
[X] Yes => ability to share slides via HDMI
Complexity:
[X] Advanced
[X] Intermediate
[ ] Beginner (NO)
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.