Meeting room ESTOCOLMO - 1st floor
Meeting room BARCELONA - 1st floor
Meeting room LOS ANGELES - Park floor
Meeting room AMSTERDAM - Park floor
Meeting room MERIDA - 1st floor
by David Pich
Webpack 4 its here! But what does that mean to you? Join me as not only I help break down everything we’ve accomplished this year, but also look forward to what we have in store for you in the future. Join me as we’ll talk about what it means to represent the #0CJS (Zero Config JS) movement, what it means to put developers first, and how we aim to embody the term Legato: to perform in a smooth, flowing, manner without gaps.Join me as I breakdown why this update, more then any that have come before, is the most groundbreaking set of changes for the future of webpack and our ecosystem!
In 2011, state of the art in frontend development was generally a large MVC application, probably built with Backbone, styled with global css, and written in ES5. Fast forward today, and now we have to spend days or even weeks picking out what technologies we're going to use before we even start. And config files....don't even get me started on config files.
It's safe to say JS is no longer trying to prove itself. It has arrived. Even if it was once a 'dumb kid brother' to something like Java, it's now fully a first class citizen in the programming language ecosystem. JS is certainly not the only dominant language or the 'best tool' for every situation. But increasingly, most tech stacks have it as a central part of their strategy.
We'll look forward at the bets we continue placing on JS and the web, by first looking back at how far we've come and what those steps looked like. From these lessons, we can gaze into the distance and see what the path ahead may look like.
In web development, routing often refers to splitting an application’s UI based on rules derived from the browser URL. Numerous tools/libraries exist that allow us to enable routing both on the client and server side of applications.
What does it actually take to construct a client side router? First, I'll use the most basic tools that the Vue framework already provides to build a fully functional custom client side router. We'll then switch over to using the official vue-router library to understand all the benefits that it adds such as nested routes, navigation guards, transition effects, etc.
The objective of this talk is to convey the relevance/importance of client-side routing and how easy it is to accomplish with integrating vue-router to a well structured Vue app.
Writing 3D applications for the browser is possible since some years due to the WebGL API. But since Virtual Reality and Augmented Reality are getting more popular, web developers and designers now have a serious reason to get to know the 3D web, its APIs and design patterns.
Since the mid 90s, developers have struggled to build web applications that can be executed both on the client and the server. And still today, even with Node.js and virtual DOM libraries like React, this can be quite challenging.
In this talk, we'll look at common obstacles and problems that developers face when building this type of web application, including typical performance and security issues. You'll leave the presentation knowing how to build a fast and secure web application that can be rendered on the client and the server.
In this session we will talk about these challenges and possible solutions as well as what you should look out for.
Even if you've never done anything with machine learning, you have probably already heard that it's very powerful, adaptive and will change our way of thinking about computing forever. But how can you, a web developer, who's never been interested much in statistics benefit from the ML hype? In this talk I want to give you the tools to build a small self-learning application that runs completely in the browser with deeplearn.js
We will talk about how we've been doing design at npm, and how we think about UX. We'll talk about stages of UX Design in organizations and where npm stands. Who designs at npm? Although I'm the only designer, anyone who touches product makes an impact on the UX, and that's where we're headed.
Although we usually know what components are needed when building most views within an app, sometimes we don't know what they are until runtime. This means we need to build a screen based on the application state, user preferences, or response from an API. A common case is building dynamic forms, where the questions and components needed are either configured by a JSON object, or where fields change based on the users' answers.