39: Famo.us Mobile Performance & Mixed Mode

Steve Newcomb, CEO at Famo.us, joins us for a second time with software engineer Michael O’Brien to talk about the changes in the framework. Moving toward what Famo.us calls “MIxed Mode”, which will debut in the upcoming framework 0.4 release, will allow developers to utilize the power of WebGL combined with the DOM. Essentially this means using the right tool for the right render target. “Mixed Mode” is not the only news Famo.us has to share.

 

As we know from episode 17 of our podcast, Famo.us is always pushing the boundaries of imagination and what is possible. The 0.4 release will also have front end containers very similar to Flash but with editing capabilities. Famo.us Hub, a new service being released, Famo.us JQuery Wdgets,  and so much more is almost at our developer fingertips.  

 

Release 0.4 will be 25kb minified and provide an extremely versatile set of tools for us to use as developers. The biggest announcement though is quite simpler but very relevant….Famo.us is now MIT licensed!

Resources

Panelists

Rachel Nabors - Master Web Animation Wizard, speaker & her own boss at Tin Magpie

Direct download: episode-39_famous-mobile-performance-and-mixed-mode.mp3
Category:JavaScript -- posted at: 7:25am EDT
Comments[0]

38: Aurelia.io

Rob Eisenberg (@EisenbergEffect) recently released a framework that focuses on standardization & swappable modules. Rob is no stranger to framework building, having created the popular JavaScript framework Durandal.js and more recently having helped develop Angular 2.

 

Aurelia has a great story. It uses ES6/ES7 JavaScript standards so you are coding with raw JavaScript. Templates use the template HTML tag and bindings are handled by pure JavaScript Template Strings. The framework itself is very barebones and can easily work with other libraries, frameworks, or modules outside Aurelia. This approach is very different than what we’ve seen from todays application or component frameworks.

 

Rob talks with us about this ‘spiritual successor’ project of Durandal, why it was created, and how it can be used today.

Resources

Panelists


Special Thanks to our community friends Webbear1000, Souldrinker, and zewa666 for their questions and contributions on Gitter.

Direct download: episode-38_aurelia.mp3
Category:JavaScript -- posted at: 4:21pm EDT

37: The Ghost Platform

John O’Nolan (@johnonolan), founder of Ghost, and Hannah Wolfe (@ErisDS), Ghost CTO talk about blogging and how the Ghost Project can make a difference in the blogging community. John gives a great overview of blogging and how Wordpress, the blogging giant, had become something totally different than what it had originally set out to be. Ghost was a response to the frustration of Wordpress and has since taken blogging to where, according to John, Wordpress should have gone.

 

Hannah & John share the project’s user experience and underlying concepts that can potentially aid developers in using Ghost to its full potential. They takes us through the technical details developers would need to get started as well as tips and great resources we can take advantage of.

Resources

Panelists

Direct download: episode-37_the-ghost-platform.mp3
Category:nodejs -- posted at: 7:26am EDT

36: Understanding PhoneGap

Brian Leroux (@brianleroux), Adobe Phonegap Team Member & open source software developer, spends lots of time on the Apache Cordova and Adobe PhoneGap projects. Hailing from Canada, he loves his hockey and beer- maybe even more than coding. He has spoken at many conferences and is an expert in delivering & teaching mobile web development.

 

Brian goes into depth on the Phonegap project. Brian discusses how developers can get started building great mobile experiences with Phonegap. He also details the benefits / downfalls of different approaches to mobile development using web technologies as well as tooling, testing, and automation.

Resources

Panelists

Direct download: episode-36_understanding-phonegap.mp3
Category:mobile -- posted at: 10:10am EDT

35: React & Reactive Elements

React’s Virtual DOM (Document Object Model) & the browser DOM  are very different in their approach. Virtual DOM prefers to keep it’s logic and changes in JavaScript and eventually optimizes output to the browser DOM at the most critical moment that provides performance boosts while the browser DOM utilizes the traditional way of working with the document, accessing HTML directly, working with browser events, and manipulating state. The performance gains from a Virtual DOM approach are outstanding despite the fact that events, css, markup, and ‘all-of-the-things’ are stubbed, recreated, or handled in some way inside the JavaScript. Browser DOM, on the other hand, handles everything in the global document and leverages JavaScript, CSS, and other resources directly. Surely these approaches are not good to use together.

 

Wrong!

Andrew Rota (@AndrewRota) & Denis Radin (@PixelsCommander) talk about the ways you can leverage both Web Components & React.js together in a symbiotic fashion. Denis, creator of Reactive Elements, starts us off explaining how his library came to be and why he chose to marry these two technologies in his work. Andrew, who spoke at ReactConf 2015 talks about his experiences with Web Components & React.

Resources

 

Panelists

Direct download: episode-35_react-and-reactive-elements.mp3
Category:web-components -- posted at: 10:53am EDT

34: Tenon.io & Web Accessibility

Accessibility for web applications typically gets added at the end of development cycles with different tools and low priority. This ruins the experience for many users and generally causes a huge impact on the quality of code. Because many companies are not held to supporting the standards of Section 508, Web AIM best practices, and WCAG by their clients and the impact in ROI is hard to measure it usually doesn’t happen.

 

Karl Groves (@karlgroves), Accessibility Consultant at The Paciello Group , creator of Tenon.io, & viking web developer leads by example, being an unstoppable developer community advocate for integration of accessibility over supplementation. Tenon takes a very interesting approach in that it integrates with tools we already use. Karl goes through developer resources. Tenon, and how we can make Web Accessibility a ‘first class’ citizen in our applications by making it part of our workflow and a fully integrated part of our process.

Resources

Panelists

Direct download: episode-34_tenon-and-web-accessibility.mp3
Category:web-accessibility -- posted at: 9:59am EDT

33: React Week

React Week (reactweek.com)  is the premiere week long workshop focused solely on learning how to build applications in React.js taught by Ryan Florence. React is just the "V in MVC" so attendees will learn all about how to build full applications around React with the Flux architecture, React Router, Webpack, and Firebase.

 

Ryan isn’t the only top developer teaching at React Week. Lead Instructor, Tyler McGinnis (@tylermcginnis33) , chats with us about the React Week event, Firebase, Webpack, React and more. Tyler is no slouch when it comes to thought leadership. Not only is he joining our podcast for this episode but he is doing an episode of the JavaScript Jabber podcast and speaking at both Mountain West JavaScript, and ng-conf conferences….all in the next two weeks.

Resources

Panelists

Direct download: episode-33_react-week.mp3
Category:community -- posted at: 12:43pm EDT

32: Microsoft Spartan & Internet Explorer

The Internet Explorer team at MIcrosoft are making waves in the developer community. The Internet Explorer browser (AKA IE or Internet Exploder) has a long and jaded history. Newer developers may not recall, but fifteen years ago Internet Explorer was arguably THE best browser experience we had.  IE had some basic developer tools, it practically invented AJAX with its ActiveX Technology, and it was the standard that corporate web development was measured by. Then, something happened. Firefox was born.

 

The Firefox browser, created by Mozilla, in contrast to IE was rapidly developed and it worked with standards bodies to guide feature implementation. One key success factor for Mozilla was that Firefox was an open source community driven project. Microsoft did not follow the same philosophies as Mozilla in their development. They opted to continue using proprietary technologies and continued on the path that led them to success for so many years.

 

The community began to resent Microsoft & Internet Explorer because Internet Explorer was, and as of today, stil is the default browser for its Windows Operating System. Since its creation, Windows has the majority market share in the corporate & government spaces. For better or for worse, the most successful development companies traditionally have targeted these markets and related sub markets because they typically yield the most profits comparatively to their costs.

 

The Safari & Opera browsers also fell in line with Firefox as far as standards implementation. Some extra code is needed to make everything work the same across browsers & devices but it’s minimal in effort. This ‘cross-browser’ coding is not as insignificant with Internet Explorer. Developers now had to build extra code and spend extra time needed to support Internet Explorer which cost companies a ton of money.

 

Something happened to Microsoft in recent years that slowly changed the way they looked at the business of web & mobile development. Microsoft decided to invest in open source. They created Microsoft Open Tech. They adopted JQuery as an officially supported JavaScript framework in their products. They began taking an active role in standards bodies and implementation of open standards. Microsoft also started doing something that surprised the developer community. They started telling the public what they were building into Internet Explorer as well as the development status of those features.

 

The  IE team began adding support & tooling for popular open source projects for their .NET platform. One of the most surprising moves by Microsoft is that The Internet Explorer team publically empowered developers & users to voice the features they want in the next versions of the Internet Explorer Platform experience.

 

Jacob Rossi, Charles Morris, & Adrian Bateman join The Web Platform Podcast to chat about the future of the web and how Microsoft is returning to its former glory and, arguably, leading the way in developer happiness. Microsoft is making massive improvements in the experience of Internet Explorer. On top of that they are actively assisting companies with the upgrade process and involving users in a Technical Preview Program of Windows 10 where users can help improve the product before the official release. This preview has a new browser alongside the modern Internet Explorer. This new browser, code named ”Project Spartan”, is free of the old Internet Explorer legacy and ushers in a new way to think about MIcrosoft’s Web Platform..

Resources

Panelists

 

Direct download: episode-32_microsoft-spartan-and-internet-explorer.mp3
Category:Microsoft-Web-Tech -- posted at: 8:37am EDT

31: Building with React.js

What is Facebook’s React.js project? When it was announced at JSConf US 2013 it met mixed reviews. One question that might enter your mind is...as developer today in 2015, do I really need to know another framework? The short answer is “yes”. In episode 31 “Building with React.js” we talk with Facebook developer and TC39 member, Sebastian Markbage (@sebmarkbage) on building apps with React, React Native, React Conf 2015, what’s new in the framework, what the core concepts are, what the hype is all about, and much more.  

Resources

Panelists

 

Direct download: episode-31_building-with-reactjs.mp3
Category:reactjs -- posted at: 10:59am EDT

30: Community Contributions

We, as developers, consume so much information. We read blogs, use our social media to get the latest happenings, follow startup & corporate companies in the news, and we pull in so many libraries and frameworks that power our applications and reduce the amount of work we need to do. Many of us take it for granted that the libraries, frameworks, gists, codepens, blog posts, screencasts, podcasts, & books we consume are all someone elses hard work. That work probably required a lot of time & energy but more importantly, those community contributors took the mindset that others could benefit from their work. Why would they make it a priority to spend the extra time and effort doing this when they have their own deadlines & their own struggles? Surely these people must be crazy, right? Perhaps this is true...but what if it's not?

 

Who are the people that create for us? Why do they do it? What can we gain in our own work by delivering our own content to others? How can we help contribute? These are only a few of the questions that tend to surface when we discuss the topic of contributing to the community. Episode 30 takes a strong & hard look at the reasons why we produce content and why we consume it. More importantly, we talk to the benefits developers can gain by both producing & consuming code and content in their own work.

 

Levent Gurses (@gursesl), mobile developer and founder of Movel, talks with us about his experiences running meetups, building software in the open, and sharing with the community. Movel is a mobile product & services company that specializes in building scalable corporate

Resources

Panelists

 

Direct download: episode-30_community-contributions_.mp3
Category:community -- posted at: 7:20am EDT