Péter Schmíz peterschmiz

Background

Recently I noticed that Safari 10 for Mac/iOS had achieved 100% support for ES6. With that in mind, I began to look at the browser landscape and see how thorough the support in the other browsers. Also, how does that compare to Babel and its core-js runtime. According to an ES6 compatability table, Chrome, Firefox, and IE Edge have all surpassed what the Babel transpiler can generate in conjunction with runtime polyfills. The Babel/core-js combination achieves 71% support for ES6, which is quite a bit lower than the latest browsers provide.

It made me ask the question, "Do we need to run the babel es2015 preset anymore?", at least if our target audience is using Chrome, Firefox, or Safari.

It's clear that, for now, we can't create a site or application that only serves ES6. That will exclude users of Internet Explorer and various older browsers running on older iOS and Android devices. For example, Safari on iOS 9 has pretty mediocre ES6 support.

Update (August 2016)

Please take a look at these updated instructions on Github to troubleshoot issues you have with Windows and Tessel 2.

The issue:

..mobile browsers will wait approximately 300ms from the time that you tap the button to fire the click event. The reason for this is that the browser is waiting to see if you are actually performing a double tap.

(from a new defunct https://developers.google.com/mobile/articles/fast_buttons article)

touch-action CSS property can be used to disable this behaviour.

touch-action: manipulation The user agent may consider touches that begin on the element only for the purposes of scrolling and continuous zooming. Any additional behaviors supported by auto are out of scope for this specification.

Lesson's learnt building the Guardian

Below is a collection of my favourite responses I gathered from Guardian engineers when asked the question: What have you learnt starting from scratch and building a mobile-first next generation web platform for the Guardian?

Daithi O Crualaoich

Work with great people.
Deploy like crazy. This means the team has to control the infrastructure as well as code.
Design is not a service. Designers have to sit in the team.
Infrastructure is intrinsically unreliable. Discard and replace is the robust strategy.
Use your CDN for HTML too.
Don't always do as you are told.

	using System.Web;
	using Sitecore.Diagnostics;
	using Sitecore.Resources.Media;
	using System;
	using System.Linq;
	using Sitecore.Data.Items;
	using Sitecore.IO;

	namespace MyProject.Custom.Media
	{

	<!DOCTYPE html>
	<html>

	<head>
	<title>Sine Wave</title>
	<script type="text/javascript">
	function showAxes(ctx,axes) {
	var width = ctx.canvas.width;
	var height = ctx.canvas.height;
	var xMin = 0;

	function getUrlParams(search) {
	const hashes = search.slice(search.indexOf('?') + 1).split('&')
	const params = {}
	hashes.map(hash => {
	const [key, val] = hash.split('=')
	params[key] = decodeURIComponent(val)
	})
	return params
	}

	<!DOCTYPE html>
	<html>
	<head>
	<title>HTML5 Web audio capture + Speech Recognition</title>
	<link href="http://www.smartjava.org/examples/webaudio-filters/css/bootstrap.css" rel="stylesheet"/>
	</head>

	<body>
	<div class="container">
	<h1 class="pagination-centered">HTML5 Web audio capture + Speech Recognition</h1><br />

	<canvas id= "c"> </canvas>
	<button id="reset">new colours</button>
	<div id="info">
	<div id="top">
	<a target="_blank" id="site" href="http://lonely-pixel.com">my website</a>
	<a id="close" href="">close</a>
	</div>
	<p>
	<br>
	- Alter particles/groups with the GROUPS variable.<br><br>