Podcasts about googlechromelabs

Steve and Josh discuss Josh's blog post that compares and contrasts Svelte, Vue, and React. They also talk about Josh's new game Quina, which is a Wordle clone with a few twists and is built with Nuxt. Josh also displays the influence of Steve's dad joke juggernaut by bringing his own dad jokes for picks. Sponsors Top End Devs (https://topenddevs.com/) Coaching | Top End Devs (https://topenddevs.com/coaching) Links Introducing Svelte, and Comparing Svelte with React and Vue (https://joshcollinsworth.com/blog/introducing-svelte-comparing-with-react-vue) Josh Collinsworth (https://joshcollinsworth.com/blog) Josh Collinsworth - writing and speaking (https://joshcollinsworth.com/writing-and-speaking) Quina (https://quina.app/) Picks Josh- SvelteKit (https://kit.svelte.dev/) Josh- The Third Web (https://tante.cc/2021/12/17/the-third-web/) Josh- Material Kitchen coated pan (https://materialkitchen.com/products/the-coated-pan) Steve- Nuxt Image (https://image.nuxtjs.org/components/nuxt-img/) Steve- GitHub - GoogleChromeLabs/bubblewrap (https://github.com/GoogleChromeLabs/bubblewrap) Steve- Hebrew wordle (https://wordleheb.web.app/) Special Guest: Josh Collinsworth .

Edellinen bäkkärijakso aktivoi palautekanavia, joten Tommi päätyi tarkentamaan kommenttia PHP:sta ja sen muutoksista. Tämän lisäksi aikaisemmassa jaksossa mainittu Remix julkaistiin ja Antti kokeili, miten se toimii.Jakson pääaiheena on CSS, erityisesti sen mahdolliset uudet ominaisuudet. Suurinta keskustelua webbipuolella on viimeaikoina aiheuttanut Container Queryt. Tähän aiheeseen pureudutaan syvemmin. Hieman lyhyemmin käydään läpi nesting CSS preprosessoreista tuttu nesting, CSS Cascade Layers, @when-sääntö, sekä @scope-sääntö.LinkitPHPhttps://bulletproofphp.dev/yes-php-is-worth-usingRemixRemixBlogitutorial@containerhttps://alistapart.com/article/responsive-web-design/Say Hello to Container QueriesContainer Queries for Designershttps://youtu.be/JsN_iE3prm0https://github.com/GoogleChromeLabs/container-query-polyfillContainer Query Unitshttps://drafts.csswg.org/css-contain-3/#container-lengths@nesthttps://www.w3.org/TR/2021/WD-css-nesting-1-20210831/@layerhttps://www.bram.us/2021/09/15/the-future-of-css-cascade-layers-css-at-layer/@whenhttps://css-tricks.com/proposal-for-css-when/https://tabatkins.github.io/specs/css-when-else/@scopeEarly Days for CSS ScopingViikon hyvät fiiliksetTommi: Corne-näppäimistön rakentaminenAntti: Avantouinti

JavaScript Remote Conf 2020 May 13th to 15th - register now! Despite JavaScript being a single-threaded language, you can now leverage multi-threaded computing thanks to modern browser features such as web workers, workouts and service workers. In this show, Majid explains how these features work and what problems they solve. We also discuss the strategies you can use to introduce them to production codebases and give your users a much more enjoyable experience on your web app. Panel Paige Niedringhaus Carl Mungazi Charles Max Wood TJ VanToll Guest Majid Hajian Sponsors G2i | Enjoy the luxuries of freelancing "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! Links Comlink makes WebWorkers enjoyable Workbox Figma The AssemblyScript Book Houdini: Demystifying CSS Picks Majid Hajian: Follow Majid on Twitter > @mhadaily Deep Work - Cal Newport Carl Mungazi: Off the Main Thread | The Web Platform Podcast Charles Max Wood: Natural Goat Milk Soaps for Healthy Skin — Goat Milk Stuff ‎Flip Timer & stopwatch on the App Store Desktop tripod Devchat.tv Remote meetups Devchat.tv Remote Conferences Paige Niedringhaus: DJI Phantom 4 Drone Ozark show on Netflix TJ VanToll: Goat-2-Meeting — Sweet Farm Follow React Round Up on Twitter > @reactroundup

JavaScript Remote Conf 2020 May 13th to 15th - register now! Despite JavaScript being a single-threaded language, you can now leverage multi-threaded computing thanks to modern browser features such as web workers, workouts and service workers. In this show, Majid explains how these features work and what problems they solve. We also discuss the strategies you can use to introduce them to production codebases and give your users a much more enjoyable experience on your web app. Panel Paige Niedringhaus Carl Mungazi Charles Max Wood TJ VanToll Guest Majid Hajian Sponsors G2i | Enjoy the luxuries of freelancing "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! Links Comlink makes WebWorkers enjoyable Workbox Figma The AssemblyScript Book Houdini: Demystifying CSS Picks Majid Hajian: Follow Majid on Twitter > @mhadaily Deep Work - Cal Newport Carl Mungazi: Off the Main Thread | The Web Platform Podcast Charles Max Wood: Natural Goat Milk Soaps for Healthy Skin — Goat Milk Stuff ‎Flip Timer & stopwatch on the App Store Desktop tripod Devchat.tv Remote meetups Devchat.tv Remote Conferences Paige Niedringhaus: DJI Phantom 4 Drone Ozark show on Netflix TJ VanToll: Goat-2-Meeting — Sweet Farm Follow React Round Up on Twitter > @reactroundup

Maximiliano Firtman is a mobile web developer from Buenos Ares, Argentina. He has been a developer for 24 years and his most recent focus has been on progressive web apps, or PWAs. Steve and Max reflect on the technologies they were using when they first got started in web development and talk about their experience with mobile development. One area that Max emphasized was bringing the web into the mobile space. They discuss the progression of web access on mobile and some of the available tools. Max notes that responsible design has a very high cost in web performance for mobile devices, which requires unique approaches. They discuss some of the issues with latency in mobile, even on 4G. The solution to this latency is PWAs. Progressive web apps are a set of best practices to create web apps that are installable. They can work offline at high speeds on several operating systems. Once installed, it looks like any other app on the system. Max delves into more details on how it works. He talks about how the resources for your application are managed. He assures listeners that it’s just a website that’s using a new API, they’re not changing the way the web works, and that when that API is there, the app can be installed. It will also generally use your default browser. Steve and Max discuss how local data is stored with PWAs. To write PWAs, you can use Angular, React, JavaScript, or Vue, and it’s a pretty transparent process. Max talks about some common tools used for local storage and some of the PWAs he’s worked on in the past. The benefit of using PWAs is that they generally run faster than regular web apps. To get started, Max advises listeners to install one and start exploring. Panelists Steve Edwards Guest Maximiliano Firtman Sponsors G2i ____________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________ Links Progressive Web Apps Appsco.pe IndexedDB Max's site Picks Steve Edwards: The Club Maximiliano Firtman: Llama Follow Max on Twitter

Maximiliano Firtman is a mobile web developer from Buenos Ares, Argentina. He has been a developer for 24 years and his most recent focus has been on progressive web apps, or PWAs. Steve and Max reflect on the technologies they were using when they first got started in web development and talk about their experience with mobile development. One area that Max emphasized was bringing the web into the mobile space. They discuss the progression of web access on mobile and some of the available tools. Max notes that responsible design has a very high cost in web performance for mobile devices, which requires unique approaches. They discuss some of the issues with latency in mobile, even on 4G. The solution to this latency is PWAs. Progressive web apps are a set of best practices to create web apps that are installable. They can work offline at high speeds on several operating systems. Once installed, it looks like any other app on the system. Max delves into more details on how it works. He talks about how the resources for your application are managed. He assures listeners that it’s just a website that’s using a new API, they’re not changing the way the web works, and that when that API is there, the app can be installed. It will also generally use your default browser. Steve and Max discuss how local data is stored with PWAs. To write PWAs, you can use Angular, React, JavaScript, or Vue, and it’s a pretty transparent process. Max talks about some common tools used for local storage and some of the PWAs he’s worked on in the past. The benefit of using PWAs is that they generally run faster than regular web apps. To get started, Max advises listeners to install one and start exploring. Panelists Steve Edwards Guest Maximiliano Firtman Sponsors G2i ____________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________ Links Progressive Web Apps Appsco.pe IndexedDB Max's site Picks Steve Edwards: The Club Maximiliano Firtman: Llama Follow Max on Twitter

Maximiliano Firtman is a mobile web developer from Buenos Ares, Argentina. He has been a developer for 24 years and his most recent focus has been on progressive web apps, or PWAs. Steve and Max reflect on the technologies they were using when they first got started in web development and talk about their experience with mobile development. One area that Max emphasized was bringing the web into the mobile space. They discuss the progression of web access on mobile and some of the available tools. Max notes that responsible design has a very high cost in web performance for mobile devices, which requires unique approaches. They discuss some of the issues with latency in mobile, even on 4G. The solution to this latency is PWAs. Progressive web apps are a set of best practices to create web apps that are installable. They can work offline at high speeds on several operating systems. Once installed, it looks like any other app on the system. Max delves into more details on how it works. He talks about how the resources for your application are managed. He assures listeners that it’s just a website that’s using a new API, they’re not changing the way the web works, and that when that API is there, the app can be installed. It will also generally use your default browser. Steve and Max discuss how local data is stored with PWAs. To write PWAs, you can use Angular, React, JavaScript, or Vue, and it’s a pretty transparent process. Max talks about some common tools used for local storage and some of the PWAs he’s worked on in the past. The benefit of using PWAs is that they generally run faster than regular web apps. To get started, Max advises listeners to install one and start exploring. Panelists Steve Edwards Guest Maximiliano Firtman Sponsors G2i ____________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________ Links Progressive Web Apps Appsco.pe IndexedDB Max's site Picks Steve Edwards: The Club Maximiliano Firtman: Llama Follow Max on Twitter

Episode Summary Surma is an open web advocate for Google currently working with WebAssembly team. He was invited on the show today to talk about using web workers and how to move work away from the browser’s main thread. His primary platform is bringing multithreading out of the fringes and into the web.  The panel talks about their past experience with web workers, and many of them found them isolated and difficult to use. Surma believes that web workers should pretty much always be sued because the main thread is an inherently bad place to run your code because it has to do so much. Surma details the differences between web workers, service workers, and worklets and explains what the compositer is.  The panel discusses what parts should be moved off the main thread and how to move the logic over. Surma notes that the additional cost of using a worker is basically nonexistent, changes almost nothing in your workflow, and takes up only one kilobyte of memory. Therefore, the cost/benefit ratio of using web workers gets very large. They discuss debugging in a web worker and Surma details how debugging is better in web workers.  Surma wants to see people use workers not because it will make it faster, but because it will make your app more resilient across all devices. Every piece of JavaScript you run could be the straw that breaks the camel’s back. There’s so much to do on the main thread for the browser, especially when it has a weaker processor, that the more stuff you can move away, the better. The web is tailored for the most powerful phones, but a large portion of the population does not have the most powerful phone available, and moving things over to a web worker will benefit the average phone. Surma talks about his experience using the Nokia 2, on which simple apps run very slow because they are not being frugal with the user’s resources. Moving things to another thread will help phones like this run faster.   The panel discusses the benefit of using web workers from a business standpoint. The argument is similar to that for accessibility. Though a user may not need that accessibility all the time, they could become in need of it. Making the app run better on low end devices will also increase the target audience, which is helpful is user acquisition is your principle metric for success.  Surma wants businesses to understand that while this is beneficial for people in countries like India, there is also a very wide spectrum of phone performance in America. He wants to help all of these people and wants companies acknowledge this spectrum and to look at the benefits of using web workers to improve performance. Panelists Charles Max Wood Christopher Buecheler Aimee Knight AJ O’Neal With special guest: Surma Sponsors Adventures in DevOps Sentry use the code “devchat” for 2 months free on Sentry’s small plan Adventures in Angular Links Web workers Service workers Worklets  Ecto model Babel Swoosh Comlink WhatsApp Follow DevChatTV on Facebook and Twitter Picks Charles Max Wood: For Love of Mother-Not Surma: Follow Surma @DasSurma on Twitter and at dassur.ma WebAssembly Spec AJ O’Neal: The GameCube Ultimate Pikmin for Wii and GameCube Super Monkey Ball Christopher Buecheler CinemaSins Sincast podcast

Episode Summary Surma is an open web advocate for Google currently working with WebAssembly team. He was invited on the show today to talk about using web workers and how to move work away from the browser’s main thread. His primary platform is bringing multithreading out of the fringes and into the web.  The panel talks about their past experience with web workers, and many of them found them isolated and difficult to use. Surma believes that web workers should pretty much always be sued because the main thread is an inherently bad place to run your code because it has to do so much. Surma details the differences between web workers, service workers, and worklets and explains what the compositer is.  The panel discusses what parts should be moved off the main thread and how to move the logic over. Surma notes that the additional cost of using a worker is basically nonexistent, changes almost nothing in your workflow, and takes up only one kilobyte of memory. Therefore, the cost/benefit ratio of using web workers gets very large. They discuss debugging in a web worker and Surma details how debugging is better in web workers.  Surma wants to see people use workers not because it will make it faster, but because it will make your app more resilient across all devices. Every piece of JavaScript you run could be the straw that breaks the camel’s back. There’s so much to do on the main thread for the browser, especially when it has a weaker processor, that the more stuff you can move away, the better. The web is tailored for the most powerful phones, but a large portion of the population does not have the most powerful phone available, and moving things over to a web worker will benefit the average phone. Surma talks about his experience using the Nokia 2, on which simple apps run very slow because they are not being frugal with the user’s resources. Moving things to another thread will help phones like this run faster.   The panel discusses the benefit of using web workers from a business standpoint. The argument is similar to that for accessibility. Though a user may not need that accessibility all the time, they could become in need of it. Making the app run better on low end devices will also increase the target audience, which is helpful is user acquisition is your principle metric for success.  Surma wants businesses to understand that while this is beneficial for people in countries like India, there is also a very wide spectrum of phone performance in America. He wants to help all of these people and wants companies acknowledge this spectrum and to look at the benefits of using web workers to improve performance. Panelists Charles Max Wood Christopher Buecheler Aimee Knight AJ O’Neal With special guest: Surma Sponsors Adventures in DevOps Sentry use the code “devchat” for 2 months free on Sentry’s small plan Adventures in Angular Links Web workers Service workers Worklets  Ecto model Babel Swoosh Comlink WhatsApp Follow DevChatTV on Facebook and Twitter Picks Charles Max Wood: For Love of Mother-Not Surma: Follow Surma @DasSurma on Twitter and at dassur.ma WebAssembly Spec AJ O’Neal: The GameCube Ultimate Pikmin for Wii and GameCube Super Monkey Ball Christopher Buecheler CinemaSins Sincast podcast

Episode Summary Surma is an open web advocate for Google currently working with WebAssembly team. He was invited on the show today to talk about using web workers and how to move work away from the browser’s main thread. His primary platform is bringing multithreading out of the fringes and into the web.  The panel talks about their past experience with web workers, and many of them found them isolated and difficult to use. Surma believes that web workers should pretty much always be sued because the main thread is an inherently bad place to run your code because it has to do so much. Surma details the differences between web workers, service workers, and worklets and explains what the compositer is.  The panel discusses what parts should be moved off the main thread and how to move the logic over. Surma notes that the additional cost of using a worker is basically nonexistent, changes almost nothing in your workflow, and takes up only one kilobyte of memory. Therefore, the cost/benefit ratio of using web workers gets very large. They discuss debugging in a web worker and Surma details how debugging is better in web workers.  Surma wants to see people use workers not because it will make it faster, but because it will make your app more resilient across all devices. Every piece of JavaScript you run could be the straw that breaks the camel’s back. There’s so much to do on the main thread for the browser, especially when it has a weaker processor, that the more stuff you can move away, the better. The web is tailored for the most powerful phones, but a large portion of the population does not have the most powerful phone available, and moving things over to a web worker will benefit the average phone. Surma talks about his experience using the Nokia 2, on which simple apps run very slow because they are not being frugal with the user’s resources. Moving things to another thread will help phones like this run faster.   The panel discusses the benefit of using web workers from a business standpoint. The argument is similar to that for accessibility. Though a user may not need that accessibility all the time, they could become in need of it. Making the app run better on low end devices will also increase the target audience, which is helpful is user acquisition is your principle metric for success.  Surma wants businesses to understand that while this is beneficial for people in countries like India, there is also a very wide spectrum of phone performance in America. He wants to help all of these people and wants companies acknowledge this spectrum and to look at the benefits of using web workers to improve performance. Panelists Charles Max Wood Christopher Buecheler Aimee Knight AJ O’Neal With special guest: Surma Sponsors Adventures in DevOps Sentry use the code “devchat” for 2 months free on Sentry’s small plan Adventures in Angular Links Web workers Service workers Worklets  Ecto model Babel Swoosh Comlink WhatsApp Follow DevChatTV on Facebook and Twitter Picks Charles Max Wood: For Love of Mother-Not Surma: Follow Surma @DasSurma on Twitter and at dassur.ma WebAssembly Spec AJ O’Neal: The GameCube Ultimate Pikmin for Wii and GameCube Super Monkey Ball Christopher Buecheler CinemaSins Sincast podcast

Sponsors Sentry use the code “devchat” for $100 credit Triplebyte CacheFly Panel Lucas Reis Justin Bennett Charles Max Wood Joined by special guests: Chris Toomey Episode Summary In this episode of React Round Up, Chris Toomey introduces himself, talks about his work and his podcast and moves on to explaining the differences between a React vs GraphQL centric application. Justin explains in detail how the Relay framework works, and Chris describes the scenarios where GraphQL stands out in the process of building an application and also throws some light on the benefits of choosing it over other APIs such as REST. The panel then discusses how GraphQL is advantageous in the documentation context since it has a good schema, and also in data modeling. Chris shares some past examples of creating React applications where GraphQL and Apollo made things much simpler, and also elaborates on the trade-offs and challenges associated with it. Links The Bike Shed Chris Toomey: React & GraphQL – Bringing Simplicity to Client-Side Development / React Boston 2018 Chris’s Twitter The Past, Present, and Future of GraphQL Native - Nick Schrock @ GraphQL Europe Picks Justin Bennett: Where art thou, my error? Auto by Intuit on GitHub Lucas Reis: MDX Deck library Code Surfer library Charles Max Wood: HubSpot Zapier Google Docs Chris Toomey: Tell me when it closes Quicklink Upcase

Sponsors Sentry use the code “devchat” for $100 credit Triplebyte CacheFly Panel Lucas Reis Justin Bennett Charles Max Wood Joined by special guests: Chris Toomey Episode Summary In this episode of React Round Up, Chris Toomey introduces himself, talks about his work and his podcast and moves on to explaining the differences between a React vs GraphQL centric application. Justin explains in detail how the Relay framework works, and Chris describes the scenarios where GraphQL stands out in the process of building an application and also throws some light on the benefits of choosing it over other APIs such as REST. The panel then discusses how GraphQL is advantageous in the documentation context since it has a good schema, and also in data modeling. Chris shares some past examples of creating React applications where GraphQL and Apollo made things much simpler, and also elaborates on the trade-offs and challenges associated with it. Links The Bike Shed Chris Toomey: React & GraphQL – Bringing Simplicity to Client-Side Development / React Boston 2018 Chris’s Twitter The Past, Present, and Future of GraphQL Native - Nick Schrock @ GraphQL Europe Picks Justin Bennett: Where art thou, my error? Auto by Intuit on GitHub Lucas Reis: MDX Deck library Code Surfer library Charles Max Wood: HubSpot Zapier Google Docs Chris Toomey: Tell me when it closes Quicklink Upcase

Una extensión para trabajar con la web en el navegador como si fuera una imagen. https://github.com/GoogleChromeLabs #extension #chrome Autor: Daniel Primo Síguenos en https://twitter.com/RadioDevPodcast y https://t.me/RadioDev

Recording date: 2018-09-20 Tweet John Papa https://twitter.com/john_papa Ward Bell https://twitter.com/wardbell Dan Wahlin https://twitter.com/danwahlin (0:01:51) John reads the mailbag about browser support, service workers performance imapc,t and adding home screens to PWAs. (0:01:51) Mailbag https://twitter.com/RealTalkJS/status/1042572672025194496 (00:2:15) Maxim describes PWA support in the browsers (0:03:10) Ward points out that Addy Osmani https://twitter.com/addyosmani says: "It's important to remember that Progressive Web Apps work everywhere but are supercharged in modern browsers. Progressive enhancement is a backbone of the model." (0:03:42) Service worker support in "Can I Use" https://caniuse.com/#feat=serviceworkers (0:03:50) Maxim recommends using the PWA feature detector https://github.com/tomayac/pwa-feature-detector (0:04:10) Maxim answers John's question about how PWAs have changed over the past few years (0:05:45) Maxim answers what a PWA is and the value to developers and users (0:07:00) Ward asks "What problem does PWA solve?" (0:07:43) Dan asks what he benefits of PWA are to an enterprise business (0:08:50) Maxim points out how low wifi (LiFi) can be hard to deal with (0:09:22) What is a PWA https://developers.google.com/web/progressive-web-apps/ (0:09:30) Ward asks if a PWA magically knows if its offline or not (0:11:50) Maxim talks about LiFi as really low connectivity (0:13:20) John clarifies with Maxim that PWAs uses browser APIs to check their connectivity (0:14:00) Ward asks if he should use the raw service worker protocol (0:15:15) Dan and Ward asks Maxim what makes this easier (0:16:57) Maxim talks about the Workbox project https://developers.google.com/web/tools/workbox/ (0:18:15) John asks Maxim what else besides Service Workers, that is a part of PWAs (0:18:30) Maxim discusses web app manfiest https://developer.mozilla.org/en-US/docs/Web/Manifest (0:21:10) Maxim talks about Service Worker precache https://github.com/GoogleChromeLabs/sw-precache (0:22:22) Ward asks Maxim to tell a story about one of Maxim's successful experiences with PWAs (0:28:26) mobile era rocks PWA https://mobileera.rocks/ (0:28:46) Ward raises how conferences are notorious for low wifi (0:33:00) John asks Maxim when not to do a PWA (0:38:00) Ward, John and Maxim discuss security concerns with PWAs (0:44:30) Lighthouse tool for PWAs https://chrome.google.com/webstore/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk (0:45:30) Maxim mentions the Web Hint tool for PWAs https://webhint.io/ (tip: npx hint https://example.com ) (0:46:50) Someone to follow: Nicholas Zakas https://twitter.com/slicknet https://humanwhocodes.com/ (0:47:38) Someone to follow: Simona Cotin https://twitter.com/simona_cotin?lang=en (0:48:10) Someone to follow: Arthur Stolyar https://twitter.com/nekrtemplar Additional Resources PWA Checklist https://developers.google.com/web/progressive-web-apps/checklist Curated list of PWA news by Maxim: https://twitter.com/progwebnews/ PWA Feature Detector https://tomayac.github.io/pwa-feature-detector/ Mobile Era PWA: https://mobileera.rocks/ Workbox: https://workboxjs.org Webhint: https://webhint.io PWA Get Started: https://developers.google.com/web/progressive-web-apps/ https://developer.microsoft.com/en-us/windows/pwa Excellent post on PWA: https://developers.google.com/web/updates/2015/12/getting-started-pwa

Panel: Joe Eames Cory House Aimee Knight Special Guests: Ben Clinkinbeard In this episode, the JavaScript Jabber panelists talk about D3.js with Ben Clinkinbeard. D3.js is a JavaScript library that has you use declarative code to tell it what you want and then it figures out all of the browser inconsistencies and creates the notes for you. He talks about the two main concepts behind D3, scales and selections, which once you understand make D3 a lot more user friendly. He then touches on SPGs and discusses his Learn D3 in 5 Days course. In particular, we dive pretty deep on: What is D3.js? Stands for Data Driven Documents JavaScript How much of the learning curve is attributed to learning D3? SPG 2 main concepts behind D3: scales and selections Is learning about SPGs a prerequisite to leaning D3? How serious are you talking when saying idiosyncrasies? SPG tag Understanding positioning in SPG Positions with CSS transforms Are you required to use SPG? Not required to use SPG with D3 Canvas SPG is vector based SPG utility function Responseivefy Learn D3 in 5 Days course Is there and overlap with D3 and React? And much, much more! Links: D3.js JavaScript Responsivefy Learn D3 in 5 Days course React @bclinkinbeard Ben’s GitHub Picks: Cory React cheat sheet “Why software engineers disagree about everything” by Haseeb Qureshi Joe Eames “JavaScript vs. TypeScript vs. ReasonML” by Dr. Axel Rauschmayer Aimee “How To Use Technical Debt In Your Favor” Neuroscience News Twitter Ben ComLink

Panel: Joe Eames Cory House Aimee Knight Special Guests: Ben Clinkinbeard In this episode, the JavaScript Jabber panelists talk about D3.js with Ben Clinkinbeard. D3.js is a JavaScript library that has you use declarative code to tell it what you want and then it figures out all of the browser inconsistencies and creates the notes for you. He talks about the two main concepts behind D3, scales and selections, which once you understand make D3 a lot more user friendly. He then touches on SPGs and discusses his Learn D3 in 5 Days course. In particular, we dive pretty deep on: What is D3.js? Stands for Data Driven Documents JavaScript How much of the learning curve is attributed to learning D3? SPG 2 main concepts behind D3: scales and selections Is learning about SPGs a prerequisite to leaning D3? How serious are you talking when saying idiosyncrasies? SPG tag Understanding positioning in SPG Positions with CSS transforms Are you required to use SPG? Not required to use SPG with D3 Canvas SPG is vector based SPG utility function Responseivefy Learn D3 in 5 Days course Is there and overlap with D3 and React? And much, much more! Links: D3.js JavaScript Responsivefy Learn D3 in 5 Days course React @bclinkinbeard Ben’s GitHub Picks: Cory React cheat sheet “Why software engineers disagree about everything” by Haseeb Qureshi Joe Eames “JavaScript vs. TypeScript vs. ReasonML” by Dr. Axel Rauschmayer Aimee “How To Use Technical Debt In Your Favor” Neuroscience News Twitter Ben ComLink

Panel: Joe Eames Cory House Aimee Knight Special Guests: Ben Clinkinbeard In this episode, the JavaScript Jabber panelists talk about D3.js with Ben Clinkinbeard. D3.js is a JavaScript library that has you use declarative code to tell it what you want and then it figures out all of the browser inconsistencies and creates the notes for you. He talks about the two main concepts behind D3, scales and selections, which once you understand make D3 a lot more user friendly. He then touches on SPGs and discusses his Learn D3 in 5 Days course. In particular, we dive pretty deep on: What is D3.js? Stands for Data Driven Documents JavaScript How much of the learning curve is attributed to learning D3? SPG 2 main concepts behind D3: scales and selections Is learning about SPGs a prerequisite to leaning D3? How serious are you talking when saying idiosyncrasies? SPG tag Understanding positioning in SPG Positions with CSS transforms Are you required to use SPG? Not required to use SPG with D3 Canvas SPG is vector based SPG utility function Responseivefy Learn D3 in 5 Days course Is there and overlap with D3 and React? And much, much more! Links: D3.js JavaScript Responsivefy Learn D3 in 5 Days course React @bclinkinbeard Ben’s GitHub Picks: Cory React cheat sheet “Why software engineers disagree about everything” by Haseeb Qureshi Joe Eames “JavaScript vs. TypeScript vs. ReasonML” by Dr. Axel Rauschmayer Aimee “How To Use Technical Debt In Your Favor” Neuroscience News Twitter Ben ComLink

Descripcion del programa José Manuel es ingeniero de software, trabaja como desarrollador web en Estocolmo para Spotify. Especializado en web performance optimization, SEO y accesibilidad. Con él nos adentraremos en el mundo de las Progressive Web Apps, y veremos como gracias al nuevo Catálogo de Apis podemos realizar acciones tales como notificaciones push, almacenamiento local y ejecución offline entre muchas otras. ¡Esperamos que os guste el episodio y como siempre nos vemos al final! ¿Queréis participar? ¿Queréis participar y ayudarnos a decidir que grabar en WeCodeSign y proponer invitad@s? Aquí podéis participar en WeCodeSign. Recomendaciones Preguntas rápidas: José Manuel Quién me ha inspirado: Alberto Quién me ha inspirado: Davide Mendolia Quién me ha inspirado: Felipe Ribeiro Quién me ha inspirado: Steve Souders Quién me ha inspirado: Nicholas C. Zakas Quién me ha inspirado: Addy Osmani Quién me ha inspirado: Dan Abramov Quién me ha inspirado: Stoyan Stefanov Recomiéndanos un recurso: Frontend Focus Recomiéndanos un recurso: JavaScript Weekly Recomiéndanos un recurso: Chrome and Web at Google I/O 2017 Recomiéndanos un recurso: JS Conf Recomiéndanos un recurso: CSS-Tricks Recomiéndanos un recurso: Smashing Magazine Recomiéndanos un recurso: High Performance Browser Networking Recomiéndanos a un invitado o invitada: Jaume Sanchez Elias ¿Qué tema te gustaría que tratásemos?: Web Performance Contacta con: José Manuel Twitter de José Manuel Web de José Manuel Links del programa Hilo sobre cómo aparecieron las PWA, por Alex Russell Progressive Web Apps: Great Experiences Everywhere (Google I/O '17) Production Progressive Web Apps With JavaScript Frameworks (Google I/O '17) PWA Directory Progressive Web Apps La guía sin conexión by Jake Archibald The Service Worker Cookbook Service Worker Tools Service Worker Pre Cache Tu primera Progressive Web App by Pete LaPage Building Progressive Web Apps A big list of progressive web app tips and tricks The State of Progressive Web Apps Production Progressive Web Apps with JavaScript Frameworks Qué son las Aplicaciones Web Progresivas o "Progressive Web Apps" Progressive web apps PWA: Para Webs Asombrosas Recomendaciones de Ignacio Progressive Web App questions Progressive Web App Checklist The PWA Resource list Lighthouse Patrocinadores Fictizia.com Contacta con Ignacio Web de WeCodeSign Twitter de WeCodeSign eMail de WeCodeSign Web de Ignacio Villanueva Twitter de Ignacio Villanueva