Polymer 2.4 release preps for version 3

Polymer v2.4 is out and it has some changes to prep you for what is coming in v3 (for example, template changes for components). However, if we assume that the v3 “Modulizer” does its job, you shouldn’t have to upgrade because moving your templates into the classes should be handled automatically later on.

The blog entry also covers some of the progress toward v3 and also mentions that there’s a new 3.0-pre.6 available now.

Polymer 2.4 released

Grid, grid, everywhere a grid, grid

Shop Talk Show podcast picked CSS grid as one of their “things” that will be big in 2018 web development just a few weeks ago and I’d have to say that I agree.

The noise level around grid is pretty darn loud right now and the resources for learning it are better than ever. If you haven’t already succumbed to Rachel Andrew’s examples and video tutorial before, then maybe Wes Bos’s new free course on CSSGrid.io will do the trick for you.

webpack v4 beta available

Sean T. Larkin tweeted about this a couple of weeks back, but at that time, webpack v4 was only an alpha. In it he touted some of the improvments which had been made to picking reasonable defaults (and thus requiring much less configuration), speed improvements, Uglify with ES2015 support, bundle sizes, etc.

Here’s his blog post that seems to cover all the material of his tweet storm as well as a call to action for testing out the beta: webpack 4 beta - try it today!

Protecting your user's data (a follow up)

The companion piece to the horror story I posted about NPM packages being used as a vehicle to steal your user’s passwords and credit card numbers has dropped.

In it the author lays out a variety of techniques for protecting yourself and your users via changes to your website (the main one being, isolate the code you use for login or credit card submission from all other code):

How to stop me harvesting credit card numbers and passwords from your site

New Polymer 3.0 preview available

If you know me, you know how convinced I am that Web Components is the future of how we build components in the browser; not React, not Angular, and not Vue. With that said, Polymer is just one vision of how we can fill in the various parts of Web Components and make them easier to build. But it’s a good one and I’ve used it myself successfully in a couple of projects now.

A few months back, the Polymer team announced that Polymer 3 wouldn’t be a huge rewrite of version 2 as much as it would be a repackaging. For example, they were going to abandon HTML Imports in favor of using NPM and webpack to handle JavaScript modules. At that time they dropped a really early preview of version 3 which did that and just the other day they released a new one. Here are some links to both of the relevant blog posts as well as a link to a getting started blog post kind of buried in the middle of the first blog post. I wanted to pluck it out in case you never looked at the one from last August.

Stack Overflow: The Brutal Lifecycle of JS Frameworks

This is another of what you see a lot at the end of one year and the beginning of the next, data mining of large data sets in order to glean insights into what has happened in the past and what is likely to happen in the future. In this case it’s Stack Overflow looking at the waxing and waning of JavaScript frameworks over a period of years based upon their own trend data for people asking and answering questions:

The Brutal Lifecycle of JavaScript Frameworks

DigitalOcean Currents Q4 2017 Presentation

DigitalOcean (the web hosting company, or infrastructure company, or whatever everybody wants to be called these days) apparently does a quarterly survey of developers and makes a presentation out of it. It’s actually the first time I think I’ve heard of it, but here’s the results: DigitalOcean Currents Q4 2017 At this time of year, everybody under the sun is doing year end retrospectives, surveys, and data mining to learn about 2017 and look forward to 2018.