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

业界会议

W3C中国10周年大会 - 2016.07.09
http://www.w3ctech.com/event/58
期待演讲资料早日放出来

深阅读

React & Npm 组件库维护
http://mp.weixin.qq.com/s?__biz=MzIzMzEzODYwOA==&mid=2665284706&idx=1&sn=ec14150963c7071b93784971f6055f6f
介绍了百度 FEX 的 React 实践经验。

Make the Web Work For Everyone
https://hacks.mozilla.org/2016/07/make-the-web-work-for-everyone/
Millions of websites have compatibility problems on one or more of the major browsers, leading to a poor user experience. The web developer community can fix this. So, developers, here are a few things to inspire you to make your next web site work for everyone.

强迫症的模块化
http://efe.baidu.com/blog/an-obsessive-view-on-modularization/
观点比较偏激,但技术需要自我突破。

You Don’t Need Js
https://github.com/NamPNQ/You-Dont-Need-Javascript
CSS is powerful, you can do a lot of things without JS. 只用 css 可以做到什么?

A Front End Developer is Aware
https://css-tricks.com/front-end-developer-aware/
Because the front end developer is this central hub position and dealing with lots of different people doing lots of different jobs, the job can be done better if they are aware. Aware of everything else that makes a website tick.

Babel for ES6? And Beyond!
https://www.h5jun.com/post/babel-for-es6-and-beyond.html
Babel 并不仅仅是作为将 ES6 编译成 ES5 的工具,或者处理 JSX 的替代工具,事实上它几乎可以将 ES6 代码转换为任何结构语言。因此,在很多情况下我们可以拿它来做非常神奇的事情。

ES6 for Humans
https://github.com/metagrover/ES6-for-humans
结合实例用通俗易懂的方式介绍 ES6 的各种特性。另附: ES5 Objects vs. ES6 Maps – The differences and similarities

How well do you know CSS display?
https://www.chenhuijing.com/blog/how-well-do-you-know-display/
The display property is one of the most important CSS properties we use for layout. Most of us would have used block, inline and none. table and inline-block are also quite common. The new darling is definitely flex, because it’s a display property that was created specifically for layout. The upcoming grid (currently still being actively worked on) is another layout-specific property that we’ll soon have in our arsenal as well.

LambCI -Serverless continuous integration
https://github.com/lambci/lambci
https://medium.com/@hichaelmart/lambci-4c3e29d6599b#.t0gbduor6
A continuous integration system built on AWS Lambda. 最近 servreless 和 lamda 挺火的,相关文章 Create A Simple Twitterbot with AWS Lambda and Node

[译]如何部署软件
https://blog.coding.net/blog/deploying-software
https://zachholman.com/posts/deploying-software
This is a long — sorry not sorry! — written piece specifically about the high-level aspects of deployment: collaboration, safety, and pace. There’s plenty to be said for the low-level aspects as well, but those are harder to generalize across languages and, to be honest, a lot closer to being solved than the high-level process aspects.

一个靠谱的前端开源项目需要什么?
https://segmentfault.com/a/1190000005859766
看看你有哪些不知道的

JavaScript web frameworks trends for 2016
https://rebelliard.com/blog/javascript-web-frameworks-trends-2016
基于 Google Trends 的分析,可以发现 React 在国内明显比美国要火很多

Beyond Console Debugging Tricks
https://medium.com/outsystems-experts/beyond-console-debugging-tricks-f7d0d7f5df4#.firrfuthj
调试技巧汇总

性能测试应该怎么做
http://coolshell.cn/articles/17381.html
性能测试是一个挺复杂的问题的,它和监控一起,是性能技术方案落地的依据。这点总觉得挺不错的:性能测试要统一考虑这么几个因素:Thoughput吞吐量,Latency响应时间,资源利用(CPU/MEM/IO/Bandwidth…),成功率,系统稳定性。耗子哥还提供了一个关于讨论平均值的文章 http://apmblog.dynatrace.com/2012/11/14/why-averages-suck-and-percentiles-are-great/

百度移动端首页前端速度那些事儿
https://segmentfault.com/a/1190000005882953
秒开是百度首页的基本要求,这个文章介绍了如何综合利用各种技术优化访问速度。

今日头条架构演进之路
http://mp.weixin.qq.com/s?__biz=MzAwMDU1MTE1OQ==&mid=2653547520&idx=1&sn=f303a6250eb68775e9b6dbbdea6b9f06
从架构的角度,技术团队应对的压力最主要来自三方面:
- 服务稳定性。接口的稳定性,让服务更可靠;
- 迭代速度。迭代速度对于大公司来讲相对没那么重要,规模比较大,生存压力相对小一点,但相对中型小型公司来讲,迭代速度是必须要保证的,时间窗也是一个决定能否成功的重要因素;
- 服务质量。主要关注用户满意度,它也是一个特别重要的 topic。

Web缓存知识体系
http://mp.weixin.qq.com/s?__biz=MzA4Nzg5Nzc5OA==&mid=2651660745&idx=1&sn=9c8293278e018b82b70d7c73049e3878#rd
总结得还挺全面的,缓存是一种思想,它可以用在很多地方,起到四两拨千斤的效果。

R语言为量化而生
http://blog.fens.me/r-finance/
大数据正逐步应用在产品研发的各个环节中,作为该领域使用范围较广的一门语言,还是值得研究的。这个 bolg 中有不少学习资源。

[译]来自于编程大师的职业建议:别老想着写码
http://www.zcfy.cc/article/don-039-t-just-code-career-advice-from-the-programming-masters-javaworld-668.html
年轻人不要把时间都荒废在玩电脑上和研究代码有几种写法上去,你们应该多接触跟人类相关的各种知识,比如历史、文学和艺术啊什么的;真正优秀的程序员是那些专注于认识、理解、沟通和解决问题的人,你得明白,软件只是用来增加效率的工具而已;语言可以影响编程的思维,所以学习多种语言是一件很必要的事情,不同的语言有不同的处理方式;在写码之前,你就应该想好你要做些什么,你想要达成怎样的效果,然后通过哪些方法去做,做的更好;另附:我从编程总结的 22 个经验

API 杂谈
http://36kr.com/p/5049025.html
API 设计看似简单,很多道理大家都懂,但要结合业务场景设计高质量的 API 还是需要花很多心思的。一套成熟的 API,很多时候都是不断演化迭代出来的,很少有 API 的设计和实现从最开始就是完美无瑕疵的,说说自己做 API 的一些体会吧

如何从菜鸟成长为架构师
http://blog.2baxb.me/archives/1578?n
从学习、思考、实践三个维度分享了经验,赞这句:架构师(和其它很多)的工作中最重要的部分是实践,夸夸其谈很容易,与其拽一些技术名词,不如把你正在做的系统真正的做好。

新鲜货

ESLint v3.0.0 released
http://eslint.org/blog/2016/07/eslint-v3.0.0-released
We just pushed ESLint v3.0.0, which is a major release upgrade of ESLint. This release adds some new features and fixes several bugs found in the previous release. This release also has some breaking changes, so please read the following closely.

Node v6.3.0
https://nodejs.org/en/blog/release/v6.3.0

CLI Love: How to Write Better CLI Tools with Node.js
https://www.crowdcast.io/e/node-cli/
感兴趣的同学届时可以围观这个直播

React Native 高质量学习资料汇总
http://www.jianshu.com/p/454f2e6f28e9

jQuery 3.1.0 Released
http://blog.jquery.com/2016/07/07/jquery-3-1-0-released-no-more-silent-errors/ 修复了 ready 在异常处理方面的问题: http://blog.bugsnag.com/a-warning-about-jquery-3

CloudRail 统一第三方 api 管理
https://cloudrail.com/
提供了全平台的第三方服务例如 SMS,Email,Cloud Storage 等,懒人的一站式服务。

FIT 可视化拖拽网页生成器发布了
http://fit.baidu.com/components/pc/gaea
http://fit.baidu.com/designer
给出了这个平台的 npm 安装方式以及 DEMO。

whistle - 跨平台(Win/Mac/Linux)的 Fiddler
https://segmentfault.com/a/1190000005882861
基于 Node 写的类似 Fiddler 功能工具

VS Code 1.3
https://code.visualstudio.com/Updates
一个月就能有那么多更新

ES8提议
https://github.com/sirisian/ecmascript-types
选择 typescript 是个明智的决定,不论这个草案是否能够施行。

Typescript Optinal class
https://github.com/Microsoft/TypeScript/pull/8625
https://github.com/Microsoft/TypeScript/wiki/Roadmap
ts class 可选类型在 2.0 见面,并且 2.1 也解决了众多痛点,真佩服微软的语言设计能力。

High Performance Browser Networking
https://hpbn.co/
Performance is a feature. This book provides a hands-on overview of what every web developer needs to know about the various types of networks (WiFi, 3G/4G), transport protocols (UDP, TCP, and TLS), application protocols (HTTP/1.1, HTTP/2), and APIs available in the browser (XHR, WebSocket, WebRTC, and more) to deliver the best—fast, reliable, and resilient—user experience.

Horizon: A Scalable Backend Perfect for JavaScript Mobile Apps
https://www.sitepoint.com/horizon-a-scalable-backend-perfect-for-javascript-mobile-apps/
Horizon is a scalable backend for cross-platform, JavaScript based mobile apps, especially those needing realtime functionality. It was built by the awesome people at RethinkDB and so uses RethinkDB as the default database. Horizon exposes a client-side API that allows you to interact with the underlying database. This means you don’t have to write any backend code. All you have to do is spin up a new server, run it and Horizon will take care of the rest. Data is synced between the server and the connected clients in realtime.

np - A better npm publish
https://github.com/sindresorhus/np

zingtouch
https://zingchart.github.io/zingtouch/
A JavaScript gesture detection library for the modern web. ZingTouch provides six standard gestures that are completely customizable.

Latest Editor’s Draft of HTML 5.2 Released
http://w3c.github.io/html/

产品及其它

Excel 到底有多厉害
http://www.zhihu.com/question/27588491/answer/90603436
Excel究竟有多厉害?它跟任何一个图灵完备的语言都是图灵等价的,所以它们都一样厉害。你可以理解成,凡是其他图灵完备的语言(比如,C语言)能做的,Excel在理论上都能做。所以,能用Excel做出游戏来并不奇怪。甚至你用Excel实现一台虚拟机应该也是可以的。

Facebook 设计总监:我的产品设计年度总结
http://www.geekpark.net/topics/215993
从设定框架、执行、制定成功标准等维度进行了分享,赞:一个产品能获得成功,是因为它真正帮人们解决了某个问题。在试图带来创新之前,先好好想明白你要为谁、为什么解决问题。任何解决的方案都应该建立在对这两个点极其清晰的思考上。尽可能在最短的时间内得出最可信的结论。执念于某个问题的团队,比起执念于某种特定解决方案的团队,更容易成功。

人工智能前沿技术与产业发展趋势
http://mp.weixin.qq.com/s?__biz=MzI3MTA0MTk1MA==&mid=2651984482&idx=2&sn=3abfa4b0378afbabdc9629f6d5f78afb
清华大学计算机系教授关于这个行业的分析,可以了解下。

暴雪游戏开发趣闻 (若干则)
http://gulu-dev.com/post/2016-07-03-blizzcon2015-talks
工程师们不会随便说“这不行”;设计师的目标是“让尽可能多的玩家获得最好的体验”,工程师的目标是“尽量不要让任何人有糟糕的体验” ;解决设计问题的时候,他们考虑的最多的不是解决方案,而是对玩家实际体验的影响。

他只改了2个字,让腾讯避免了灭顶之灾
http://mp.weixin.qq.com/s?__biz=MzA5NzAzMjIxMw==&mid=2650924546&idx=1&sn=294739a6f43a7e83c58dcce67c431666
封闭 -> 开放,看似简单,但对一个公司来说还是很艰难的,腾讯做到了,其实微软也做到了。

作者:nwind (http://wuduoyi.com/) - 我的文章禁止未经许可全文拷贝转载,未经许可只能转载 1/10 的内容