JavaScript

Season 2

Code

eat sleep

On this episode of Eat Sleep Code, guests Alex Bezuska and Eric Lathrop talk about game development, the Ludem Dare, Game Jam and how the started Two Scoop Games. Later, Jen Looper joins the show to talk about gaming with the internet of things.

Developer Network

Game Development

On this episode of Eat Sleep Code, guests Jeremy Likness talks about why he uses AngularJS. We clear the air about Angular 2 and discuss using directives for a clean separation of concerns.

All About AngularJS

On this episode of Eat Sleep Code, guest Derick Bailey from Watch Me Code talks about using messaging patterns like RabbitMQ to create scale-able applications. We also learn how messaging promotes asynchronous behavior throughout an application.

Messaging Patterns

On this episode of Eat Sleep Code, guest Cody Lindley talks about ECMAScript 6 (or JavaScript 2015). Cody fills us in on why the new standard is important and what it means to software developers.

The effect of ES6 (JavaScript 2015)

On this episode of Eat Sleep Code, guest TJ VanToll talks about the inner-workings of NativeScript. NativeScript is an open source project that allows developers to write native iOS and Android applications using JavaScript, XML and CSS.

http://developer.telerik.com/featured/nativescript-inside-the-black-box/

Ed Charbeneau: Hello, and welcome to Eat Sleep Code, the official Telerik podcast. I'm your host, Ed Charbeneau, and with me today is TJ Van Toll.

TJ Van Toll: Hey, Ed.

EC: And today, we'll be talking about NativeScript. What's inside the black box? TJ is a developer advocate on the DevRel team with Telerik. TJ, you work primarily with the NativeScript team and the engineers to discuss what's going on with NativeScript, and bring NativeScript to the masses.

TT: Yeah, that's more or less right. I've been with Telerik for a bit over two years. And I've been involved with a few different Telerik products. So Kendo UI, the Telerik Platform. And I've been working with the NativeScript team for basically the greater part of this year.

EC: And NativeScript is a way of developing native applications using JavaScript as the primary development language. Correct?

TT: Yeah. I'd like to think of it basically as a way that you can build iOS and Android apps, and Windows Phone, Windows Universal apps, probably some time later this year or early next year. And it's a way of doing it, as you said, with JavaScript, but also some other technologies that developers, and particularly web developers with some languages and technology skill sets that these people may already have. So JavaScript, CSS, optionally typed script. There is a lightweight XML language that's very XAML like for building your actual UIs, NPM for package management. And even when it comes over to the native site, you can use things like CocoaPods for existing iOS frameworks, existing iOS dot framework files, Android frameworks or things like jars. So we try to bring in the most amount of skills that people may already have. And allow people to leverage as many existing tools as you can, all while building iOS and Android apps that a lot of people are looking to do today.

02:22 EC: So what's nice about this is we're building actual native applications from this product. We're not putting this in a web view like, let's say, Apache Cordova or something like that.

02:33 TT: Yes. So that the real single biggest differentiator between NativeScript and something like Cordova and some of these other technologies out there is that you are building a truly native app. And that means that you have a truly native user interface, which means the UI controls are gonna be the same thing that you would have available in iOS app that you built in Xcode or an Android app that you built in Visual Studio. And as such, you're basically gonna have native-like performance because you're using those native controls. Your app is gonna not only look like a native app, but also really perform like a native app as well.

Find the full transcript on Telerik Developer Network

http://developer.telerik.com/featured/nativescript-inside-the-black-box/

NativeScript Inside the Black

On this episode of Eat Sleep Code, guest Cory House talks about ReactJS. We discuss the pros and cons of ReactJS and how different React is from other front-end frameworks.

React JS

On this episode of Eat Sleep Code, guest Chris Michel talks about how Sass can improve your CSS code, what's happening in the Sass community, and what Sass means for your next project.


Is Sass Right For Your CSS

On this episode of Eat Sleep Code, guest Matt Millican talks about Microsoft's open source initiative. Why did Microsoft go open source, what products, and what to expect in the future.


Why Microsoft Open Source

On this episode of Eat Sleep Code, guest Elle Waters explains why accessibility is important in software development and what a developer's responsibilities are when creating a product.

http://developer.telerik.com/content-types/podcast/accessibility-developers-user-story/

EC: Good, so today we're gonna be talking about accessibility. And I've brought on one of my favorite accessibility experts, Elle Waters. To give you a little background about Elle and myself. I met Elle at a conference called Code PaLOUsa, and I was watching a very interesting and informative and yet entertaining session on accessibility, and this brilliant speaker was giving a great session when her MacBook completely died. [chuckle] And when her MacBook died, she kept the best composure of a speaker that was having the worst technical difficulties ever, and I was literally impressed at that moment 'cause that is not something that fits my DNA. I probably would have thrown some technology out some windows at that point. So with that I'd like to reintroduce Elle Waters. Elle, tell us a little bit about yourself.

EW: Thanks. Oh my gosh, I had forgotten all about that, [chuckle] that really painful episode, but that's really flattering. So, I am currently the Director of Strategy at a company called Simply Accessible. What that means in day to day life is that we work with a lot of different organizations, a lot of different companies, different sizes. And I tend to work with companies that are large enterprise companies facing some impossible deadlines for accessibility and large challenges. And I really enjoy the challenge of that and we work with designers, developers, and testers primarily, along with some management to be able to further the cause and help them understand how to be able to build accessible digital content.

Find the full transcript on Telerik Developer Network http://developer.telerik.com/content-types/podcast/accessibility-developers-user-story/

Accessibility a developer's user story

On this episode of Eat Sleep Code, guest Todd Motto talks about overcoming JavaScript fatigue. With dozens of new JavaScript frameworks, tools, package managers, and task runners in the ecosystem, how do developers decide on a framework and move forward with a project.

Find the full transcript on Telerik Developer Network

http://developer.telerik.com/content-types/podcast/overcoming-javascript-fatigue/

Ed Charbeneau: Hello, and welcome to Eat Sleep Code, the official Telerik podcast, I'm your host Ed Charbeneau and with me today is Todd Motto. Hi Todd.

Todd Motto: Hey Ed.

00:22 EC: Today we're gonna be talking about JavaScript fatigue. Todd, I brought you on the show today because you are a new team member for Telerik and you're working with JavaScript and Kendo UI, and I thought it'd be a great time to talk about overcoming JavaScript fatigue. And let's talk about that in a moment, but first let's do some introductions, tell us a little bit about yourself and what you do.

00:51 TM: Cool. Yeah, thanks for having me on the show. I'm a new member to the team as you mentioned. I'm over in England, I cover the developer advocate scene in the UK, and parts of Europe and hopefully a little bit further across the pond and over in the US. So yeah, I'm working on the Kendo UI side of things, we'll be diving into the NativeScript as well. There's also the React stuff, and Angular 1 and Angular 2 integrations, so I'll be heavily involved with. So, it's gonna be an exciting year.

02:12 EC: Yeah. Alright man, so we wanted to talk about JavaScript fatigue today. Let's kick it off by explaining what JavaScript fatigue even is.

02:26 TM: Yes. So I think… Well, at the moment, there's this JavaScript fatigue you could probably do a search for it on a Twitter search and get new tweets on it every minute. I think we're just in this JavaScript boom at the moment where there's so many frameworks, and so many new features and tooling, and libraries, and all this stuff that's happening daily and everybody is sort of recommending new things to do. The day before yesterday I was… I'd recently switched over from using Sublime Text to using Atom, and obviously everyone has their own favorite text editor, but everyone's sort of like, "Why don't you try this, why don't you try this, why don't you try this editor instead?" And it's the exact same thing that happens with the JavaScript scene. You might say, "Oh, I've just built this on Angular." And somebody will go, "Why didn't you do in this, why didn't you do it in React? Why didn't you do this? Why didn't you use Flux?" Do you know what I mean? It gives a developer, especially a new developer, to the community like somebody who's come from a jQuery background that builds website to then joining like a software engineering team that builds software in a browser, so web application side of things, to make a jump.

03:37 TM: And then there's this kind of "Which way do I go down?" The path used to be quite clear a couple of years ago, there used to be a couple of frameworks that were sort of the industry leaders and then everybody kinda got a bit smarter and said, "Oh, you know what? I'm actually going to create my own framework or my own version of this framework, and I'm gonna make it 100 times smaller, that's my aim." And then React came out, and then Angular 2 is on its way, and there's all the tooling associated with it. I think instead of just maybe five paths that we had a couple of years ago, we have got 500 paths, and then we've got all the tooling around it. So that's my nutshell definition of JavaScript fatigue, is which way do you go, then when you choose a path, you then go another 500 paths so you can choose either with build tools and back-ends, and web servers, and all this kind of thing.

http://developer.telerik.com/content-types/podcast/overcoming-javascript-fatigue/

Overcoming JavaScript Fatigue

On this special episode of Eat Sleep Code John Bristowe from the Telerik DevRel team interviews developers from Microsoft Build.

Build Day 1 Interviews

Jared Faris dives deep into the near future of the web with ES2016, Web Standards, Services Workers, and HTTP/2. It's an epic web episode you don't want to miss.

Where The Web Is Going In 2016

Eat Sleep Code is the Official Telerik Podcast (Telerik by Progress). On Eat Sleep Code you'll hear from industry pros and developers just like you. Topics include all things software development and upcoming tech.

Progress believes in giving back to the developer community and we do this by writing, speaking and staying in touch with the software development community.

Where The Web Is Going In 2016

Eat Sleep Code Podcast