2018.01.29

Title: 2018.01.29

Deep Reading

Chrome welcomes Speedometer 2.0! https://v8project.blogspot.jp/2018/01/speedometer-2.html The Blink and V8 teams welcome the recent release of the updated Speedometer 2.0 benchmark. Applying the original concept to a list of contemporary frameworks, transpilers and ES2015 features makes the benchmark a prime candidate for optimizations again. Speedometer 2.0 is a great addition to our real‑world performance benchmarking tool belt.

Firefox 58: The Quantum Era Continues https://hacks.mozilla.org/2018/01/firefox-58-the-quantum-era-continues/ In 2018, we’ll build on that incredible foundation, and in that spirit our next several releases will continue to bear the Quantum moniker. Let’s take a look at some of the new goodies that Firefox 58 brings. Also: Extensions in Firefox 59、Release Notes for Safari Technology Preview 48

A Component Dev Kit for Angular https://blog.angular.io/a-component-dev-kit-for-angular-9f06e3b4b3b4 The Angular CDK gives developers solid, well‑tested tools to add common interaction patterns with minimal effort. Also: Stable AngularJS and Long Term Support.

Where Is the Future of Front‑End Engineers? https://mp.weixin.qq.com/s?__biz=MzIzOTU0NTQ0MA==&mid=2247486819&idx=1&sn=90531d46d3ccfcc9e64d9c59b075cfb6 A front‑end engineer is first a programmer, and also a software engineer. They work closest to the user, handling human‑computer interaction and user experience. Although called “front‑end,” their scope is already quite broad. Looking ahead, I think front‑end work will keep both fragmenting and converging. Specialization has driven efficient collaboration since the Industrial Revolution, and that pattern will likely persist for a long time; convergence is driven by the same quest for efficiency. The split‑and‑merge dynamics will continue, but the core fundamentals probably won’t change dramatically.

Apple Releases iOS 11.3 Beta https://mp.weixin.qq.com/s?__biz=MzA3ODg4MDk0Ng==&mid=2651114169&idx=1&sn=a2e841247e8993ffe395b0263e3a2f9f Battery monitoring, optional throttling, new AR experiences, richer emojis. Also: ARKit 1.5 Now Available

WeexConf 2018 Practical Series Weex + UI、Weex Technical Evolution、Weex Technical Evolution Part 2

React and visual automata‑based programming https://medium.com/dailyjs/react-and-visual-automata-based-programming-c1d13e153cde This post consists of three parts. In the first one I’m telling about my journey to visual automata‑based programming. The second one shows the process of building a GUI using visual automata‑based programming. The code is written in JavaScript and React is used to render the view. The last part is a summary of my experience with state machines where I explain how they changed the way I think about state management.

The 2018 Web Developer Roadmap https://codeburst.io/the-2018-web-developer-roadmap-826b1b806e8d An illustrated guide to becoming a Frontend or Backend Developer with links to courses.

Project Guidelines https://github.com/wearehive/project-guidelines While developing a new project is like rolling on a green field for you, maintaining it is a potential dark twisted nightmare for someone else. Here's a list of guidelines we've found, written and gathered that (we think) works really well with most JavaScript projects here at Hive.

ECMAScript regular expressions are getting better! https://mathiasbynens.be/notes/es-regexp-proposals#legacy This article highlights what’s happening in the world of JavaScript regular expressions right now. Spoiler: it’s quite a lot — there are more RegExp‑related proposals currently advancing through the TC39 standardization process than there have been updates to RegExp in the history of ECMAScript! Also: Ruan’s ES6 RegExp tutorial.

An explanation of JavaScript’s weird type system https://medium.com/dailyjs/the-why-behind-the-wat-an-explanation-of-javascripts-weird-type-system-83b92879a8db In order to prevent developers from giving semi‑coherent, hand‑wavy explanations of why JS works the way it does (and of course to educate you, the reader), let’s dive into the Why behind the WAT.

JavaScript: The Bad Parts – A (biased) JSVM engineers’ perspective https://docs.google.com/presentation/d/1n5ZvVXyItjGNBFoQFh‑T04_UdOWcuOdvLC3e_udTjPQ/edit#slide=id.p

The building blocks of Web Workers + 5 cases when you should use them https://blog.sessionstack.com/how-javascript-works-the-building-blocks-of-web-workers-5-cases-when-you-should-use-them-a547c0757f6a We’ll be taking apart Web Workers: we’ll offer an overview, discuss the different types of workers, how their building components come to play together, and what advantages and limitations they offer in different scenarios. Finally, we’ll provide 5 use cases in which Web Workers will be the right choice.

Android native library merging https://code.facebook.com/posts/405334539915815/android-native-library-merging/ Android developers who use lots of C++ code might be familiar with the native library limit that existed in Android versions prior to 4.3. One solution is to manually combine multiple small libraries into one larger one. However, this usually is not a scalable solution. Combining libraries requires moving source code around and carefully managing compilation settings and dependencies. It can also make code less modular, which can be problematic if your organization is building multiple apps from a shared codebase.

Four lessons in making Pinterest faster on Android https://medium.com/@Pinterest_Engineering/four-lessons-in-making-pinterest-faster-on-android-5a3c69c045af This post will cover the four key lessons we learned that improve performance on Pinterest.

Cloud: IaaS vs PaaS vs SaaS vs DaaS vs FaaS vs DBaaS https://brainhub.eu/blog/cloud-architecture-saas-faas-xaas/ Maybe you’ve heard of some of the following: IaaS, PaaS, SaaS, DaaS, FaaS, DBaaS. If you are not a DevOps engineer, you’ve probably heard about some of these concepts but not all of them. Even if you have used some of them, you likely don’t know everything you should. You may have even used parts without knowing the name of the applied concept. So let’s take a closer look to gain a better understanding of what they really are.

A GraphQL Primer: Why We Need a New Kind of API https://www.smashingmagazine.com/2018/01/graphql-primer-new-api-part-1/ In this first article, rather than jumping into the implementation, I want to go over how and why we have arrived at GraphQL (and similar tools) by looking at the lessons learned.

---

Originally written by Ping Xia (平侠) and published in Chinese on Web技术周刊 (Web Tech Weekly). Translated and adapted for DriftSeas with permission.