I’m a software engineer & OSS contributor at Object Computing. I’ve been a developer for 7+ years, and React/Angular development for the past 3 years. A long-time server-side developer, I stumbled into the world of frontend, and decided I like it here.
Angular has brought MVC & dependency injection to the browser, while React nudges developers towards a simpler, functional approach to view rendering. What if there was a tool that took the best ideas from both of these titans, giving us simple, expressive components while still including enough “magic” to significantly boost developer productivity?
Enter Vue.js
In this talk we’ll get to know this new kid on the frontend block, contrast Vue with it’s better known rivals. We’ll explore the ecosystem: state management with Vuex, routing with Vue-router - and see why Vue.js might not be just another JavaScript framework.
A single-page application means putting a lot of traditionally server-side internals in the great unknown of a client's browser. The move of data and logic towards frontend requires a different model for application security. In addition to old foes like cross-site scripting, we now have to consider concepts like local storage, routing, JWTs and OAuth2 frameworks, and understand their implications in locking down our apps. Let's clear up the confusion and zero in on the approaches and techniques you need to secure your React app. We'll examine several layers of security relevant to React apps, including UI-level security (preventing XSS attacks and securing routes with React Router and Higher-Order Components), and API security using JWTs and third-party authentication-providers. The format of this talk won't include hands-on examples, but sample projects of the various approaches discussed will be provided.