FEX 技术周刊 - 2016/07/25

微信搜索『FEX』关注我们的公众号，及时获得最新资讯。

深阅读

Create Apps with No Configuration
https://facebook.github.io/react/blog/2016/07/22/create-apps-with-no-configuration.html
https://github.com/facebookincubator/create-react-app
Create React App is a new officially supported way to create single-page React applications. It offers a modern build setup with no configuration. 来自 React 官方的开发者配套开发工具，挺值得研究的。

Introducing Stack Overflow Documentation Beta
http://blog.stackoverflow.com/2016/07/introducing-stack-overflow-documentation-beta/?cb=1
“Together, we believe we can do the same thing for technical documentation that we did for Q&A.” Documentation is community-curated, example-focused developer documentation, based on the principles of Stack Overflow.

V8 Release 5.3
http://v8project.blogspot.jp/2016/07/v8-release-53.html
V8 version 5.3, which will be in beta until it is released in coordination with Chrome 53 Stable. V8 5.3 is filled will all sorts of developer-facing goodies, so we’d like to give you a preview of some of the highlights in anticipation of the release in several weeks.

Serverless Architectures
http://martinfowler.com/articles/serverless.html
Martin Fowler 大师的这篇划时代之作还在更新，最近 新增了 Serverless 架构的优缺点。

[译]作曲家与听众
http://efe.baidu.com/blog/composers-and-audiences/
用作曲家和听众来比喻当先前端界的框架、工具之风，呼吁大家在关注这些的同时 Web 技术本身能给用户带来的体验优化。这两个观点很棒：

• 用户一点也不关心你是怎么构建应用的，他们只关注：1）能用，2）流畅。
• 开发者需要更努力的学习 web 平台本身，而不是某种框架对其的抽象。web 开发者们能够少花一些时间在钻研流程、原理、以及抽象化上。这些东西对于日常构建和维护代码是很重要，但不能因此转移我们对最终服务用户的需求的关注

聊聊前端排序的那些事
http://efe.baidu.com/blog/talk-about-sort-in-front-end/ 各种引擎的排序是如何实现的

Exploring the Physical Web
https://medium.com/@urish/exploring-the-physical-web-without-buying-beacons-efae51e36c2e#.qdrxy3xeg
https://google.github.io/physical-web/
The Physical Web is still pretty new, but the basic idea is that the Physical Web lets you broadcast any URL to the people around you. Awesome, right? The Physical Web lets you anchor URLs to physical places by way of a BLE beacon, effectively allowing you to “park” a webpage, link to a file, etc., wherever you want. It’s kind of like putting your own “Pokémon Go” wherever you want for people to find — except without making them surrender all their data 😉

The History of the URL: Path, Fragment, Query, and Auth
https://eager.io/blog/the-history-of-the-url-path-fragment-query-auth/
https://eager.io/blog/the-history-of-the-url-domain-and-protocol/
学习下 URL 的历史，有助于我们更好地使用它。

选择一个 HTTP 状态码不再是一件难事
http://www.zcfy.cc/article/choosing-an-http-status-code-stop-making-it-hard-8211-racksburg-904.html
能不能有一种直观的决策树来让你快速确定你要用到的少数状态码，并将那些不相关的和废弃的状态码排除掉？答案就在此文。

工作五年，后面四年重复着第一年的活儿
http://www.barretlee.com/blog/2016/07/21/donnot-repeat-yourself/
胡子哥文中提到的问题挺值得关注的。赞这段：我喜欢用编程解决问题，只要是重复的事情，我一定会想尽办法简化，然后交给机器去做。我希望今年可以用程序解决更多的问题。

京东-我们是如何做好前端工程化和静态资源管理
https://mp.weixin.qq.com/s?__biz=MzIxMzExMjYwOQ==&mid=2651890600&idx=1&sn=19b9ae0fc7d547a19914b90f1f04d479
来自京东的实践，做的还蛮不错的。这是他们产出的工具 https://github.com/o2team/athena ，感兴趣的同学可以研究。

Facebook iOS App技术演化十年之路
http://mp.weixin.qq.com/s?__biz=MjM5MDE0Mjc4MA==&mid=2650993357&idx=1&sn=51683b149e4c29e0095a33161511cafb
文尾总结三了点。首先，大家要做App，第一肯定需要壳，里面的信息视情况而定。其次是Mobile里面要做一些优化。最后，至于React Native，Facebook没有用，大家要保持非常警惕的心态。

How To Use Arguments And Parameters In ECMAScript 6
https://www.smashingmagazine.com/2016/07/how-to-use-arguments-and-parameters-in-ecmascript-6/
In this tutorial, we will explore arguments and parameters in detail and see how ECMAScript 6 has upgraded them. 另附：The Most In-Depth Yet Understandable ES6 Destructuring Tutorial

[译]使用VueJS 2.0开发一款app
https://github.com/DDFE/vue-blog/issues/1
非常详细的 vue 学习资料，可以顺着它了解下这个火热程度仅次于 Angular、React 的框架。

Angular 2: Why TypeScript?
https://vsavkin.com/writing-angular-2-in-typescript-1fa77c78d8e8#.pmhrzi4ov
TypeScript 有哪些优势

How Browsers will re-shape App Development with Progressive Web Apps
https://welance.de/journal/progressive-web-apps/
From browsers to native apps, and back to browsers again. Progressive web apps are about to unveil the true potential of modern browsers and new web standards. How did we get here?

React移动web极致优化
http://dev.qq.com/topic/579083d1c9da73584b02587d
手Q家校群做重构优化经验，使用了 React 进行重构。

聊一聊网页的分段传输与渲染那些事儿
https://segmentfault.com/a/1190000005989601
科普了 chunked 在前端的应用。

Mobile JavaScript Apps: The Dawn of React Native
http://thefullstack.xyz/react-native/
作者的观点是：The truth is that React Native is saving us JavaScript developers from continuing to create 2nd class mobile app experiences. From looking with envy at the amazing experiences native mobile developers are churning out, without even breaking a sweat. Web Platform evangelists may say React Native is not the hero JavaScript deserves. But I say React Native the hero JavaScript needs right now. React Native is the framework to which mobile JavaScript apps will be compared to from now on. Web or otherwise.

Android存储系统之架构篇
http://gityuan.com/2016/07/23/android-io-arch/
本文讲述Android存储系统的架构与设计，涉及到最为核心的便是MountService和Vold这两个模块以及之间的交互，主要从全局角度把握和剖析Android的存储系统。另附：A deep dive into Android View constructors，介绍了 Android view 构造函数。

图片之旅
http://blog.mrriddler.com/2016/07/20/%E5%9B%BE%E7%89%87%E4%B9%8B%E6%97%85/
详细分析了几种图片格式的原理

多屏互动——H5 中级进阶
https://segmentfault.com/a/1190000005988744
手把手介绍，用了重力感应和罗盘 API

Stack Exchange Network Status - Outage Postmortem
http://stackstatus.net/post/147710624694/outage-postmortem-july-20-2016
The direct cause was a malformed post that caused one of our regular expressions to consume high CPU on our web servers. 写正则一定要注意效率。

Server-side Web Components: How and Why?
https://scotch.io/tutorials/server-side-web-components-how-and-why
不过最近 Web Components 好像不火了

专访百度胡志广：百度日处理百亿PV的HHVM分析
http://geek.csdn.net/news/detail/90064
对比 HHVM 和 PHP7 等话题

Facebook的实时流处理技术
http://toutiao.com/a6309016645101732098/
本文介绍了Facebook在设计该系统时从易用性、性能、容错、可伸缩性以及正确性等方面考虑所做的重要设计决策，这些决策和系统如何满足秒级的延迟需求，以及在构建该系统的过程中Facebook所总结的经验教训。

新鲜货

Microsoft REST API Guidelines
https://github.com/Microsoft/api-guidelines/blob/master/Guidelines.md
The Microsoft REST API Guidelines, as a design principle, encourages application developers to have resources accessible to them via a RESTful HTTP interface. To provide the smoothest possible experience for developers on platforms following the Microsoft REST API Guidelines, REST APIs SHOULD follow consistent design guidelines to make using them easy and intuitive.

Running Node.js on the JVM
http://eclipsesource.com/blogs/2016/07/20/running-node-js-on-the-jvm/
Node.js is everywhere. But even with the rise of Node.js and popularity of JavaScript, Java continues to shine. Furthermore, few organizations can afford to migrate their entire platform from the JVM to Node.js. This means organizations must either continue with their current technology stack or run multiple stacks with networked APIs to communicate. Another option is to run Node.js and the JVM in a single process, and J2V8 finally makes this possible.

腾讯云TAB缘何一跃成为开发者新宠？
https://www.qcloud.com/
http://www.qcloud.com/blog/?p=1226
腾讯云联手 LeanCloud 推出移动开发工具TAB，号称：快速入门移动开发；无须关心基础设施；支持多平台接入；实时掌握应用动态；

HTTP_PROXY漏洞
https://httpoxy.org/
当你通过 CGI 模式连接后端与WebServer时，由于 RFC 3875(CGI) 规定所有HTTP Header均会加上HTTP前缀设置入系统环境变量中，因此一旦请求头中附带了 Proxy 字段，后端业务执行时就会使用指定的 Proxy 值作为环境变量 HTTP_PROXY 的值，进而导致所有后端对外的请求都会走指定的代理，那么通过代理就可以轻松的对后端服务内部业务进行嗅探与修改。当然这样的漏洞实施是有一些前提条件的，比如后端服务需要使用 CGI 模式，并且后端服务有外部可访问的接口依赖，如百度地图 Web API等等。

gitlab 员工手册
https://about.gitlab.com/handbook/
详细说明了内部的工作方式，很值得参考

weex&ReactNative对比
https://zhuanlan.zhihu.com/p/21677103
很详细的对比。 但仅供参考，技术选型是一个综合性问题，结合业务特点、团队状况进行合理的选型才是应有之路。

howler.js - Audio library for the modern web.
https://howlerjs.com/
howler.js makes working with audio in JavaScript easy and reliable across all platforms.

Create WebPage Screenshots with Node.js and SlimerJS
https://davidwalsh.name/slimerjs-screenshots
SlimerJS is very much like PhantomJS: a promise-based automation system that uses Firefox’s Gecko rendering engine instead of WebKit.

d4 — Declarative Data-Driven Documents
https://d4.js.org/
d4 is an experiment in using React to produce data-driven documents (ala d3) that are performant and understandable. This is not a library, but rather a demonstration that it’s possible (and preferable) to use React instead of the core of d3.

WebTask - All you need is code
https://webtask.io/docs/how
Run code with an HTTP call. No provisioning. No deployment.

Q2 Android WebView statistics
http://www.quirksmode.org/blog/archives/2016/07/q2_android_webv.html
Android WebView 版本碎片化真严重

Android 开发团队昨天搞了一次「微直播」，都和大家聊了啥？
http://sspai.com/34895
透露了许多关于 Android N 的话题，另外，Google releases final Android 7.0 Nougat preview

小团队也能做大系统？听技术布道师解读Cloud Native
http://funnytechnology.baijia.baidu.com/article/550244
文中提到的 Cloud Native 这个架构可关注

产品及其它

TOMsInsight-底层用户生态：差异化行为认知
http://mp.weixin.qq.com/s?__biz=MzA3NTcwOTIwNg==&mid=2655842763&idx=1&sn=9166646bb075a72ded69f30d31166d1f
这篇分析报告忽略最上层的互联网应用层面，从依次往下的终端行为、生活因素、精神消费三个因素所对应的角度（不同终端使用消费行为、互联网融入生活的方式、本地化的精神消费生活）来洞察底层用户生态的差异化行为认知。赞文末这段：互联网是我们实现自由梦想的途径，是我们创造自我价值的载体。我们需要站起来保护，为后人留下的我们的「英雄故事」，才能今生无悔。

IT人的巨流河
http://mp.weixin.qq.com/s?__biz=MzA3MDMwOTcwMg==&mid=2650004601&idx=1&sn=fc559a476537674b258d3b7f05599192
http://mp.weixin.qq.com/s?__biz=MzA3MDMwOTcwMg==&mid=2650004599&idx=1&sn=d09785c4d98d30607f3fad6f12f8d34f
对码农江湖地位的分享挺精辟的，赞这几点：

• IT超出了普通人生活经验，所以不容易理解
• IT在人类生活中扮演了非常重要的角色，但IT人员的能量并没有获得同等的重视
• IT人员本身有相对一致的工作方式
• IT人员的价值观通常比较健康
  如果只想把IT当成可替换的工种来使用，而不尊重IT自身的规律、不尊重这个领域的价值观、不尊重从业的人员，是很难真正从IT获益的。

另附相关文：创业、承诺以及技术人的困境

八年开心
http://weibo.com/ttarticle/p/show?id=2309403999974294686937
开心网的真实故事，这份坚持还是值得赞赏。这几点反思挺不错的：

• 优秀的团队，应该远大于个人能力之和
• 一件事做对了，应该忘记它往前看。再回头一看，就已经不是了。
• 成功者的错误逻辑：因为我是。。。所以做。。。我们就要。。。
  赞：胜也罢，败也罢，就是不要同他讲和！

傲慢与偏见之 - 轮到我们领先了
http://mp.weixin.qq.com/s?__biz=MzI0MjA1Mjg2Ng==&mid=2649866891&idx=1&sn=1795e487429295d7229e8b516aeca1c0
中国企业要想证实自己的全球竞争力，放下我们领先的傲慢和偏见，真心去研究不同地区的本地市场，真心去和当地的合作伙伴合作，去建立本地化团队，认真聆听客户的反馈和意见，在这个基础上，发挥中国公司资源，技术，团队的优势，我们才有机会，真正建立本地化的门槛和壁垒，切下最大的国家化蛋糕。