Chrome 59 Updates

When I updated my Chrome to the latest version I ended up on 59.0.3071.86 so I figured it was time to cover what’s new in Chrome 59. Here’s Google’s highlights for the browser itself. Native Notifications - Image Capture - Headless Chrome - And their companion video about updates to the Chrome Developer Tools.

Node.js 8 and NPM 5

I read through the information about NPM v5 the other day and I have to admit I found that it was all likely important stuff (that is, changes that needed to be made), but not particularly exciting. It seemed like things which would just make it behave a little better, work in a few more situations, or be a little bit faster: v5.0.0 That’s probably not a very charitable summation for something which was probably a lot of work to put together.

GraphQL (Baader-Meinhof Edition)

I never hear much about GraphQL but of course, it seems like it’s everywhere this week… New Toolsday Podcast on GraphQL GraphQL > Tune in this week to hear us ford through unfamiliar waters as we tackle GraphQL! We go through why you should get excited about this new way of dealing with APIs. GraphQL Back-end as a Service It had never occurred to me that with all the BaaS that exist out there (Firebase, Backand, Hood.

Google Talks About Dev Tools Improvements and More About WebAssembly

Google Also Does Animated Dev Tips It’s not just Umar Hansa who does animated Gifs of Chrome Dev Tool features, Google does some of their own for new features in this entry from their blog talking about several updates which will be coming in the near future to the Chrome Developer Tools: What’s New In DevTools (Chrome 60) Lin Clark: A Cartoon Intro to WebAssembly I did get to watch Lin Clark: A Cartoon Intro to WebAssembly | JSConf EU 2017 - YouTube in the last few days and it was, as promised based upon the number of people who linked to it, very very good.

React Videos Old (Not Really) and Very New

ReactConf 2017 Videos Here’s something old, well, older. Mid March isn’t that long ago, so if you missed the videos from React Conf 2017 or you’re new to working on React, here’s a smorgasbord of 35(!) videos from that conference up on YouTube: React Conf 2017 ReactEurope 2017 Videos But what if that’s old hat? After all, this is JavaScript, two months is the equivalent of 14 human years. Then you’ll be glad to know that there are now YouTube playlists up for ReactEurope 2017.

New Content and Some Contact Details

New Template If you’ve been here before then you can immediately tell that the look of things is completely different. I’m using Hugo right now to generate this site and I started with the Hyde template just to have something up but I quickly found it to be extremely limiting. I’ve now switched to Mainroad and other than the weirdness above where it uses the list of my last posts as a menu (something I’m very puzzled by) it does pretty much everything better than Hyde did.

All Modules All The Time

ES2015 Modules Although we’ve gotten basically everything else from ES2015 in our browsers (and you can and should be using it without having to run your code through Babel or TypeScript or anything else; IE11 be damned), we haven’t gotten modules. And lots of us really want modules. This is a really good overview of not just where the various browsers stand today with regard to modules (spoiler: widespread but most of the implementations are still turned off by default and you have to enable a flag to try them out).

Friday Podcasts and's New Course

New Podcasts from JavaScript Jabber, My JS Story, and JSParty JSJ 263 Moving from Node.js to .NET and with John-Daniel Trask This episode features Moving from Node.js to .NET and with John-Daniel Trask. John-Daniel is the Co-founder and CEO of Raygun, a software intelligence platform for web and mobile. He’s been programming for many years, and is originally from New Zealand. Tune in and learn what prompted them to move to the .

Why we're moving from X to Y

At work we have used AngularJS for four years now and really loved it. However, it seems like the handwriting is on the wall for the long term future of the framework. Google’s team for Angular originally seemed to hope that everyone would migrate from AngularJS to Angular 2/4/X organically and now they’ve stepped up their game on the homepage to push people toward the new one. From what I’ve seen so far, I think it’ll get a lot more pushy in the future if they don’t get to the point where the majority of traffic is to the new Angular site (which is where they’ve said in the past they would start to move away from 1.