POPULARITY
2 episodes with ie8
2 episodes with ie8
2 episodes with ie8
2 episodes with ie8
5 episodes with ie8
2 episodes with ie8
关于电影《金属之声》Sound of Metal (2019)，我们几个展开了关于听觉、听觉障碍（失聪，或像节目里一样，不太尊重地说「聋」）与听力保护的讨论。这也是对我们2015年第14期节目《声波老中医》时隔六年的call back。本期节目由「若饭」赞助播出。若饭是一个总是加班熬夜的程序员创立的硬核代餐品牌，浓缩了20种人体必需营养，无需冲泡，开盖即饮、轻享一餐。6年时间，若饭累积了近15万复购用户。这一期节目，我们探讨了人类身体的一种线性的功能退行，这对于每一个人，都是必须面对的宿命般的问题。而我台第一次广告，就恰好得到了一个和身体哲学与生活方式紧密相关的品牌支持，非常荣幸。关注微信公众号若饭，回复「声波飞行员」，新用户立享8折优惠。 如果你喜欢我们的节目，欢迎在你收听的平台留言参与互动；转发与分享是对我们最大的支持。如果你想用最直接的方法支持「声波飞行员」，可以在「爱发电」搜索并为我们打赏，增加它继续飞行下去的动力，谢谢。[00:00:00] 来自未来食物品牌「若饭」的第一条广告；BGM#0. Yoko Kanno - The Egg and I[00:03:23] BGM#1. The Rolling Stones - Sympathy for the Devil[00:05:27] 断更抱歉；关于若饭、soylent 与未来食物；[00:09:28] der糕和她的EOZ；孟获的新朋友Soundcore Liberty 2 Pro；从Hear ID 测试聊到电影《金属之声》；[00:16:55] 关于听力损伤在影视作品的表达；各人看高响度现场音乐的经历；[00:31:46] 人物主观的听障如何在音轨上进行处理；TestV 以及类似的降噪产品评测制作方式解析；[00:35:44] 拉一拉与听障相关的片单；Russell Peters 对聋子的恶意笑话；听障社区的共同体理念；[00:43:37] 如果你突然失聪会怎么样；阿赖耶识快速通道；不断退行的听力造成的焦虑与自我审视；[01:05:26] 造成听力退化的环境；身边的听障人士；[01:14:40] BGM#2. AC/DC - You Shook Me All Night Long[01:17:20] 听力保护科普的误区：医师「使用耳机不超过2小时」类似言论的偏颇之处；耳机作为听力保护的工具；枕头下的舒曼波发生器；[01:27:26] 睡眠耳塞、白噪音和工作BGM；第14期擎天老法师的经历，孟获心疼IE8；[01:47:20] 如果我们聋了，会作何选择；听障共同体和修房子；[01:56:07] BGM#3. 細野晴臣 - Paraiso[01:56:31] 结束语#飞行员：Der糕 / 地下丝贼 / 包雪龙 / 孟获
关于电影《金属之声》Sound of Metal (2019)，我们几个展开了关于听觉、听觉障碍（失聪，或像节目里一样，不太尊重地说「聋」）与听力保护的讨论。这也是对我们2015年第14期节目《声波老中医》时隔六年的call back。本期节目由「若饭」赞助播出。若饭是一个总是加班熬夜的程序员创立的硬核代餐品牌，浓缩了20种人体必需营养，无需冲泡，开盖即饮、轻享一餐。6年时间，若饭累积了近15万复购用户。这一期节目，我们探讨了人类身体的一种线性的功能退行，这对于每一个人，都是必须面对的宿命般的问题。而我台第一次广告，就恰好得到了一个和身体哲学与生活方式紧密相关的品牌支持，非常荣幸。关注微信公众号若饭，回复「声波飞行员」，新用户立享8折优惠。 如果你喜欢我们的节目，欢迎在你收听的平台留言参与互动；转发与分享是对我们最大的支持。如果你想用最直接的方法支持「声波飞行员」，可以在「爱发电」搜索并为我们打赏，增加它继续飞行下去的动力，谢谢。[00:00:00] 来自未来食物品牌「若饭」的第一条广告；BGM#0. Yoko Kanno - The Egg and I[00:03:23] BGM#1. The Rolling Stones - Sympathy for the Devil[00:05:27] 断更抱歉；关于若饭、soylent 与未来食物；[00:09:28] der糕和她的EOZ；孟获的新朋友Soundcore Liberty 2 Pro；从Hear ID 测试聊到电影《金属之声》；[00:16:55] 关于听力损伤在影视作品的表达；各人看高响度现场音乐的经历；[00:31:46] 人物主观的听障如何在音轨上进行处理；TestV 以及类似的降噪产品评测制作方式解析；[00:35:44] 拉一拉与听障相关的片单；Russell Peters 对聋子的恶意笑话；听障社区的共同体理念；[00:43:37] 如果你突然失聪会怎么样；阿赖耶识快速通道；不断退行的听力造成的焦虑与自我审视；[01:05:26] 造成听力退化的环境；身边的听障人士；[01:14:40] BGM#2. AC/DC - You Shook Me All Night Long[01:17:20] 听力保护科普的误区：医师「使用耳机不超过2小时」类似言论的偏颇之处；耳机作为听力保护的工具；枕头下的舒曼波发生器；[01:27:26] 睡眠耳塞、白噪音和工作BGM；第14期擎天老法师的经历，孟获心疼IE8；[01:47:20] 如果我们聋了，会作何选择；听障共同体和修房子；[01:56:07] BGM#3. 細野晴臣 - Paraiso[01:56:31] 结束语#飞行员：Der糕 / 地下丝贼 / 包雪龙 / 孟获
Mike North is the Ember guy at Frontend Masters and LinkedIn’s web developer trainer. Today the panel is talking about the upcoming Ember update, which Mike calls a total reinvention of the way you build with Ember. Finally, they are letting go of the cruft and stuff they had to hold on to in order to support IE8 and using modern interface The panel talks about some of the issues with IE8, and agree that the reason Ember felt its age because it was built for IE8. Ember 314 is moving from the past into the present, a sleek modern way to build apps. Mike talks about how easy the new Ember is to use. Mike talks about the excitement in the Ember community because the new build is focused on stability and seamlessness. Charles talks about his less seamless experience with the Angular community. For context, Mike North’s first frontend masters course was recorded in 2014, and he’s only had to change two lines of code. Ember is the only framework that has managed to go all the way from IE7/IE8 to today without a major gap,breaks, or rewrites. They transition to talking about what keeps Ember going. There is an effort to make sure things are decentralized and not tied to any specific company, although Apple, Netflix, Nasa, and PlaysStation all use it. LinkedIn has also been hiring Ember core member to continue working on it, and sponsoring open source work. Next, they talk about how Ember works with TypeScript. You can install an Ember add on with one terminal command that will enable TypeScript in an Ember app.There are some issues that could cause misalignment with JavaScript and TypeScript, but Ember has designed things around it. MIke talks about the major change in the learning curve with using Ember and how far Vanilla JS will take you. Overall, it is a lot more approachable than it used to be. They move on to talk about the availability of third party solutions with Ember. Mike assures them that Ember has add-ons, and parts of the framework are opening up to allow experimentation with components. There are lots of ways to make Ember your own without running the risk of diverging, giving more flexibility than ever while maintaining the happy path. Testing within Ember is also a priority, and they want the code to be as readable as possible. The last topic discussed in this show is the importance of developer education. LinkedIn looks at employment numbers and the rate at which new jobs open, and software engineering is growing like crazy and will likely continue to grow.The rate at which new people are graduating with computer science and programming degrees, as well as those from unconventional backgrounds, is not keeping up with the number of jobs. This means that there will be fewer senior people spread across bigger groups of developers with less experience. The panel agrees that it is the responsibility of people who have been around or learned something period to pass on the knowledge because the more knowledge is passed on, the more stable things will remain as seniors become more scarce. It is also important for companies to level up junior developers. They conclude by talking about tools available for people who want to learn more about Ember Octane, and Mike makes an open request to the JS community. Panelists Charles Max Wood Steve Emmerich Chris Ferdinandi Aimee Knight AJ O’Neal Christopher Buecheler With special guest: Mike North Sponsors React Native Radio Sentry use the code “devchat” for 2 months free on Sentry’s small plan Dev Ed Podcast Links Ember Frontend Masters IE8 Ember Octane Sprout Core TypeScript ES6 Lodash Mocha Backstop.js Semver https://twitter.com/thefalken/status/1177483501777473537 Follow DevChatTV on Facebook and Twitter Picks Chris Ferdinandi: Vanilla JS Academy, get 30% off with code ‘jsjabber’ leanweb.dev Steve Emmerich: 123 Magic RGDK Aimee Knight: Recursion blog post Wholesome Provisions Protein Cereal AJ O’Neal: Carby V2 by Insurrection Industries GameCube Mods Charles Max Wood: Nikon D5600 Rode Newsshooter Viltrox light panel Quest Nutrition pumpkin bars Christopher Buecheler: Tool’s Fear Inoculum on Apple Music, Spotify, and Google Play Mike North: Github Universe Github Tracer Bench Follow Mike @mike-north on Github, @northm on LinkedIn, and @michaellnorth on Twitter
Mike North is the Ember guy at Frontend Masters and LinkedIn’s web developer trainer. Today the panel is talking about the upcoming Ember update, which Mike calls a total reinvention of the way you build with Ember. Finally, they are letting go of the cruft and stuff they had to hold on to in order to support IE8 and using modern interface The panel talks about some of the issues with IE8, and agree that the reason Ember felt its age because it was built for IE8. Ember 314 is moving from the past into the present, a sleek modern way to build apps. Mike talks about how easy the new Ember is to use. Mike talks about the excitement in the Ember community because the new build is focused on stability and seamlessness. Charles talks about his less seamless experience with the Angular community. For context, Mike North’s first frontend masters course was recorded in 2014, and he’s only had to change two lines of code. Ember is the only framework that has managed to go all the way from IE7/IE8 to today without a major gap,breaks, or rewrites. They transition to talking about what keeps Ember going. There is an effort to make sure things are decentralized and not tied to any specific company, although Apple, Netflix, Nasa, and PlaysStation all use it. LinkedIn has also been hiring Ember core member to continue working on it, and sponsoring open source work. Next, they talk about how Ember works with TypeScript. You can install an Ember add on with one terminal command that will enable TypeScript in an Ember app.There are some issues that could cause misalignment with JavaScript and TypeScript, but Ember has designed things around it. MIke talks about the major change in the learning curve with using Ember and how far Vanilla JS will take you. Overall, it is a lot more approachable than it used to be. They move on to talk about the availability of third party solutions with Ember. Mike assures them that Ember has add-ons, and parts of the framework are opening up to allow experimentation with components. There are lots of ways to make Ember your own without running the risk of diverging, giving more flexibility than ever while maintaining the happy path. Testing within Ember is also a priority, and they want the code to be as readable as possible. The last topic discussed in this show is the importance of developer education. LinkedIn looks at employment numbers and the rate at which new jobs open, and software engineering is growing like crazy and will likely continue to grow.The rate at which new people are graduating with computer science and programming degrees, as well as those from unconventional backgrounds, is not keeping up with the number of jobs. This means that there will be fewer senior people spread across bigger groups of developers with less experience. The panel agrees that it is the responsibility of people who have been around or learned something period to pass on the knowledge because the more knowledge is passed on, the more stable things will remain as seniors become more scarce. It is also important for companies to level up junior developers. They conclude by talking about tools available for people who want to learn more about Ember Octane, and Mike makes an open request to the JS community. Panelists Charles Max Wood Steve Emmerich Chris Ferdinandi Aimee Knight AJ O’Neal Christopher Buecheler With special guest: Mike North Sponsors React Native Radio Sentry use the code “devchat” for 2 months free on Sentry’s small plan Dev Ed Podcast Links Ember Frontend Masters IE8 Ember Octane Sprout Core TypeScript ES6 Lodash Mocha Backstop.js Semver https://twitter.com/thefalken/status/1177483501777473537 Follow DevChatTV on Facebook and Twitter Picks Chris Ferdinandi: Vanilla JS Academy, get 30% off with code ‘jsjabber’ leanweb.dev Steve Emmerich: 123 Magic RGDK Aimee Knight: Recursion blog post Wholesome Provisions Protein Cereal AJ O’Neal: Carby V2 by Insurrection Industries GameCube Mods Charles Max Wood: Nikon D5600 Rode Newsshooter Viltrox light panel Quest Nutrition pumpkin bars Christopher Buecheler: Tool’s Fear Inoculum on Apple Music, Spotify, and Google Play Mike North: Github Universe Github Tracer Bench Follow Mike @mike-north on Github, @northm on LinkedIn, and @michaellnorth on Twitter
Mike North is the Ember guy at Frontend Masters and LinkedIn’s web developer trainer. Today the panel is talking about the upcoming Ember update, which Mike calls a total reinvention of the way you build with Ember. Finally, they are letting go of the cruft and stuff they had to hold on to in order to support IE8 and using modern interface The panel talks about some of the issues with IE8, and agree that the reason Ember felt its age because it was built for IE8. Ember 314 is moving from the past into the present, a sleek modern way to build apps. Mike talks about how easy the new Ember is to use. Mike talks about the excitement in the Ember community because the new build is focused on stability and seamlessness. Charles talks about his less seamless experience with the Angular community. For context, Mike North’s first frontend masters course was recorded in 2014, and he’s only had to change two lines of code. Ember is the only framework that has managed to go all the way from IE7/IE8 to today without a major gap,breaks, or rewrites. They transition to talking about what keeps Ember going. There is an effort to make sure things are decentralized and not tied to any specific company, although Apple, Netflix, Nasa, and PlaysStation all use it. LinkedIn has also been hiring Ember core member to continue working on it, and sponsoring open source work. Next, they talk about how Ember works with TypeScript. You can install an Ember add on with one terminal command that will enable TypeScript in an Ember app.There are some issues that could cause misalignment with JavaScript and TypeScript, but Ember has designed things around it. MIke talks about the major change in the learning curve with using Ember and how far Vanilla JS will take you. Overall, it is a lot more approachable than it used to be. They move on to talk about the availability of third party solutions with Ember. Mike assures them that Ember has add-ons, and parts of the framework are opening up to allow experimentation with components. There are lots of ways to make Ember your own without running the risk of diverging, giving more flexibility than ever while maintaining the happy path. Testing within Ember is also a priority, and they want the code to be as readable as possible. The last topic discussed in this show is the importance of developer education. LinkedIn looks at employment numbers and the rate at which new jobs open, and software engineering is growing like crazy and will likely continue to grow.The rate at which new people are graduating with computer science and programming degrees, as well as those from unconventional backgrounds, is not keeping up with the number of jobs. This means that there will be fewer senior people spread across bigger groups of developers with less experience. The panel agrees that it is the responsibility of people who have been around or learned something period to pass on the knowledge because the more knowledge is passed on, the more stable things will remain as seniors become more scarce. It is also important for companies to level up junior developers. They conclude by talking about tools available for people who want to learn more about Ember Octane, and Mike makes an open request to the JS community. Panelists Charles Max Wood Steve Emmerich Chris Ferdinandi Aimee Knight AJ O’Neal Christopher Buecheler With special guest: Mike North Sponsors React Native Radio Sentry use the code “devchat” for 2 months free on Sentry’s small plan Dev Ed Podcast Links Ember Frontend Masters IE8 Ember Octane Sprout Core TypeScript ES6 Lodash Mocha Backstop.js Semver https://twitter.com/thefalken/status/1177483501777473537 Follow DevChatTV on Facebook and Twitter Picks Chris Ferdinandi: Vanilla JS Academy, get 30% off with code ‘jsjabber’ leanweb.dev Steve Emmerich: 123 Magic RGDK Aimee Knight: Recursion blog post Wholesome Provisions Protein Cereal AJ O’Neal: Carby V2 by Insurrection Industries GameCube Mods Charles Max Wood: Nikon D5600 Rode Newsshooter Viltrox light panel Quest Nutrition pumpkin bars Christopher Buecheler: Tool’s Fear Inoculum on Apple Music, Spotify, and Google Play Mike North: Github Universe Github Tracer Bench Follow Mike @mike-north on Github, @northm on LinkedIn, and @michaellnorth on Twitter
V úplně první epizodě s @machal (https://twitter.com/machal) probíráme úvodní kroky u nového projektu z hlediska kódování, výhody a nevýhody HTML5 tagů, co znamená Mobile-First pro front-end a nakonec zjednodušení tvorby stránek pro začátečníky. Nevyhnutelně si několikrát připomeneme různé problémy s IE8. --- Send in a voice message: https://anchor.fm/bruskodu/message
Mike North: @michaellnorth | mike.works Show Notes: 00:51 - Transitioning from CTO to Independent Trainer 03:37 - Customizing Content and Developing Curriculum 06:37 - Bringing a Developer Into the JavaScript Ecosystem 12:47 - Training Developers with Non-Traditional Backgrounds 16:56 - Keeping Up with “Fifth Gear” 19:27 - Developing Frontend Masters Courses 22:40 - “Progressive Web Apps” 34:37 - Web Security Resources: LinkedIn's REACH Program IndexedDB Transcript: CHARLES: Hello, everybody and welcome to The Frontside Podcast, Episode 79. My name is Charles Lowell, a developer at the Frontside and your podcast host-in-training. With me today is Elrick, also at the Frontside. Hello, Elrick. ELRICK: Hey, what's going on? CHARLES: Today, we are going to be talking with Mike North, who is doing all kinds of interesting stuff as per the usual so we'll jump right in. Hey, Mike. MIKE: How is it going? I'm glad to be here. CHARLES: Last time that I saw you, I think it was about a year ago at the Wicked Good Ember Conf and we were standing on the beach, drinking scotch and talking about Fastboot but you were doing something completely and totally different then than you are now so I was wondering, we were talking the conversation before we started rolling, that your role nowadays is independent consultant and personal dev trainer. I was wondering if you talk a little bit about that move from the CTO role that you're playing at your old company to kind of moving into that independent trainer, like why and how. MIKE: Yeah, I do remember talking about Fastboot at Wicked Good Ember. It feels like things have moved quite a bit since then. I have always loved teaching developers. When I've been a team lead, it's the favorite part of my job just because I get profound satisfaction out of helping people get over these hurdles that most of the time took me a much longer time with blog posts and podcasts and incomplete examples and libraries that were out of date and Stack Overflow with half answers. I've decided to dedicate myself to trying to make it easier for people in an increasingly complex web development world to wrap their head around everything. While I was a tech lead or a CTO, I always had to split my focus between helping developers grow and something else. Oftentimes, that something else was where the deadlines were and the time pressure was. It felt a little bit like I was driving a car that only had first and fifth gear where you're like on the bleeding edge of open source and what was the latest commit to master and [inaudible]. Then like, "Oh, let's be extremely patient with this person. They've never seen promises before because they came from another programming language. Let's help them digest this at their own pace." It's this slow and patient process of building up from the fundamentals and then the bleeding edge is like, "Let's use Babel Stage 0." It was very hard for those two aspects to exist at the same time in myself so I decided I'm just going for the training side. That's really all I do these days. CHARLES: It was so, but now would you qualify that as the first gear or the fifth gear? MIKE: That's the first gear. It gets you off the ground. It takes you from stop and gets you moving and then you have to develop your own expertise beyond that. But I like to think I'm developing a really, really excellent first gear. Today for example, I'm converting a bunch of Python developers at LinkedIn who are basically the ops team. I'm teaching them Ember and JavaScript at the same time through a series of about 20 exercises over three days. That process is many weeks long without assistance so this is like, "Let's get rolling much more efficiently and quickly," than via DIY approach. CHARLES: Now, do you find you have to custom-tailor for the environment or the developers moving from like someone coming from, say C# would have a different experience than someone coming from Python? MIKE: Absolutely. When I have my material, I have sections that I can drop. If you are a C# developer, I do not have to explain conceptually what 'async' and 'await' mean. You've been working with that for a while. I probably throw up a little example in C# and then the equivalent in JavaScript to sort of create a bridge from your existing expertise into the JavaScript world. Another one -- this is very true -- is teaching Ruby developers how to use Elixir. You don't have to say, "This is a router. We have controllers. There are actions and controllers." There are so many parallels that really it's more useful to help, rather than teach things from scratch to create connections back to the expertise they already have so they're not starting from zero and they can say like, "In the Ruby world, I would think of doing XYZ." Now, I have a map in between that and this new thing. CHARLES: Obviously, there's a lot, a lot, a lot of languages and environments that you could transition to, probably more than matches your own personal experience, in doing that frontline development. What kind of research do you have to do to develop a curriculum for, say someone coming from Clojure or someone coming from Scala or something like that? Maybe that never happens. MIKE: I have a pretty, pretty broad background. My entry into programming was a subset of C and then I graduated to C++ and Java and Ruby and I used to do ASP stuff. I've written iOS apps. I feel like I have enough of a foothold into various areas like I know one JVM language. That is usually enough. If you're running a lot of Clojure, I can at least speak Java to you because odds are, you're working with that and you're seeing that and you know it. Oftentimes, I have what I need. There are situations where I can borrow something in a very cursory level. Not to rip on Scala but I have not found it valuable to make connections to that particular language for clarity and [inaudible] but I have used Haskell before and I'm not a Haskell developer but it is a pure functional language. When trying to help people understand how is this different, then the JavaScript got them running where the Ruby ends up running. It's useful to use something like that. It's a very small language, very simple and you can wrap your head around the basics. ELRICK: What are some of the particular challenges that you face when bringing in a developer outside of the JavaScript ecosystem into JavaScript since JavaScript is kind of the Wild West that you can do everything in JavaScript? What are some of the challenges you face in bringing in a new developer from Python or C or whatever that may be? MIKE: You put it very well. It is definitely the Wild West. You can do anything if you have enough [inaudible] yourself and enough power to get serious stuff done. Really, it's like the explosion in number of choices and tools, the explosion of complexity. I learned JavaScript when it was something that you sprinkle on top of your Rails app for a little interactivity, a little animation on a screen or something like that. I was lucky to learn it at that point in time when that was the norm because I've been able to gradually accumulate for more than ten years now. The tooling like using Grunt, using Golf, using Brunch and then stepping up to other more sophisticated build tools. I learned those one by one in the context of real projects. Now, it's like the mountain is so high, people don't know where to start so that's a big challenge for developers. To throw them into a meaningful project like if you asked a mean JavaScript developer, not angry but the average JavaScript developer, they're like maybe -- CHARLES: I should dare to say that the average JavaScript developer is mean. MIKE: A little bit and probably maybe [inaudible] with me as well, depending on [inaudible]. But they're going to spin up some project with webpack and Babel and all of these tools. If that's your first exposure to the language and to working with the language, you're operating in an environment that you don't understand. Research shows that is the less effective option there to slowly building things up over time. I spend a lot of time going back to the basics and making sure we're not working with promises until we've explicitly focused on them, chained a couple together, managed errors and then now, we can work with Fetch. We're not going to jump into that and throw ourselves into this deep end of the pool. We want to incrementally build up skills. It takes a little bit longer but when you have that understanding as you're learning, you get a lot more out of it because anything that you can't get a grip on to as you learn it, it sort of just evaporates into thin air and don't retain that, even if you kind of fill in those holes later. CHARLES: Yeah, it could be so hard too. Actually, this has been an experience that I've been having, I would say almost for the past two years, as the tools advance, not only you are starting from a place of not understanding but the tools themselves do not teach you. I've had two moments where I got really mad. One actually was on an Ember project and one was a project using webpack but it was the same fundamental problem where in one I was actually working with someone who was very new to JavaScript and an error happens and the stack trace was some just big bundled garbage that gave no insight at all. MIKE: In vendor.js. CHARLES: Yes, in vendor.js or in bundle JS. It was like, "How is anyone supposed to learn?" The most fundamental thing about working with Ruby or working with Node or working with anything is you get a stack trace. MIKE: Debugging is really hard. I think it just takes a little time reaching out to people who are experiencing the Stockholm Syndrome like most of the time, JavaScript developer. We all are working with Ember CLI and webpack. I'm not ripping on these tools but we're used to that complexity in our lives. When we see that stack trace, we're like, "Oh, well. I probably need a source map. I'll make sure that that's there. It's natural that I'm debugging a file that the browser is not really seeing like it mapped back to my source code debugging." This is natural to us. But if you put that in front of a developer who hasn't been living under those circumstances, the number of times they raised their hand is like, "What the hell is this?" It is just amazing and it really helps. I've reset my expectations to what a normal programming experience should be and JavaScript does not provide that today. That is really challenging to keep someone in the midst of all that. CHARLES: I feel like it's hard and do you think we'll ever achieve that? Or is it just going to be a constant hamster wheel of progress versus the tooling to educate what progress has been made or to communicate what progress has been made? MIKE: I think the tooling is fine but it's just that we have a gap in terms of learning experience. We just need really -- I'm not voluntary here because I've got a ridiculous backlog -- a couple long tail horses working with vanilla JavaScript, rendering some stuff on the screen, maybe a course of React but no JSX yet, just create component. A couple of things to fill in a gap between where maybe code school leaves off and where you are expected to be by the time you start interviewing for a spot as frontend developer on a team but there's a huge chasm right now. There's the intro guides and then there's professional life and trying to bridge the gap between those is ridiculously a challenge right now due to the huge ramp up of complexity from like, "Let's do some stuff in the console," to, "Running transpile JSX code with async [inaudible]. We've got regenerator in there to polyfill generator functions." There's so much in your average JavaScript at these days. CHARLES: Your work that you're doing at LinkedIn, part of it is trying to bring and train developers who come from more nontraditional backgrounds, including a lot of things like boot camps. What is your experience of their experience coming in? Are boot camps doing the right thing? Are they teaching the right things? Are they trying to kind of parachute them on top of that mountain? Or do you find that they're just at the base camp, so to speak? Because it sounds like your approach is like you've got to really start from fundamentals so that you can understand the layers of complexity if you're going to, someday stand on them. MIKE: I think a lot of the boot camps are doing an excellent job. These days, the employees we have at LinkedIn who come from boot camps, I would bet on them against your average MIT grad every time, just because their education is so practical. It's amazing that in the world of computer science, the stuff that you're taught in school is a little bit farther removed than one would expect, compared to the stuff that we do every day in our jobs -- building real apps. I do not need to know in my day-to-day work at LinkedIn how an operating system works or how to build a device driver. This is a little bit too fundamental. It's the wrong abstraction for practical everyday work for most people. Where in these boot camps, they focus completely on the practical. In fact, I've been fortunate enough to get involved with the REACH program here at LinkedIn, where we hire explicitly people from nontraditional backgrounds like boot camps. They're not all from boot camps but many of them are. We just hired 30 of them in March. The pilot program, I think we've hired two or three in our New York office and it just went really well. It started like, "Let's double down and double down again and double that again." This time, we're doing 30 and I expect there will be a new round next year where we poll even more. The idea is we take these REACH candidates and pair them with a mentor engineer for six months. At the end of that six months, we had to make a decision as to like this person at the level we expect of an entry level software engineering hire. From what I've seen, we're doing really well at preparing these folks and they're unbelievably valuable to the teams that they've been placed in. ELRICK: That's amazing. That's very interesting. Is there a standardized curriculum thing that each mentor will follow to get this person after they entered his REACH program and then ramp them up or is it like each person just goes and looks at what the person knows and then ramps them up accordingly. MIKE: I'd say, it's a mix of both. We have a set of technical trainings for them or we'll have a testing expert from within the company and teach a little testing seminar to them. There's that standardized curriculum there. But the nature of being taught by boot camp or teaching yourself is that you're going to have holes in your knowledge and it's not often predictable where those holes will be. That's why we make sure we do this mentorship very explicitly and over a long period of time so that if it turns out that you never learned about how to work with tree-data structures. That was not part of the go-no/go decision that brought you on but we should probably, at least get you there. At least to the point where if you're traversing a down tree and you're like parent and child, what is this, what do you mean by leaf-level node. This is stuff that is actually meaningful for web developer in some cases. CHARLES: In the context of the work that you're doing with the REACH program but also touching on something that we talked about at the beginning about the first gear and the fifth gear, part of generating a curriculum is still being in contact with what's up in the fifth gear right because ultimately, what you're trying to do is you're working with people who are in first gear or looking to get a smooth transition in the first gear but at the same time, you want to set them up and you want to be in contact for what's in fifth gear now is going to be first gear in five years. How do you feed that in? MIKE: I'm fortunate to have a great team that I work with here. This group that I roll up to in LinkedIn, they're experts and you probably know of like Chris Epstein and Tom Dale and Steph Petter. A 15-minute coffee break with one of these people is enough to keep [inaudible]. Sometimes, it's a little bit like drinking from a fire hose because it's like I spend an hour with a student trying to help them understand like, "This is why a Promise is useful. Here is the callback equivalent," and then now, "Let's dive in to Glimmer. Why this track annotation is the right way to go for automatic updating." It sends me for little bit of a loop sometimes but it is definitely keeping me up to date. The other factor, of course is when you've been doing this for a while. History sort of repeats itself so a lot of the patterns that we're seeing today, I've seen somewhere else. I was working with code splitting when I was writing Dojo JavaScript code years and years ago. I was defining my module layers in a very explicit way. I had to do that. I didn't have done a webpack that would figure out, put these splits are. But I have that experience to look back to and for that reason, it is not often that an entirely new concept comes along. Oftentimes, they're like amazing refinements on things that how to smell like stuff that we've used before in the software engineering world. CHARLES: Yeah or here's something that has never been used, is very prevalent in these other context which we're going to apply here. MIKE: Exactly. CHARLES: And like, "Oh, my goodness. It's a perfect solution." In addition to the work that you're doing with LinkedIn and developing those training curricula and stuff, you're also doing some work for Frontend Masters in an area that's very exciting, I think to me. I'm sure it's exciting to you because you decided to throw a whole lot of time into developing a course for it. That's in the development of progressive web apps, which for me has been like this thing that I'm so curious about but I'm like a kitten playing with a little yarn ball. I want to dive in but I'm just going to tap it with my paws right now. MIKE: Yeah, it's a really interesting area and I think that even if you're not using progressive web technologies today, it's one of these things that sort of reinvigorates your energy for JavaScript's future and what may be possible soon. Steve and I have put together this amazing progressive web app course, which has I think like 18 short examples of iteratively building up a grocery shopping app. If you've used InstaCard or something like that, we start out with app already built and it's like a single-page app as doing everything that you would expect. After a few of the exercises, it works offline. After a few more, you can add stuff to the card and background sync, push it to the API when you come back online. We get deep, deep, deep into service workers. That's one of the areas that my work at LinkedIn and my teaching with Frontend Masters overlaps really well because I've been heavily involved in creating our service worker for LinkedIn.com. I may be able to take some of what we've learned here and disseminate it a little bit so that, hopefully fewer people have to learn the hard way. It's best to keep things simple at first and add on functionality. I'm about to cross like the [inaudible]. This is my favorite just because the example turned out to fit so well and in particular, on Frontend Masters, I think Steve and I have had contrasting teaching styles but they complement each other so well because I'm like the 'melt people's brains' instructor. I love to throw people exercises that are like 120% of what they can do and it's going to hurt, just like when you're lifting weights at the gym, like you're going to beg for mercy but we're going to make you strong. Then Steve, just listening to him, even with I am in the classroom and he is teaching me Electron. He's so energizing and he's really funny too but not in an overtly cracking jokes kind of way. He's just so fun when he teaches. I think it is a really good combination just because things lined up just by luck and through hard work and just the right way out of a couple of important areas. CHARLES: Now, just for people who might not be familiar with the term progressive web apps, what does it encompass? Do people actually call them PWAs? MIKE: No. I'm going to start, though. I like that. That carries very well over a video chat or something. Nobody knows how to spell that: P-U-A? P-W-U-A? It is a rejection of the old idea that in order to take advantage of some web technology, it has to be supported in all of the browsers that we need to support. The idea here is to hold as a core tenet of our design practices, the idea of progressive enhancement, meaning we serve up a basic experience and where we can take on these superhero features, like the ability to work offline, the ability to receive push notifications, we go ahead and do so. If your browser doesn't support this, that's unfortunate. No big deal. You still get a good experience. But if you're using a very recent version of Chrome or Safari or you have a new Android device, these browsers can take advantage of sophisticated metadata or sped up a background process that can serve up data to your app and your app doesn't even know that there's something between it and the API. That is the idea of progressive web apps -- apps that become superheroes where possible and they still work and provide a great basic experience for antiquated browsers like IE8 and Safari. CHARLES: The idea theoretically, you could work without any JavaScript or whatsoever. What's the ground floor there? MIKE: That is ideal. I think server-side rendering, which is what you're talking about there, even if JavaScript is not working, just HTML and CSS will provide a basic experience. That's great but that's not a modern browser technology thing. If you have JavaScript turned off in today's Chrome, like Chrome 60, versus IE9, both of them working with them without JavaScript. What we're really talking about here is app-like characteristics, where we are pushing web technology to the point where you will swear that this came from an App Store. It's on your home screen. It's running in the full screen. You're getting push notifications. It works offline and you can store a large amount of structured data locally on the device. All of the stuff sounds like the list of reasons to reach for native mobile technology because the mobile web is not good enough. But in fact, it has a feature set of this family of progressive web technologies. It's really like a web app that is so good and so modern that it feels and looks just like a native mobile app. CHARLES: That sounds so hard to do right. MIKE: Well, it is now, just because what we have to work with can be thought of it like a basket of ingredients, rather than a solution that we drop in. But over time, as more people start working with these ingredients, I think we're going to see a lot of consensus around the best patterns to use and boilerplate code will fall away as we can identify that the set is in fact commonly needed and not a beautiful and unique snowflake. CHARLES: Because it seems like the thing that I always struggle with is not wanting to put the critical eggs in the basket of a superhero feature or have you being able to provide an alternative if the superhero feature doesn't exist. Some features, if you just don't have it, that's fine. You can turn it on if the capabilities available but certain features are very critical to the functioning of your application. I'm casting about for an example and I'm not finding one immediately but -- MIKE: Offline is a great one. That fits pretty neatly. If you're using an older browser or if you're using Safari, which by the way, I should stop ripping on Safari. For the listeners out there, we saw a commit lend in webkit, where service for APIs are beginning to be stubbed out. No longer do we have to look at length. Service worker, enthusiasm and Safari has got it in the five-year plan. There was motion last week. We haven't seen motion in ages so thank you Safari Team. Thank you. Keep up the good work. CHARLES: Is there a discipline of Safari-ologists who monitor the movement of Safari to bring this news? MIKE: Of course, we monitor it because right now, Chrome and Firefox, they are pretty much hopeful in terms of supporting this modern stuff. Opera supports this modern stuff. Samsung's fork of Chromes support this modern stuff. Especially when we think about the mobile web, you got to worry about Android and you got to worry about iOS Safari and right now, like we've talked about these progressive web apps, you don't get that superhero experience on an iPhone or an iPad. Once we crossed that threshold, this is going to have a breakaway level of adoption because there are no more excuses. Essentially, for a mobile web experience, you can send push notifications to the user. That is huge. That is probably at the top of the list for why some people use native apps, instead of mobile web. The more we can do that, the more we can make it so that a great LinkedIn experience can be delivered to your phone without having to install a binary. I just have to update Facebook the other day and it was over 100 megabytes. Why do we need to do that? You should be able to make it work with less. I'm sure that there's some great stuff in there. Apparently, Snapchat filters are popular but I don't need this. Can we code split that away or something because I don't want to have to download that? I can't even download it on the cell network because it's over 100 megabytes. It's really exciting to see the web start to compete with this heavy mobile experience because now I think is ready. CHARLES: Now, when you talk about push notifications, you're talking about being able to send things to my lock screen. MIKE: To your lock screen while the browser is not on the foreground, while the app is not open. Essentially, you're installing a lightweight process that runs in the background. It receives events that originate from your server and the user can tap on them and then your little lightweight worker process in the background decides what to do when that tap happens, like open up the app, take them to this URL or something like that. That is a game changer. That's huge. Or background sync like the user added some items to their cart and then they lock their phone and now, their plane has landed. That's why they were offline and they get back on the internet and without them having to touch their phone, now we can push that data to the server and everything's in sync, rather than like, "Please revisit your app. We need to run some JavaScript code to flush IndexedDB or API." It still feels like a hack at that point. This is a fluid experience. ELRICK: Wow. This is exciting for me as I don't have any more space on my cellphone, thanks to all the apps that I have to install to do various things on the web. MIKE: You're not alone. CHARLES: Yeah, it's crazy and just the amount of code sharing that you can have, I guess that doesn't happen much these days on the web where you've got these popular libraries out on CDNs so that the chances are that you've got jQuery 1.2.1 on your cache, you've got 16 versions of jQuery so most of your web applications don't have to do that. I guess we kind of do the equivalent of statically linking everything. MIKE: There is a benefit near that where we have imperative code managing our cache, instead of just relying on the HTTP cache or app cache, if you have a vendor.js file that is not changing over six months, there is no reason you should be re-downloading that every time you deploy your app or letting the browser evict that, just because memory pressure is high from Google image search results or something like that. We really don't have much control over it. But with a service worker, we can say, "Hold on to this," or maybe like prefetch the next version of the app so that we're going to show you the old version now but the next time you refresh, here's the new version available instantly. It's downloaded in the background and it's like click to update your version, like it's already here waiting for you. That's huge. That's amazing. CHARLES: That is amazing. Although the complexity skeptic in me is thinking, "Oh, my goodness. Now, we've got all this state that we're storing on the server. We have to have data migrations." We need some sort of migration mechanism for our clients-side state and perhaps some transaction and rollback in case you're not able to successfully migrate your data. It sounds like a lot of fun but I'm just imagining we really are getting started here. Has there been any work on that aspect? MIKE: If you've ever worked with IndexedDB, it does have a concept of migrations. Basically, the data you store on a device has a version and when you read in what's called a file but it's a database, when you read that in, the first thing you do is you basically bring it up to date incrementally. You'll bring it in, you're looking for version nine like your code wants version nine. What you see is version two because your user hasn't been at your site for six months and you're going to take it from two to three to four to five to six. Each of those, essentially constitutes a migration. We just have to apply the same principles of forward-compatible changes. The escape hatch here is remember it's progressive enhancement so if we had to destroy everything, fall back to a basic experience and start from scratch, like discard all of our data, it's really being held there as an optimization. Some people use this immutable caching strategy or basically, like rolling out a new service worker version constitutes for the most part. Any data that wasn't created by a user you're going to discard that and you're going to fetch it new. You don't have to worry about like, "Crap. This six month-old thing is still plaguing half our users and we can't get rid of it," like you can have [inaudible]. But you should really check out this course. It is simpler than you think and what we demonstrate is not a trivial like hello service worker. It is taking in a classic single page app, making it completely offline, having it exist on the home screen and I think the service worker ends up being no more than 100 lines of code. It's not too bad. ELRICK: I'm definitely going to check that out because my progressive web app journey is still on just service workers. MIKE: That's very [inaudible], though. ELRICK: Yeah. I'm definitely checking it out. Sounds like a really fantastic course. MIKE: I've been focusing a lot on this area and another one is security. The reason I picked these two is because developers are not really going to learn about these on the critical path to [inaudible] plus they learn about them the wrong way. As the JavaScript world is becoming radically more complex with each passing year, I've tried to target some of my efforts towards areas where they are not getting as much attention as I'd like to see, just because we have to focus somewhere. Obviously, getting the app out and figuring out how to make the build tools work for us. Without that, we can't do anything at all. One of the courses that's coming in September for Frontend Masters is a one-day web security workshop or we'll do with like cross-site scripting, how to work with certificates because if you start playing with HTTP/2 -- the next generation of HTTP -- you will need to generate some certificates for development at least today you need to. I've seen some amazingly smart developers get this dangerously wrong to the point where they compromise their own machine and anything that's on that machine, just by trying to set up dev environment. Typically, I'm an optimist but when it comes to this PWA stuff and security, I am paranoid. I feel like, we as a community need to get together and have the discipline to brush up in these areas so that as we introduce all of this new stuff, we don't end up opening a bunch of holes. Nowhere near the same rigor as put into frontend compared to backend and now, the line is blurred. Right now, we're server-side rendering so our code is running on the backend somewhere so injecting something can really mess things up in a bigger way. ELRICK: Yeah, I think that's a fundamental characteristic of someone does going to be involved in security paranoia. You have to be paranoid about everything. MIKE: Yep. I don't trust anything. CHARLES: It's important to make those things easy because I'm definitely fall more into the hippie camp like, "Everything is going to be fine. Let's trust everybody," which is I know is totally unrealistic. But then you get into these secure technologies and you learned enough of it just to get the task that you're going to do and then you forget. SSL is a great example. Over the course of my career, I've learned how SSL certs have worked probably, at least 10 times. ELRICK: Right, [inaudible] you had to set it up in production. CHARLES: Yes, exactly and then I promptly forget about it, never worry about it again and then the next time I'm like, "How did that work? What's this trust chain? What?" ELRICK: Exactly. I read a study from Carnegie Mellon a couple of years ago that showed developers observe security best practices dramatically less than the general public and the general public is not good. Do you know what I'm talking about when I say a certificate warning and a browser, there's big scary red screen saying like something is wrong here? Before the Chrome team put some effort into improving that, 70% of people would click through those and proceed anyway. After their improvements, over a third of people still clicked through and that number when you just look at Canary versions of browsers, that number is actually considerably higher close to 50% of our developers. We're trained by every broken certificate system that exists on the internet like the legitimate ones or maybe some things just expired. They're training people to just click straight through these things and as a result, it is terrifyingly easy to mess with people. We have to remember as developers, our machines, those have the private deploy keys and those have the SSH keys to commit code to GitHub, we have to treat that like it's a private data. It's really, really important that we make it easy and that we make sure that that easy path is also very safe. CHARLES: Absolutely. All right. Well, thank you so much Mike for coming by and talking with us. We touched on a lot of subjects but I feel like I certainly learned a lot. MIKE: Yeah, thanks. It's been so much fun talking with you this morning. CHARLES: Anybody who wants to go and check out those courses, they're on Frontend Masters. Now correct me if I'm wrong, you've obviously got the one on progressive web apps or PWAs. If it doesn't work offline, it's faux-PWA. MIKE: Yes, I like that. That's going to become a t-shirt sometime soon. CHARLES: The fundamentals of progressive web app development, which is now released if I understand correctly. MIKE: Members have access to everything, you can watch the raw video now. The edited course will be available later this year. CHARLES: Okay, and that's with Steve Kenny. I am very much looking forward to looking at that and learning more about it. Then you've also got ones coming up in September on TypeScript web security in Visual Studio Code. MIKE: Yep and members can watch that as a live-streamed event. Frontend Masters even ask people to watch the comment stream so you'll have a proxy question asker or hand raiser in the room. It's really a great experience to be part of a live thing. CHARLES: Oh, man. That sounds awesome. Then if you are obviously doing your independent consulting and if people want to get in contact, how would they do that? MIKE: You can find me on Twitter, @MichaelLNorth or you can visit my website, Mike.Works and I have all of the courses I teach and outlines and I can just open up a little chat bubble on the lower right, ask me any questions that you have. I am really passionate about teaching people. If you like that's useful for your team, please reach out and I'd love to talk. CHARLES: Fantastic. Thanks, Mike and thanks everybody for listening to us. If you want to get in touch with us, you can always do that. We're on Twitter at @TheFrontside and email, Contact@Frontside.io. Thanks, Mike. Thanks, Elrick and I will see you all later. MIKE: Thank you so much. ELRICK: Bye.
Kris Van Houten: @krivaten | krivaten.com | Q2 Show Notes: 00:55 - Kris' Interest and Passion for Accessibility 06:07 - Using Ember for Accessibility: Pattern Adoption 10:13 - Context Switch Awareness and Managing Focus 12:08 - Asynchrony and Desired Interaction 14:04 - Building a Form Input Component 19:05 - Things That Are Hard to Catch 22:41 - Assistive Browsers? 28:17 - Making Things Accessible From the Start Resources: Building for Accessibility by Nathan Hammond @ Wicked Good Ember 2015 The A11y Project: Web Accessibility Checklist WCAG 2.0 checklists Why Don't Screen Readers Always Read What's on the Screen? Part 1: Punctuation and Typographic Symbols Mozilla Accessibility Kris' Blog Post Series on Accessibility: Part 1: What is accessibility and why should we care? Part 2: A Primer on Accessibility Part 3: Getting Our Apps Ready for Accessibility Part 4: Building an Accessible Icon Component in Ember Part 5: Building an Accessible Input Component in Ember Part 6: Building an Accessible Alert Component in Ember Part 7: Building an Accessible Numbers Component in Ember Part 8: Building an Accessible Currency Component in Ember Transcript: CHARLES: Hello, everybody and welcome to The Frontside Podcast, Episode 72. My name is Charles Lowell, a developer here at The Frontside and podcast host-in-training. With me today is Wil. WIL: Hello. CHARLES: Hey, Wil. Today, we're going to be talking about accessibility in single page applications with Kris Van Houten who is a developer at Q2. Hey, Kris. Thank you for coming on the show. Today, we're going to talk about something that I know a lot of people's minds here and probably elsewhere on the internet, it's a topic that's getting a lot more attention, which is a good thing and that's accessibility. We're going to explore the niche of accessibility as it applies to single page applications. Now, you're a frontend developer at Q2, what initially got you interested in and passionate about accessibility in general? KRIS: I honestly feel my path to passion in this area has been a little bit unorthodox in a number of ways. I basically started out in total apathy of this topic and over the last year, it has turned into a genuine interest of mine. About three years ago, I remember listening to an episode of ShopTalk Show with Dave Rupert and Chris Coyier and they kind of went on this large rant about accessibility and why more developers need to be concerned and compassion about it. Dave Rupert was talking about his contributions to the accessibility project and I'm sitting back and thinking to myself and this is back then, obviously, "Why would anyone who is blind want to use anything that I'm working on." I basically balked at the idea and disregarded it entirely. At that time, I was just getting my feet wet with Ember working on an application with a company here in Cincinnati and we had these conversations about, "I notice that we put this action or a clickable event on a div element, should we not be doing that? Is it that not something that we should be doing?" I remember sitting back and having this conversation and saying, "The ads been crawled by SEO and Ember isn't yelling at us for doing it. It still works fine so what the heck? Let's just go with it." Basically, every single app that come into since then has basically adopted that same mindset even before I joined the team so I know it's not just me who is thinking this. A lot of developers that have been exercising the same way of doing their code. CHARLES: Right, it's the path of least resistance. Everybody's got a job to do. Everybody's got features to deliver so that practice can be very easily self-perpetuating, right? KRIS: Exactly and I think a lot of developers just don't understand the semantic difference between a div or a label or a button or a link and how browsers can actually treat these difference HTML attributes or HTML tags differently because of how assistive technology can utilize them for per person's benefit. That's where I was a little over a year ago basically. When I first started at Q2, that first week, I got pulled into a discussion about design patterns which is another passion of mine and somehow, that turned into me joining a group that was to establish to figure out how to tackle the task of making our large app accessible. Basically, we had a company come in, audit our application and we got a big fat F for accessibility so it's something that we said, "We need to start tackling this problem." Being that, I just started at the company that week, I was going to tell them no but internally, I was panicking and saying, "I got to figure out what is this whole accessibility thing is and why it's important." I started looking for books, articles on the topic and trying to basically flood myself with information. Two things that really transformed my way of thinking was actually a talk given by Nathan Hammond at that Wicked Good Ember in 2015, where he shows an example of building an application without accessibility in mind so basically, doing what I was doing before which is we're adding actions to div tags, we're not really caring about semantic HTML, we're just making the feature or the application work. But then what he does, which I think is super powerful is he pulled up a colleague of his who is blind and had him try to use the application. He just goes through and you can see the struggle and he's actually vocalizing and talking about where he's [inaudible] with this application. Long story short, Nathan comes back up and makes a few adjustments. DHTML has [inaudible] up again and it's night and day difference just by changing the markup and by dropping in the Ember A11y add-on which helps with focusing the browser in certain areas of the content. He's able to totally transform how's individuals able to use the app. For me, that was a super powerful to come in and see that and see someone actually struggle with a website that they were trying to use. I think, [inaudible] where I always saw accessibility was it will only affects people who can't see and I think that's the other area where I've really started to have that paradigm shift was when I realized that this isn't just people who can't see. It's for people who have motor difficulties, who can't use a mouse and how to use a keyboard instead. People who have various vision issues, whether that's cataracts, colorblindness, glaucoma, dyslexia, some in these effects, not just DHTML but also affects color contrast, the fonts that we're using that impacts every area of application design and development and that's where I started to realize that that was where the paradigm shift happened in my mind where I started thinking to myself we really need to start talking about this more and getting other developers on board in general on this. CHARLES: It can be intimidating, especially when it feels like on a single page application, your divs have to do more, so to speak in the sense that it feels that your HTML is fatter. It's not just a thin layer but your HTML is actually part of the UI. KRIS: Exactly, yeah. CHARLES: When it comes to having this paradigmatic shift that you're describing, when you're looking at your single page applications, are there any insights into the general structure of the application that you feel like you've gained that are foundational, they kind of transcend accessibility? I guess, what I'm saying is, is there any way that you become like a better developer or been able to recognize foundational patterns because of having these insights surrounding accessibility? KRIS: I've been working with Ember for about three or four years now, basically since it was still in beta. Over the last several years, I have started to accumulate a lot of knowledge as to how we can utilize Ember to do a lot of the heavy lifting for us. When I started getting more passionate about the area of accessibility, first question that came into my mind are how can we use Ember to do some of the heavy lifting for us. For example, some of the things that I had done was go through and start working on developing a couple of components that basically cover a lot of things that I find ourselves doing [inaudible] a lot. Whether that might be a component to just plain icon on a page or a component to display input on a page. What we're able to do is using Ember, we can say, "Here's the icon I want to display but if I don't happen to pass in an aria-label attribute, for example. The component will add the 'aria-hidden=true' for me. Being able to really utilize the power of Ember to do some of that stuff for us on the back side of things, I guess you could say it magically. CHARLES: Let me stop you there for a second and unpack that example. What you're saying is, if I'm going to put an input on the page, if I actually don't assign an ARIA role, it's going to hide it from me? KRIS: No. I was thinking of an icon components, say if I'm using Font Awesome, for example and I want this with the trash icon so I wrote a component for our specific icon library that we're using. We pass in the icon that we want to display, again that could be the trash icon and we can also pass in an aria-label attribute to add a label to that span that will be read to the user. But if we don't pass that attribute in, the component will automatically add the 'aria-hidden=true' attribute for us so basically it skips over it. CHARLES: Yes so it won't be just garbage for a screen reader or someone navigating with a keyboard. WIL: Yeah, otherwise the screen reader tries to read the content of the icon CSS which is just the Unicode. CHARLES: Right. KRIS: Yeah. What we really is trying to figure out and what I've spent a lot of my time, especially in writing my blog series on this was while we are using React or Vue or Angular or Ember or whatever, how can we utilize the power of the single page application frameworks to do some of that heavy lifting for us in the background without us needing to explicitly define everything. I'd say, especially when you work on a large team like what I work on currently, we can't expect everybody to be extremely well-versed in the area of accessibility so if we can do some of the work for them and just encourage them to adopt these components in their daily workflow, it does some of the work for us. That's what we're working on and talking a lot about at Q2 is basically this pattern adoption. CHARLES: Right so it sounds like to kind of paraphrase, whether you're working in any framework most of them have this concept of components so really leaning hard on that idea to make components at the very granular level aware of their own accessibility. Is that fair to say? KRIS: Yeah, obviously there's more I'm sure as we go for the conversation about some of the things that I've tackled in this area but long story short, being able to utilize and recognize, you have this extremely powerful JavaScript framework at your disposal to do some of work for you so why not equip to do just that. CHARLES: Yeah. I guess that falls into my next question, which is there are component level concerns and if there are other component level concerns, I definitely want to hear about them but what immediately leaps to mind is there are also cross-cutting concerns of any single page application, what's the state of your URL and if you're using a router. Some of the content on the page is going to be changing and others isn't like how do you cope with that? What are the cross-cutting concerns of an application that span components and then how do you cope with them? KRIS: I think one thing that comes to mind as you're talking is the whole area of context switch awareness. If I click a link, if I go from the home page of an application to my profile page, how does a screen reader know that that content has now changed to present this new information to the user? I know what we were able to do was we were able to drop in the focusing out with component that's put out by the Ember accessibility team, which basically whenever we render to an outlet, that's utilizing this focusing outlet component, it will focus the browser to that main area and start presenting that information back to the users. One area that was at the top of our list as we start tackling accessibility was we need to figure out this whole context switch awareness thing because -- this is back then obviously when we first got started -- back then there was no way for a user to know when the page changed so they would basically be sitting there, waiting for any kind of feedback or whatsoever to be presented back to them and it just wasn't happening. I would say, managing focus is probably one of the top level concerns when it comes to single page applications because it's a single page application so if you click a link, the page isn't completely refreshing, prompting the screen reader to present the information back to user. That's one of the key areas that I think of. CHARLES: What about things like asynchrony because a lot of times, these context switches are not boom-boom, one-two. The content on which you want to focus isn't available yet. Usually, the analog from a visual UI would be a loading spinner or a progress bar. How do you deal with those to say, "Your content is not quite ready. If you're made to wait it's because we want your content to be of the highest quality." KRIS: Sure, yeah. We were able to drop in the focusing outlet components in our application and it took care of a good chunk of the work but it seems like in our application, we're doing something that might not be as conventional as the rest of the Ember community would like them to be so we might not use the model hook as we should. It's hard for the page to know when the contents actually ready, when it's been rendered to the DOM to present back to the user. One thing that I'm currently trying to tackle right now, to figure out how we can remedy that problem. I probably say, honestly that's the challenge I'm working on right now. I don't have a solid answer to that one at the moment. CHARLES: Irrespective of how it plugs into the tool that you're using, what would just be the desired interaction there, regardless of how you make it work? KRIS: I guess, conceptually what I'd be thinking about is how can we notify the user we're loading content right now and whether that we have an alert box that has the ARIA alerts, basically attributes set on it, that we could pass in new, basically notifications to it to let the user know, "Loading content. Please wait," and then once that content resolves, focus them on that main outlet where the content has been displayed to read that content back to the user. That's how we're trying to think about tackling this issue but we haven't have a time to implement it to see how it's going to work across all the different avenues of application. CHARLES: I did want to come back at the component level. are there any other ways that you can lean on Ember or lean on React or lean on Vue, if you're using a component or in framework, just talk a little bit more about how you use those to unlock your application and make it more accessible. KRIS: One thing I can think of is a way that we can enforce better usage of the framework that we're using is one that comes to mind is a component that I worked out in the blog series that I wrote was building a form input component. Especially, when you're trying to write an accessible app, I think about how can we enforce certain patterns when other developers come in later on and want to add a field to a form or use this component somewhere else in the application. What are some ways that we can enforce that they're doing everything, using the component correctly so that way it renders accessible mark up? What I tinkered around with and we actually just landed in our application is basically a form group component to where we pass in, obviously the value that the input is bound to. But we also pass in a label that is tied to the input and whenever you hit save and the app goes to refresh, if you don't pass the label, there's an assert statement that basically fires up an error into the console and lets you know, "You're trying to use this component, you need to pass into label attribute for the purposes of accessibility and here's the instructions on how to do it." We've been kind of toying around with this idea of enforcing patterns because again, we have several dozen developers at Q2 that are working on this stuff and they're not all wizards when it comes to accessibility but how can we gradually start getting them to the place where they're adopting these patterns and best practices. I'd say, doing things like that, we are enforcing patterns in the usage of the components as well is really a key. One thing that we implement it in our testing framework is the use of a Deque Labs' aXe engine to basically go through, we can pass it a chunk of HTML and it will give us any suggestions that it has to make that content more accessible. We're using that in our test library right now, in our test build and encouraging developers as they write new components, as they go in and modify components to throw new snippets in to make sure that the content that's being spit out here is accessible and then submit your PR again. Just trying to be more hands on in that way. CHARLES: So you actually running a GitHub agent or something that's actually in the same vein as your test suite or if you're taking like snapshotting with Percy for doing visual diff so you're actually running a third check, which is an accessibility check? KRIS: Right now, we were able to land the aXe engine into our test build a couple months back so we're just slowly incrementing that over time. We have a couple challenges in the way of getting Percy implemented but that is in our list of goals to have that running as well. But one thing that I really like about aXe engine in particular is that if your check fails, it refines improvements that you should be making. The nice thing about it is also spits out a link to a page on Deque Labs website. They give an explanation of what have found and basically educates your developers for you. To me, I think that's huge because again, we can't educate every single developer and expect them to be pros at this but we can utilize tooling like the aXe engine or the [inaudible] Chrome extensions or stuff like that to do some education for us. As we work towards automating this further and further by using the aXe engine in our development side of things or using Percy on the test build as well. See, there's all kinds of stuff you can do but that's where we are right now. CHARLES: I really like that idea because in comparison with what we talked about at the top of the show, about how there's this path of least resistance that developers will follow quite naturally and quite rationally, which can lead to not accessible applications. It sounds to me like what you're doing is a establishing the same path of least resistance but having that path guide you towards accessible applications and saying, "This path of least resistance thing, it can be an asset or a liability so we might as well make it an asset." KRIS: Yeah, for sure. We sit down once a week and we talk about whatever challenges we're trying to work through in terms of accessibility. We have a weekly meeting where we sit down and talk about it. I thought one of the key topics to those conversations is how do we get the other developers that are not in these meetings more aware, more informed and more up to speed with this that they care about it, that they're working on it and it's part of their inner dialogue as they're writing out new features that are going to be deployed out to our clients. Lots of challenges there. CHARLES: Yeah. We've talked about some of these problems that you catch, you're actually writing some assertions there on the test build so you'll actually fail if there's certain requirements that aren't met but what are the things that are more intangible? How do those come up in terms of accessibility? What are the things that you can't catch through automated testing? KRIS: Right now, some of things that we're having a hard time testing which Percy will help once we get that implemented is contrast ratios and stuff like that. That's one of the key things that comes to mind for me when I think of the things that are a little hard to catch. I think another thing that's hard to catch, especially at the aXe engine and stuff like that, won't necessarily catch is the flow of your dialogue. When I turn on a screen reader and it starts reading back this page and content to me, sure we can make it so that it doesn't read out the icons character code and a lot of stuff. It presents the information we want back to us but I think, having that information presented back to the user in a way that's legible, that makes sense to them is probably one of the bigger challenges that I've been working on a little bit. One that comes to my mind is like the reading of currencies or numbers. One thing that I found way helpful was Deque put out a very thorough article on how the different screen reader like JAWS, NVDA, Apple's VoiceOver, how they read different types of punctuation, different types of graphics symbols, how they read [inaudible], $123.50, what does a screen reader actually read back to you. That's where I've actually been spending so much of time lately is building on some components that instead of reading back what the streaming will read back by default, which should be, "Dollar sign, one-two-three-five-zero," having actually read back, "One hundred twenty-three dollars and fifty cents," so basically, writing a series of components, I would do some of that, again heavy-lifting force, in that way, our developers don't have to go in and manually add-ons aria-labels obviously. That's been a nice little challenge where something that's we are working on just testing right now and making sure it works right if there is any downsides to doing this but I want a person using a screen reader or other types of assistive technology to hear the information as I'm thinking about it. When I see $123.50, I'm thinking in my head that's, "One hundred twenty-three dollars and fifty cents," not in single digits one right after the other. Those are things that a lot of the automated software isn't catching. It's not catching like, "Your grammar is bad," or, "This isn't making any sense to me." It is catching like are you passing in or applying the attributes to HTML elements that you should be. Are you using semantic structure in your headings and stuff like that?" I think that's one of the areas where developer is need to get their hand dirty, turn on the a screen reader or use any array of different voice-over tools to actually listen to the content being present back to them to see how it's presented. CHARLES: Yeah, it's almost a difference between a syntax error versus a runtime error like we've got a lot tools that can catch the syntax errors and you can put those in and catch where you have something that's malformed but some sentences can be perfectly formed but make no sense and it takes a human set of eyes to make sure if that content is coherent. One of the things that if you're going to ship applications to people, you need to be able to try and measure as closely as possible the environments in which the people will be using your software so you can actually have an accurate measure of whether it works or not. For example, in the Ember world lately in the stuff that we've been doing with acceptance testing in React, we admit people are going to be using a multiplicity of browsers to access this application so it's very typical to use Testem or use Karma to fire up five different browsers, which if you're using BrowserStack, you can do fifty. You know, people are going to be using IE8.1 on Edge or on a Surface. They're going to be using Safari. They're going to be using Chrome and those often surface those issues but I feel like there's no access to the actual screen reader and assistive technologies to be able to make real assertions against those things. I imagine that it would be cool if there was some way that in Testem or in Karma, you could have one of your browsers be like an assistive browser that you could actually assert, I want to assert that it read it as, "One hundred fifty-three dollars and twenty-five cents," and is that on the horizon? Is that even possible? But it seems like something that we have to shoot for if we actually want to measure that these things are working if we actually want to capture data points. KRIS: Yeah, I totally agree. If you look at the documentation on W3 for how these different HTML attributes should be treated by the browser or by the assistive technology, long story short is this is not how -- in several cases -- certain screen readers are presenting the information back to you. It's not how it's treating the content. That's again, one of the areas I thought was way interesting about that. Deque article on punctuation and typographic symbols, which is like we should expect that this software is operating at this level to present this information back to user in such a way where it understands what the dollar symbol in front of a series of numbers means but it just isn't there yet. There's still work to be done. I'm hopeful for the day where our screen readers are a lot more powerful in that capacity. One that makes me a lot more hopeful about that is I don't know if it's just because I've been more interested about this over the last year but it does seem like I'm seeing a lot more people talk about accessibility. I'm seeing Apple putting out videos, talking about the efforts that they're making to make their software more accessible. It does give me hope that there's a lot more visibility on this now. There's a lot more people fighting for this cause to cause these companies to come back and say, "We're going to put more effort into this. We not just going to make a standard screen reader and ship it and just leave it there for five years and no one was going to touch it," but, "We're going to start making improvements." One thing that I did notice just over the last couple months even was that out of nowhere, we use Apple VoiceOver in Chrome, which isn't typically how people use it. They typically use it with Safari. But if you use in Chrome, it will actually read back to you as, "One hundred twenty-three dollars and fifty cents." When I came across that, I was kind of dumbfounded but then I was thinking to myself, the vast majority of people who are using screen readers aren't using this browser but that's really interesting that they're doing this now. I dream of that day where we can basically run a series of mark up through in a test or into a function and basically have to spit back, here's how screen readers going to present this back to you. I'm hopeful for that day. CHARLES: I'm wondering now like why don't major browser vendors, why is this not just a piece of a puzzle that comes when I download Firefox. Firefox has access to my speakers, why isn't there a web standard for how screen readers will treat content? Maybe there's an effort under way. KRIS: I sure hope so. Looking through documentation, we know how things are supposed to work, how we've agreed that they should work and now basically, we're just waiting for the different browser vendors and Microsoft and Apple to make the updates to their streaming technology as well as JAWS and NVDA. I'm hopeful that these changes come soon. These are improvements to the interface. CHARLES: Yeah. Any time there's a gap, you can see that's an opportunity for someone -- KRIS: For sure. CHARLES: -- To write some software that has some real impact. I know certainly, I would love to see some way to roll these things into our automated test suites. KRIS: Yeah. I searched for it but with no avail and it's a little bit beyond my knowledge of how to build something of that caliber. I hope someone else does it because I don't know how. [Laughter] CHARLES: Well, maybe in a year, maybe in two years, maybe in 10, although hopefully a lot sooner than that. KRIS: Yeah. I would judge that at the speed of things were going right now, I'm optimistic that we're going to have some much better solutions within the next year or two on this field. Especially of how much I'm seeing people talk about it now, how much it's becoming a part of the regular conversation of web development, application development. I'm really optimistic that we're going to see some strides in this area over the next couple years. CHARLES: Okay. With the time that we have left, I'm going to ask one more question. Kris, there is something that I wanted to ask you, which is let's say that I am a developer who is working on a team that is maybe it's big, maybe it's small. I've got an application or I'm starting an application and I have a desire to make it accessible. How do I establish that path of least resistance? What advice do you have for someone who's just about to take the first step on that journey to make sure that they have the outcome that they're looking for which is the most accessible single page app that they can have? KRIS: I think it's a great question. I would start out that answer by simply saying to encourage you to be somebody who cares enough to speak up and become an evangelist, become an educator and become an enforcer in your workplace for this work. You don't have to be the most knowledgeable person in the world on the topic. God knows I'm not and I still there were people come to me, asking me, "How do I make this feature, make the guidelines, make it accessible to screen readers," but I'm passionate about this topic and I'm interested in learning as much as I can about those. Step one, just being an evangelists for it. Be interested in it, care about it. I'd say, the next thing is just learn more about semantic HTML. I would say from a lot of the things that I've been trying to tackle with the application that I'm working on, just simply writing semantic markup takes care about 80% of my challenges. In just understanding what are the different elements, what are the different tags are for and how screen readers and other assistive technology see those things. To get started, I would say there's beginner, intermediate and advance stuff. I would say go to the accessibility project, which is just A11yProject.com and read through the content there. It's very entry-level. You can probably read through most of the content within an hour or two and really start to get a grasp as to what level of effort you're looking at in terms of your application. Once you get through that, if you still want to learn more, I'd say go over to Mozilla's developer network -- MDN -- and read through their documentation. On the topic, there is a little bit more exhaustive but it's still really easy to read and really easy to grasp. Based on a content they have shared there, I'd say more of an advance level is actually go through all the documentation on the W3. It's a lot more verbose, it covers a lot more of use cases, it has a lot more suggestions and just stuff ready to go over. I'm still working through that information. There's so much of it but I would say that's as a good place to get started with understanding the different attributes, what they're for and just the importance of writing semantic HTML. I would say some definitely good things to start tinkering with to find some of the low-hanging fruit in your application would be to use some of the assessment tools that are already out there. You have the [inaudible] little JavaScript snippet that you can put in your Chrome favorite's bar or you can use the aXe engine or if you even have an aXe Chrome extension that you could pop up in your application to basically give you report on some of the areas that you should be looking to make some improvements. I think it's important to view accessibility kind of like how a lot of bloggers view SEO, is that there's always more work to be done, there's always improvements you can make but the key is to take those first steps and start making those improvements. One of the nice things about the accessibility project and there's a couple other websites out there that have some of the lists, they basically have a checklist for you to go down. If you're just getting started with accessibility, they have a checklist of all the first things that you should be covering to get your app started in that realm, to start making those improvements. I know you guys do links in the show notes. I can definitely send you those things to those items to get people started. Another thing I find myself doing a lot is while we're talking about something in our chat at work in or just go off in the code pin and mock something out in HTML and then see how the screen reader reads our content back to me and then kind of tinker with it and do a little bit of self-discovery in how this all works together. There's a lot of options out there. I know just threw a lot at your listeners but I'd say, it all starts with being someone who cares about the topic and cares enough to start asking others to care as well. CHARLES: I think that's a fantastic answer and a great note to end on. But before we go, obviously we will include those things in the show notes but also the other thing that we're going to include is a link that you actually, I understand, have a series of blog posts related to all of the things that you've been talking about, which we'll also include. KRIS: Awesome. Thanks. CHARLES: Everybody, go read it. Thank you so much Kris for coming and talking with us about accessibility. I think you're right. It is a topic that's gaining a lot more traction and a lot more mind share in the mainstream that can only be a good thing.
Intro / Outro BRUTTO - Просперо (Piano Cover) https://www.youtube.com/watch?v=NwsISaGo_PU 00:03:31 Интервью с Виктором Жорой об атаке на объекты электроэнергетики УкраиныПричиною вчорашнього знеструмлення половини Івано-Франківщини була хакерська атака http://goo.gl/yxFlrD СБУ попередила спробу російських спецслужб вивести з ладу об'єкти енергетики України http://goo.gl/px5umB First known hacker-caused power outage signals troubling escalation http://goo.gl/KxqQsf Хакери погрожують українським енергомережам. За кібератакою на обленерго читається російський почерк http://goo.gl/PG3Gxk США підозрюють Росію у причетності до кібератак на електромережі України http://goo.gl/GPtka5 Malware 'clearly' behind Ukraine power outage, SANS utility expert says http://goo.gl/s4DGoc iSIGHT Partners: Sandworm Team and the Ukrainian Power Authority Attacks http://www.isightpartners.com/?p=5305 Троян BlackEnergy используется в кибератаках на СМИ и промышленные объекты Украины http://goo.gl/bUKvOG BlackEnergy Disrupt Matrix - SOC Prime https://goo.gl/rIJuD XPotential Sample of Malware from the Ukrainian Cyber Attack Uncovered https://goo.gl/KAuM5i BlackEnergy .XLS Dropper http://bit.ly/1JQV1fa Штаб: У "Борисполі" попередили ймовірну хакерську атаку з боку РФ http://goo.gl/TZUvVG Special Publication 800-82 Guide to Industrial Control Systems (ICS) Security (pdf) http://goo.gl/cv4mzk Cyber war in perspective (pdf) https://goo.gl/RjPuqU 00:58:41 Казусы наших 1с01:01:15 Герб мининформполитики http://goo.gl/R9ETMK 01:02:02 Суд дозволив прокуратурі обшукати український офіс Google http://goo.gl/9E83F2 01:04:04 SSH Backdoor for FortiGate OS Version 4.x up to 5.0.7 http://goo.gl/o7UiyH Someone Just Leaked Hard-Coded Password Backdoor for Fortinet Firewalls http://goo.gl/p17WSL Fortinet says backdoor found in FortiOS is "a management authentication issue" http://goo.gl/b0m1tU 01:07:03 Facebook spars with researcher who says he found “Instagram’s Million Dollar Bug” https://goo.gl/SfUpSB 01:08:43 iOS 9.3 brings multi-user mode to iPads, along with more features and fixes http://goo.gl/Gjl9bl 01:11:10 How Nvidia breaks Chrome Incognito https://goo.gl/fZRwuQ Nvidia: Chrome 'Incognito' Porn Leakage Is on Apple, Not Us http://goo.gl/g3dk0Q 01:14:11 Roaming through the OpenSSH client: CVE-2016-0777 and CVE-2016-0778 https://goo.gl/Mbd8eY Evil OpenSSH servers can steal your private login keys to other systems – patch now http://goo.gl/GUaBfa How To Fix OpenSSH's Client Bug CVE-0216-0777 and CVE-0216-0778 by Disabling UseRoaming https://goo.gl/pkVRra 01:15:29 Microsoft Gives Details About Its Controversial Disk Encryption https://goo.gl/bTCfJr 01:17:21 Recently Bought a Windows Computer? Microsoft Probably Has Your Encryption Key https://goo.gl/Rikium 01:18:11 Microsoft ends support for Windows 8, IE8 through 10: What does this mean for you? http://goo.gl/tLKJiM 01:18:40 The Tor Project Is Starting a Bug Bounty Program http://goo.gl/FKaraF 01:18:55 Linode: back at last after ten days of hell http://goo.gl/0pCRSF Linode Blog » Security Notification and Linode Manager Password Reset https://goo.gl/A2ee0q 01:19:21 Cisco admins gear up for a late night – hardcoded password in wireless points nuked http://goo.gl/W8XfvK 01:19:29 Про ДДоС говнокод.ру через JS в посте на хабре https://goo.gl/QNxvWG 01:21:21 TrendMicro node.js HTTP server listening on localhost can execute commands https://goo.gl/u8yMDh 01:23:37 Debug code cracked case in hunt for mystery Silverlight zero day http://goo.gl/oW4B5d 01:24:44 Software bug granted early release to more than 3,200 US prisoners http://goo.gl/1ke6sV 01:25:32 Massive bug at online gaming platform exposes users' sensitive data http://goo.gl/YS7Ja0 01:26:19 Turkish carder scores record 332-year jail term http://goo.gl/7gGxpe 01:26:50 Vulnerability allows to permanently delete any skype account by support request http://goo.gl/fbF6y1 01:29:28 French say 'Non, merci' to encryption backdoors http://goo.gl/W4mh04 01:30:13 Database leak exposes 3.3 million Hello Kitty fans http://goo.gl/10lH0a 01:30:23 250 Hyatt hotels hacked via PoS malware http://goo.gl/Vobx0i 01:30:42 Trustwave failed to spot casino hackers right under its nose – lawsuit http://goo.gl/4CpA7i 01:31:51 Stranger talks to a kid through this hacked baby monitor http://goo.gl/KK9Xey 01:32:38 Holiday hack challenge https://holidayhackchallenge.com/ Security weekly #444 http://goo.gl/PdY9C3 01:41:07 drduh/OS-X-Security-and-Privacy-Guide https://goo.gl/TihhlC
LastPass gets a design makeover, Tank reads good, and 2015: Year in Review. Tech You Should Know The Force Awakens and makes a ton of money Microsoft is dropping support for IE8, 9, & 10 on Tuesday Netflix is now live in 130 countries! LastPass made MUCH NEEDED UI update on the web FitBit announced an Apple Watch copy Twitter is moving past the 140 character limit Microsoft made a selfie app for iPhone. Please help. Tech You Should Use Goodreads Theology From the Headlines Mashable’s Best Tech of 2015 7 Tech Trends from 2015 Recommendations Craig – Sermon of the Day Ben – Kings Kaleidoscope, Citizens & Saints, and Ghost Ship Ways to Contact Us Connect with us in Slack: slack.techreformation.com Follow us on Twitter: @techreformation Check out our website: techreformation.com Email us: ask@techreformation.com Review us on iTunes and recommend us on Overcast! Music used by special permission of Matthew Parker. Check him out on SoundCloud and iTunes!
Summary Sara Soueidan (@SaraSoueidan) has been traveling the world talking about SVG (Scalable Vector Graphics) over the past year. Since then, we've learned a lot more about the power of this declarative graphical language. Now that many projects have dropped support for Internet Explorer 8 (IE8) and older mobile browsers, SVG has become a staple for non-bitmap art, visualization, and other graphical web development. Sara has recently shared many of the ‘gotchas' and best practices in talks at Beyond Tellerand in Düsseldorf & Microsoft Edge Web Summit. Together, we take a closer look at how developers can leverage her advice in our web projects today. Resources SVG W3C Working Group - http://www.w3.org/Graphics/SVG/ MDN documentation - https://developer.mozilla.org/en-US/docs/Web/SVG SVG 1.1 - http://www.w3.org/TR/SVG/ SVG 2 - http://www.w3.org/TR/SVG2/ browser support - http://caniuse.com/#feat=svg SVG Effects Taskforce - http://www.w3.org/Graphics/fx/ Scaling check for IE9-IE11 - http://codepen.io/tomByrer/pen/qEBbzw?editors=110 Sara Soueidan – SVG Lessons I Learned The Hard Way – beyond tellerrand DÜSSELDORF 2015 - https://vimeo.com/135466848 MS Edge Web Summit 2015 - https://channel9.msdn.com/Events/WebPlatformSummit/2015/On-the-Edge-with-SVG CSS Conf AU 2015 - https://www.youtube.com/watch?v=lMFfTRiipOQ Overview of SVG Sprite Creation Techniques: https://24ways.org/2014/an-overview-of-svg-sprite-creation-techniques/ Inline SVG vs Icon Fonts [CAGEMATCH] http://css-tricks.com/icon-fonts-vs-svg/?utm_content=buffer2b75f&utm_medium=social&utm_source=facebook.com&utm_campaign=buffer Structuring, Grouping and Referencing in SVG: The , , and Elements http://sarasoueidan.com/blog/structuring-grouping-referencing-in-svg/ clipping in svg - https://css-tricks.com/building-a-circular-navigation-with-css-clip-paths/ styling content with CSS - http://tympanus.net/codrops/2015/07/16/styling-svg-use-content-css/ art direction for embedding - http://sarasoueidan.com/blog/art-directing-svg-object/ All about viewBox :: http://sarasoueidan.com/blog/svg-coordinate-systems/ The State of SVG Animation - http://blogs.adobe.com/dreamweaver/2015/06/the-state-of-svg-animation.html#.VXGQW1yqqkq Some SVG Tools - http://sarasoueidan.com/tools.html Sara on Github - https://github.com/SaraSoueidan Codrops on Github - https://github.com/codrops Smashing Book 5 http://www.smashingmagazine.com/2015/03/real-life-responsive-web-design-smashing-book-5/ complete guide to SMIL https://css-tricks.com/guide-svg-animations-smil/ CSS Motion Path module http://www.w3.org/TR/motion-1/ d3.js http://d3js.org Weighing SVG Animation Techniques (with Benchmarks) https://css-tricks.com/weighing-svg-animation-techniques-benchmarks/ The GreenSock Animation Platform (GSAP) http://greensock.com Snap.svg http://snapsvg.io/ Firefox bug https://bugzilla.mozilla.org/show_bug.cgi?id=891074 (UPDATE: Fixed by @jwatt) Angular Remote Conf Do you want to attend a conference with top level Angular speakers but can afford the cost and inconvenience in travelling? Angular Remote Conf is an online conference Sept. 24th through the 25th with live interactions, a dedicated forum, respected leaders in Angular, and best of all you never have to leave the comfort of your own home to attend. The Web Platform Podcast listeners receive a 20% discount for https://angularremoteconf.com/. All you have to do is use "webplatform" as the coupon code at checkout to get your 20% off. This works for group tickets, standard tickets, and early bird as well. Head over to angularremoteconf.com and sign up ASAP to get the maximum savings DevFestDC 2015 The Web Platform Podcast is a proud media sponsor of DevFest 2015. DevFest is a conference with Great Sessions and Code Labs on Android, Wearables, Polymer, AngularJS, Google Cloud Platform, Meteor and many others. Show hosts Danny Blue & Erik Isaksen will be speakers and the event will be held at AOL Headquarters in Dulles VA Friday Sept 11th 2015 & Saturday Sept 12th 2015. For event registration details check out devfestdc.org and click on the eventbrite link. www.eventbrite.com/e/devfestdc-2015-google-developer-group-dc-tickets-17538373748 now! Panelists Danny Blue (@dee_bloo) - Senior Front End Engineer at Deloitte Digital Erik Isaksen (@eisaksen) - Front End Development Lead at Deloitte Digital & Google Developer Expert in Web Technologies Justin Ribeiro (@justinribeiro) - Wearables & HTML5 Google Developer Expert & Partner at Stickman Ventures
今回はフロントエンドエンジニアのいずみさんをゲストに レガシーIEについていろいろ話しました。 [トピックス] * レガシーIEの検証方法 * 独自プロパティ * 新規サービスのレガシーIE対応 * レガシーIEに対応できる新卒エンジニア不足問題 * IE7 → (不気味の谷) → IE8 → (谷の中腹) → IE9 (これ自体が谷の底)
Chase and Jonathan talk Polymer, Ember 2.0 training, Netflix's freedom of responsiblity, and spend some extra time talking about IE8 support.
This week we give away Joe's stuff, we break up with IE8 like a big boy, Joe and Allen get excited about readme files, and we argue about which is worse: bad code or bad architecture. That and more in this week's episode where we explore the new bits in ASP.NET 5.
This week we give away Joe's stuff, we break up with IE8 like a big boy, Joe and Allen get excited about readme files, and we argue about which is worse: bad code or bad architecture. That and more in this week's episode where we explore the new bits in ASP.NET 5.
Are you building mobile first? Carl and Richard talk to Chris Love about his work building mobile apps - in two styles! First Chris talks about working with a startup, with the latest tools and lots of experimentation. On the other side, there's the corporate development world, which is far more conservative and resisting change. Then the conversation turns to progressive enhancement, making new versions of web pages using modern tools and letting the old pages serve older browsers until its no longer needed. IE8 has one year of life left, its time to move!Support this podcast at — https://redcircle.com/net-rocks/donations
Are you building mobile first? Carl and Richard talk to Chris Love about his work building mobile apps - in two styles! First Chris talks about working with a startup, with the latest tools and lots of experimentation. On the other side, there's the corporate development world, which is far more conservative and resisting change. Then the conversation turns to progressive enhancement, making new versions of web pages using modern tools and letting the old pages serve older browsers until its no longer needed. IE8 has one year of life left, its time to move!Support this podcast at — https://redcircle.com/net-rocks/donations
Today we discuss how to argue against supporting older browsers, like IE8 and below. The assumption is that if left up to someone else in your organization, your team will end up supporting all browsers back into the stone age. It often falls on the developers and designers to champion pushing forward with the latest […]
While at NDC, Carl and Richard chat with Cory House about his experiences building Single Page Applications for the automotive industry. Cory talks about the challenges of the industry, including supporting both IE7 and IE8 running on Windows XP and iPad devices. Quite a span of technology there! The conversation digs into UI design, the integration of third party services and meeting the expectations of a customer that is not all that focused on technology. Cory digs into the idea of SPA as a classic desktop application replacement - it can be done!Support this podcast at — https://redcircle.com/net-rocks/donations
While at NDC, Carl and Richard chat with Cory House about his experiences building Single Page Applications for the automotive industry. Cory talks about the challenges of the industry, including supporting both IE7 and IE8 running on Windows XP and iPad devices. Quite a span of technology there! The conversation digs into UI design, the integration of third party services and meeting the expectations of a customer that is not all that focused on technology. Cory digs into the idea of SPA as a classic desktop application replacement - it can be done!Support this podcast at — https://redcircle.com/net-rocks/donations
Drupal 7.26 & 6.31 + i18n, custom_serach etc. Drupal 8, Paragraphs, Radioactivity, Migrate from HTML, Snazzy Maps, Cache Bully och många fler nyheter. Drupal Association Drupal 7.27 & 6.31 Custom Search custom_search-7.x-1.16 Internationalization i18n-7.x-1.11 DrupalCon Amsterdam Hello Drupalcon Amsterdam sprints do not require a ticket Drupal Developer Days 2014 Organizers Report Drupal grow in China Holly Ross the 2014th Contributor Drupal 8 This week (or two or three) in Drupal Core Hiding form fields in Drupal 8 Rolling out the welcome Mat Watch as I try to upgrade this module to Drupal 8. What happens next you won’t BELIEVE! IE8 for Drupal8 Jobb Arbetsförmedlingen Modultipset Paragraphs Radioactivity Migrate from HTML Snazzy Maps Cache Bully Developer blogg artiklar Flag checkboxes Drush CLI input Eget bastema eller inte? Top 10 Drush commands follow up 5 Tips to debug Drupal front-end with Chrome The cost of building a “perfect” custom Drupal installation profile 3 Tips for Making Your Drupal Features Highly Reusable Extra Drupal loggor
It's another beautiful Monday (somewhere) and we've got the news of the last 2 weeks covered, and we're breaking it down for you. The news this week is, well, quite frankly kind of dark. Everything tells us we're in for a rough ride for the rest of the year, and it's only getting worse. If I sound a little funny, it's because I'm talking through a massive sinus infection and it's making me talk funny and stuffy. Also the recording you hear is take 2 ... I had a major technology fail so we had to re-record, with less sadness. Topics Covered We are happy to report that Justin Beiber is in fact, not coming out of the closet and E! Online was only hacked by those wacky military hackers from the Syrian Electronic Army. Apparently they've been on quite the hacking spree of media outlets and even put a major - albeit brief - dent in the stock market! - http://www.nydailynews.com/entertainment/e-online-twitter-account-hacked-article-1.1335214 The US Department of Labor was hacked, in what appears to be a very targeted 'watering hole' attack aimed at Nuclear employees. The attackers, if the stories are true, burned an IE8 0-day on this one, and of course they are Chinese - http://www.eweek.com/security/zero-day-exploit-enabled-cyber-attack-on-us-labor-department/ Anonymous is threatening a massive attack against the White House (the political entity not the ...nevermind), Bank of America, Citibank and other targets on May 7th. Are these folks just becoming part of the 'background noise' of the Internet? Are security professionals just starting to become numb to the DDoS attacks? - http://pastebin.com/TyvAK20F Chinese hackers have apparently ransacked QinetiQ, a defense contractor with ties to global cyber intelligence operations, spooks,and other interesting things. Bloomberg's write-up was not kind to these guys - http://www.bloomberg.com/news/2013-05-01/china-cyberspies-outwit-u-s-stealing-military-secrets.html In the perfect illustration of the fact that insider threats are real a systems manager returned to the company he was no longer employed at and wreaked havok. Folks, there is no magic 1U box that will stop this sort of attack, be vigiland and have good auditing and processes! - http://www.computerworld.com/s/article/9238874/Systems_manager_arrested_for_hacking_former_employer_39_s_network
Herzlichen Dank an: www.winfuture.de Meine Homepage: www.bindermedia.ch Mailadresse: podcast@bindermedia.ch Die Themen: Budwiser will Biergläser mit Facebook verbinden http://winfuture.de/news,75822.html Google Now steht nun auch für iOS zur Verfügung http://winfuture.de/news,75819.html iOS 7 soll so "flach" wie Metro/Windows Phone sein http://winfuture.de/news,75828.html Outlook.com: Microsoft startet Skype-Integration http://winfuture.de/news,75829.html Intel will Autofahrer am Regen vorbeisehen lassen http://winfuture.de/news,75848.html Windows Phone-App für Android-Umsteiger online http://winfuture.de/news,75854.html iOS7: Preview wohl im Juni, Launch im September http://winfuture.de/news,75863.html Das Surface "Mini" soll ein 7,5-Zoll-Display haben http://winfuture.de/news,75891.html Microsoft warnt vor Sicherheitslücke beim IE8 http://winfuture.de/news,75909.html Studie: Facebook kann Psychosen verursachen http://winfuture.de/news,75912.html Windows 8.1 könnte mit Photosynth aufwarten http://winfuture.de/news,75911.html Die News der Kalenderwoche 18/2013. Mein Gast: Jeffrey Johnson
Episode 82, recorded on Monday 19th December 2011. Our second go at episode 82 features TWiL friends Lisa Duke and Sharon Bellamy reflecting on IBM Connect, the Social Connections event in Cardiff, a new fix pack (sorry Upgrade Pack) for Domino, Chrome overtaking IE8 and much more... The post 82: Zombie flu! appeared first on This Week in Lotus.
Episode 82, recorded on Monday 19th December 2011. Our second go at episode 82 features TWiL friends Lisa Duke and Sharon Bellamy reflecting on IBM Connect, the Social Connections event in Cardiff, a new fix pack (sorry Upgrade Pack) for Domino, Chrome overtaking IE8 and much more... The post 82: Zombie flu! appeared first on This Week in Lotus.
Scott talks to open source developer Fredrik Holmström about IronJS. It's a very complete implementation of JavaScript written in F# on top of the DLR. It's even faster than IE8 now and getting faster every day. How does something like this get built? What can you use it for? What are the Iron* languages used for and how can you get involved?
iPad installation on your new BMW, IBM's Battery 500 project, more Internet Explorer 9 and Facebook phone is it real? Show Notes 1. BMW brings Apple's iPad to the back seat in X3 Need a bracket holder for your new iPad on those long road trips? Do you have a BMW X3 Crossover? If so, you are in luck! BMW is introducing a new holder during their Paris Showroom Event. These optional holders should save the consumer a few bucks and avoid using other misfitted and awkward units. 2. IE 9 review As discussed in Episode 57, Steve provides an in-depth look into the features and functions of IE 9 Beta. Items such as Pinned Sites, Performance Advisors, and Download Manager are on the table. But what is Steve's favorite element of IE 9. Listen in and find out. Our listeners provide feedback as well. From Facebook Fans: Robert: I have. Tons better than IE8, but still has some quirks. Some pages simply don't load correctly. Especially pages that have fields that need input. Mathew: lookin a lot like chrome to me but it looks nice id say it performs better than 8 for sure WOT: Though I'm on a Mac's I did test it in a VM. Certainly the best IE yet but what I like is IE finally conforms to W3C standards Mathew: that is very nice one site fits all WOT: So true! Eventually no more separate CSS code for IE. Eventually. We still write to e IE6 compatible. Ugh. 3. IE 9 Architect The Waves of Tech crew is noticing a trend. Everytime a architect or engineering hits the pinnacle of success at a company, he or she jumps ships to another company. The head IE 9 architect is now employed by Google. 4. IBM's “Battery 500 Project” IBM is in the process of using Lithium-Ion battery technology to create a battery with nearly 500 miles per charge cycle. This new battery is called “Lithium Air.” IBM hopes to cash in on the movement in China that calls for 50% of their vehicles to be battery operated by 2020. What do Steve and Dave think of the possibility of this technology being introduced into the US car industry? 5. Facebook Phone? What is Facebook up to now?!?! There have been questions swirling the tech world that Facebook is getting ready to manufacture a phone. Are they attempting to saturate the social media platform? Steve and Dave discuss the implications of more cell phone options and whether Facebook should really venture into this market.
Guest host, Patrick Eaton Engadget writes an editorial about AT&T Rumor: Google Chrome OS will launch within a week Dolly Parton has been endorsing IE8
In this episode we talk about Dmitry cutting the cable, new PHP 5.3 release, IE8 features / new ad campaign and TwitterMatic. Finally we jump into our interview with Shawn Wildermuth and discuss PRISM v2 in Silverlight, the MVVM design pattern and how PRISM makes building complex Silverlight applications easier.
Allow me to admit something shocking right off the bat: I have not watched these ads. I am blogging in ignorance , because it seems pretty clear what's going on here. As was the case with the Seinfeld ads, it seems that once again, Microsoft is barking too hard, and up the wrong tree at that. Your browser is bad, it's been bad for years. Sure, IE8 is way better than its predecessors, but that's as close to polishing poop and calling it gold as anyone has ever come. But this isn't the way to make people try it. Another blast-from-the-past celebrity? Internet disorders? Even the most forgiving of watchers (a group that does not include me) must recognize this as a desperate and ham-fisted attempt at going viral. I've said it before, and I'll say it again: Microsoft, you need to be honest and direct. Show your logo first, admit there are multiple browsers, then say why IE8 is good for people. Show the product and show it working. Seinfeld, S. H. Y. N. E. S. S. , and "Welcome to the Social" are pretentious and ineffective. "I'm a PC" was trying too hard, but it was on the right track. But try to remember, Microsoft: you're not selling people , you're selling software . Leave the highfalutin nonsense to Apple and perfume commercials. If I'm wrong please let me know, I don't want to give Microsoft any more of my eyeball time than I already have.
Android is coming to India! After the browser wars, it's mobile OS from Symbian, Google, Microsoft and Apple battling it out. Also, 10 days ago, Opera announced that it was going to re-invent the web. 10 days later, hmmm not so much! In other news, we talk about Acrobat.com, Microsoft's IE8 campaign and the latest on Pirate Bay.
In this episode we discuss the iPhone 3 software update. How did the update go? What features do we like? We also discuss the new iPhone 3GS - even though we didn't buy, we still got our hands on one. Plus we have a good laugh at Microsoft's expense! BackBites Mike admits to checking his email and overnight Tweets as soon as he wakes up Elaine avoids needing to use Terminal to fix Safari Microsoft will be providing an IE8 CD with Windows 7 Microsoft Ten Grand Browser Advert (Safari version) Microsoft Ten Grand Browser Advert (Firefox version) Microsoft Ten Grand Browser Advert (Opera version) Microsoft Ten Grand Browser Advert (IE6 version) Microsoft Ten Grand Browser Advert (IE7 version) Microsoft Ten Grand Browser Advert (IE Mac version) IE8 blows the rest away IE8 blows the rest away - Wired magazine's response What's a browser? Office 10 the Movie Office 10 - The Movie - without the need for Silverlight Microsoft to give away AV software ChatBites TweetDeck for iPhone iPhone OS 3.0 - our upgrade experiences Backup Disabler Mike's lack of friends Elaine's two-and-a-half hour backup Mike's missing app updates in iTunes Adult content warning - Shazam Playlist order on iPhone differs to that in iTunes New features of iPhone 3.0 - Our views on Search, Phone, Voice memos and synching with iTunes, Landscape keyboard, Copy and Paste The iPhone 3.0 Software walkthrough How to use the best 40 features of iPhone 3.0 O2 - Picture Messaging iPhone 3.0 - 10 hidden features Improved camera close ups iPhone Alley - 96 hidden features in OS3 Push Notification Enabled Apps OS X Updates - Bluetooth and Safari iPhone 3GS Launch - was it a damp squib? The new camera and video on the iPhone 3GS We'll disconnect 'free' iPhone tetherers Dodgy button in the iPhone version of the iTunes store. Thanks to MikeB Feedback and Comments Koi Pond Web Snapper QuickSilver IanD (sweepa on Twitter) and Sakeel have a new new podcast called DigitalOutbox about gadgets and gaming and all things tech Colin Welland - The Brits are Coming Gary Neville's personal details exposed by Apple Events 25 June 2009 at 20:00 BST - Documents - Extreme makeover - http://macbites.co.uk/live. More information at http://www.digital-iq.co.uk
TechByter Worldwide (formerly Technology Corner) with Bill Blinn
What I thought would be an easy Linux upgrade wasn't, but the one that should have been harder was easy. IE8 goes critical. How to build an important system recovery utility CD. In Short Circuits, a really dumb phish and Windows 7 approaches one of my computers.
The highlight of this episode was the JesusPhone (some call it iPhone too) and the announcement of the features that would be in its upcoming firmware upgrade. Meanwhile in India, Symantec has ranked India as the 3rd most spamming country in the world. Bebo, a little late to the game, has announced its entry into India. Other topics in the episode include, Facebook bug revealing your private data, launch of IE8, Yahoo Flickr announcing a deal with Getty Images, and the Pwn2Own Contest.
The highlight of this episode was the JesusPhone (some call it iPhone too) and the announcement of the features that would be in its upcoming firmware upgrade. Meanwhile in India, Symantec has ranked India as the 3rd most spamming country in the world. Bebo, a little late to the game, has announced its entry into India. Other topics in the episode include, Facebook bug revealing your private data, launch of IE8, Yahoo Flickr announcing a deal with Getty Images, and the Pwn2Own Contest.
TechByter Worldwide (formerly Technology Corner) with Bill Blinn
A standard-issue Nigerian scam e-mail arrived from South Africa by way of South America; I have an early review of the upcoming ThumbsPlus Release, how to rename your computer, and some funny stuff; and in Nerdly News, Adobe issues an important security patch, the Conficker worm prepares to strike, and Microsoft releases IE8.
The technology news on the Indian shore included the selection of companies to managed the much required Mobile Number portability and delay in launch of Bhuvan, a desi version of Google Earth being developed by ISRO. Other news included Microsoft finally providing users a tool to remove windows components including IE8, Blackberry's App World, Flock divorcing Firefox, Google Docs being careless, Flickr opening up videos for everyone now. We also have Godaddy as our sponsor for TKM.
The technology news on the Indian shore included the selection of companies to managed the much required Mobile Number portability and delay in launch of Bhuvan, a desi version of Google Earth being developed by ISRO. Other news included Microsoft finally providing users a tool to remove windows components including IE8, Blackberry's App World, Flock divorcing Firefox, Google Docs being careless, Flickr opening up videos for everyone now. We also have Godaddy as our sponsor for TKM.
March 6th, 2008 - No audio problems this week, so if the show sucks we have no one to blame but ourselves. The show starts off with our typical around the room introduction and Kevin drops some big news about a new computer acquisition. We discuss new NIN news, the iPhone SDK, Microsoft's price drops, Bill Gates gets punchy, and more. You can provide feedback to the show at www.techtalkshow.com. - Show Notes - News Stories: Releases next week: SSB: Brawl (3/9/08), Stargate: The Ark of Truth (3/11/08) Google Calendar now syncs with Outlook Nine Inch Nails uploads new album on Torrent sites Gary Gygax, Dungeons & Dragons creator, dies Live from Apple's iPhone SDK press conference Wii outsells the PS3 4-to-1 in Japan, Sony execs "not psyched" Microsoft chops Vista retail prices Sanity prevails: IE8 will default to standard-compliant mode MacBook Air aflutter: demand stays strong, sold out often Gates to Google: 'Your business applications stink' Experiments: Do Coat Hangers Sound As Good As Monster Cables? Microsoft Offers $100,000 to Testers of Office Live Workspace Circuit City Trading In HD DVD for Blu-Ray Players What piracy crisis? MPAA touts record box office for 2007 Weekly Picks: Pete: Jeff: Xbox 360 Chris: Keystone Light Kevin: MacBook Direct MP3 Download iTunes Subscription RSS Feed
Carl and Richard talk to Mike Nash from the Windows Platform Strategy group about IE8, Windows 7, and everything else that goes on day to day in the life of a Corporate VP.Support this podcast at — https://redcircle.com/net-rocks/donations
© 2020-2025 Ivy Podcast Discovery LLC
