Chrome Dev Summit 10.23-10.24

ReactiveConf 2017 10.25-27


V8 Release 6.3
V8 version 6.3, which is in beta until its release in coordination with Chrome 63 Stable in several weeks. V8 v6.3 is filled with all sorts of developer-facing goodies. This post provides a preview of some of the highlights in anticipation of the release.
附:V8 Today and in the Future.

Introducing the Chrome User Experience Report
We’re making the Chrome User Experience Report available to encourage performance and user experience improvements across the web. The report is a public dataset of key user experience metrics for top origins on the web. The initial release includes data from a sample of ten thousand origins and focuses on loading metrics, though we hope to expand coverage in future iterations.

Can You Afford It?: Real-world Web Performance Budgets
Performance budgets are an essential but under-appreciated part of product success and team health. Most partners we work with are not aware of the real-world operating environment and make inappropriate technology choices as a result. We set a budget in time of <= 5 seconds first-load Time-to-Interactive and <= 2s for subsequent loads. We constrain ourselves to a real-world baseline device + network configuration to measure progress. The default global baseline is a ~$200 Android device on a 400Kbps link with a 400ms round-trip-time (“RTT”). This translates into a budget of ~130-170KB of critical-path resources, depending on composition — the more JS you include, the smaller the bundle must be.

Coding with Clarity
Working code isn’t necessarily good code. Your code also needs to be easy to read, understand, and modify. It needs clarity, and to achieve that, it has to be organized well, with careful planning and proper separation of ideas taking place before you even open your code editor. Coding for clarity is something that separates the great developers from the merely good, and there are a few basic principles that can set you on that path.

The QUIC transport protocol: design and Internet-scale deployment
QUIC is a transport protocol designed from the ground up by Google improve the performance of HTTPS traffic. The chances are you’ve already used it – QUIC is deployed in Chrome, in the YouTube mobile app, and in the Google Search app on Android. It’s also used at Google’s front-end servers, handling billions of requests a day. All told, about 7% of global Internet traffic is now flowing over QUIC. There are three interesting aspects to the paper, that we can essentially divide into the Why, the What, and the How. How QUIC was built and evolved over time is an integral part of the story.

The Web Fundamentals Gap
There are no shortage of boot camps, courses, and resources to learn front-end development out there, but having interviewed a lot of the folks coming out of these boot camps, I think there is a serious under-appreciation of the importance of CSS and the fundamentals of JavaScript.

直达服务平台上的各个服务采用前端技术栈开发,但是并不跑在浏览器或 WebView 中,它舍弃了浏览器内核渲染,转而采用 Android 的原生渲染机制,也就是说,实际上是使用前端技术栈开发了一个原生应用,无论是渲染效率,还是系统能力的 API 丰富程度,都远远超出传统网页。

打造丝般顺滑的 H5 翻页库
百度 H5 团队在使用了流行开源的 H5 翻页库之后,结合自身的业务需要,开发出了平台运行时所需的 H5 翻页库,具有轻量级、高性能的特点。这篇文章讲述了在开发过程中遇到的一些问题和对应的解决办法。

EggBorn.js是采用Javascript进行全栈开发的最佳实践。EggBorn.js不重复造轮子,而是采用业界最新的开源技术,进行全栈开发的最佳组合。EggBorn.js前端采用Vue.js + Framework7 / Vue Router + Webpack,后端采用Koa.js + Egg.js,数据库采用mysql。

我在 Uber 这几年,做了很多系统稳定性及可扩展性的工作,也做了一些移动开发的工作,因此我对 Uber 端到端的技术栈还比较熟悉。在这里以我的经历为例跟大家分享一下如何快速地做一个稳定的端到端大型应用。


这个理念蛮不错的。Andrea Goulet 是 Corgibytes 的 CEO ,这家咨询公司主要承担应用的重构和现代化等项目。她曾经见识过各种各样破旧的系统、遗留的代码以及繁重的技术债,感觉人们都在以数字化的方式囤积各种“古董”。因此 Goulet 认为初创公司需要转变自己的心态,不要斥资积累技术债,而是要创造技术财;不应继续用老旧的代码将就,而应特意进行重构。她将通过本文介绍自己提出的新方法,以及将不可能变为可能的做法。

React 16 Release: What’s New?
In this article, we’ll highlight notable additions to ReactJS 16 and dabble into the archi