dotJS official site official feed
Why am I still doing this?
Mostly it's just a (good) habit.
Also, it helps to overview the sessions once again at the slightly different angle (and attitude).
The videos will be available shortly, what is the point?
Well, apart from twitter channels and sort, it will be one of the earliest sources of info, after the conference itself. But more importantly, you'll definitely won't want to watch ALL the videos.
My (slightly biased) recommendations might help you to save couple of hours.
Something else?
Yes.
Same as usual - the content is provided as is: some names and titles are totally wrong, some links might be missing, some twitter accounts might be lost in the flow and finally - some feelings might be hurt. Sorry!
What started as an interesting journey into service workers with a handful of web history ended with "embracing web pluralism" motif.
Nice inspiring talk, though.
To watch: you will learn some history behind Flash / Silverlight / HTML5 competition
Not to watch: you can skim through the slides
The talk is about VR as a new web platform.
Good news, you can already experience some cool features, like playing 360 media, or remote co-presence!
Having in mind the VR devies can have integrated browsers the future of the 3d markup may look like this:
.container {
overflow-y: scroll;
perspective: 600px;
perspective: real3d; /* handle headset perspective?! */
height: 100vh;
}
.container .hero {
transform: translateZ(100px);
}
And remember, working on the web means working everywhere.
To watch: you want to pick up general idea of VR devices and their suggested future for the web
Not to watch: you are already involved
Christophe is appealing to the sense of moderation using transpiling tools, such as BabelJS.
The main idea is not to polyfill everything, but to make transition to the native API more seamless and graceful.
There are over 750 presets, but there's a hint - just use latest!
It is also interesting to know the differences between Babel and Typescript.
To watch: it is always greay to learn something new about your (favourite) everyday tool
Not to watch: you are really dedicated ES3 user and reluctant to change
I would recommend to watch this one completely since it's hard to find slides on the web.
What's more, there is a lot of schematics there that wouldn't mind your attention.
To watch: recommended, basing on the title
Not to watch: ES modules is not your cup of tea
Surprisingly for most, Electron enthusiast would not speak about Electron!
Instead, there was a huge collection of useful tools, services, links and npm modules to share about.
You can find them all in the repo.
To watch: you require some commentary for these links
Not to watch: just go through the repo content and discover something new
The talk is overviewing some basics of reactive programming with regards of application in some of the frameworks.
There are 2 models of change propagation (push-/pull-base) that you should know about.
Sadly, or better say, naturally, there is no silver bullet, so you have to come up with some mixed solutions.
To watch: brief and engaging introduction to the state-driven framework models (React, Vue, Knockout, ...)
Not to watch: slides can be pretty sufficient and time-saving
I would recommend to watch this one optionally, since the topic is a little bit low-level and technical, so slides will come at hand.
To watch: if you must
Not to watch: you are not supposed to be working with V8
Sam Wray & Tim Pietrusky - Fun time with Web audio API and fog machines powered by NodeJS (not really an exact title)
To be honest, this kind of talk is the one worth seeing live.
Guys really nailing it!
You can find code examples and more interesting stuff in the Live JS repo
To watch: you are interested in audio-visual enhancement of your projects
Not to watch: better visit some of their live events
The talk is mostly about Next.js framework,
which main goal is basically simplify server rendering for JS web apps.
built on top of React, Webpack and Babel, which powers this very site!
To watch: you pursue the idea of js-driven server rendering and would like to know more
Not to watch: documentation is pretty good and furthemore it's React-based
Did not attend :(
Would appreciate some info!
Thanks for reading!