recommended

1. React 16.1.0 is released

Github.com/facebook/re…

React 16.1.0 was released this week. Instead of releasing React to Bower, React uses unPkg to mirror UMD builds. Developers who rely on Bower for dependency management have no choice but to use the older version. In addition, this version also fixes the UMD build, exception global variable error; An interface for parent-child communication was added to the experimental React Call Return module.

2. Release of Node.js 9.1.0

Nodejs.org/en/blog/rel…

Node.js version 9.1.0 was released this week, integrating a number of commits; Notable changes include the NODE_OPTIONS environment variable starting to support –stack-trace-limit, OpenSSL updated to 1.0.2m, and 103 Early Hints status code for HTTP modules. The CONNECT event handler overflow vulnerability has also been fixed.

3. Annual summary of vue.js used by Gitlab

About.gitlab.com/2017/11/09/…

Gitlab has been using vue. js for more than one year and has a deeper understanding of the application development of vue. js. This article is Gitlab’s sharing of the feeling of using this year. Just like Scala, vue.js is not a one-shot deal, and when used correctly, it gives excellent experience feedback; In the past year, Gitlab has also encountered and tried to solve many problems. In the following chapters, the author discusses using VueX for state management, writing high-quality code, and improving application performance.

More and more

1. With ARCore and ARKit, what else can AR industry do?

36 kr.com/p/5091876.h…

The release of ARCore represents that AR technology has fully entered the C end, and the following will be a period of mutual promotion and updating of content and technology. Before the arrival of AR glasses, the mobile terminal is a platform that has to be done and deserves to be done well. I hope Google and Apple can maintain a healthy competitive relationship and bring technology with better experience to the public. Meanwhile, I hope developers can like AR and bring more valuable AR applications.

2. Horizontal comparison between OpenAPI and gRPC

medium.com/@timburks/o…

OpenAPI (formerly Swagger) is two different ways to build web apis, but if you have studied the two technical solutions, you will find that they have a lot in common, this article is about OpenAPI and gRPC in detail and comparison. OpenAPI is a language used to describe REST apis. It provides a standard API description format. By default, data interaction is based on HTTP and data is represented in JSON format. This normalization also makes schema-based code generation easier to implement. GRPC, which is derived from Google, also provides the interface description format. By default, it uses HTTP/2 for data interaction and uses Protocol Buffer as the data format, which is stricter than OpenAPI.

Why am I still using jQuery

Hackernoon.com/i-still-lov…

JQuery is synonymous with traditional development in modern Web development. Developers like to talk about TypeScript, ECMAScript 2015+, React, Vue. In this article, the author discusses why he continues to use jQuery. A lot of the complaints about jQuery are that it increases the size of the site, but jQuery is only 27KB at the moment, and distribution through CDN does not add to the site’s stress; JQuery’s helper methods can also help improve code writing efficiency and performance. I go on to discuss how to avoid bad code, how to write extensible jQuery code, how to integrate jQuery into other frameworks, and when to avoid using jQuery.

4. GraphQL technology stack roaming

Dev-blog.apollodata.com/the-graphql…

GraphQL has been open source for more than two years, and its ecosystem has grown exponentially, with hundreds of companies using GraphQL in production environments. This article is a summary of the GraphQL Summit 2017 talk. This paper first summarizes the special features of GraphQL, and then analyzes the practical skills and relevant open source projects in GraphQL development, such as caching, tracing, pattern splicing, etc.

5. Quantitative comparison between React Native and Native apps

Codeburst. IO/react – nativ…

By now, any mobile app developer has probably heard of React Native, an excellent cross-platform development solution open-source by Facebook; However, it may be difficult for many companies to make a proper choice between Swift Native development and React Native development. This paper compares React Native and Swift Native applications in a multi-dimensional, three-dimensional and quantitative way from theory to practice. The author uses Swift and React Native to implement a simple application, including common login, list, map and other functions, and then makes a quantitative comparison for each page from the perspectives of CPU, GPU, memory usage and so on. Finally, the author compares the advantages and disadvantages of React Native from various aspects.

6. How does BBC launch its website

Medium.com/bbc-design-…

This post is shared by Neil Craig, chief architect of the BBC Online Technology Committee, on how the BBC publishes most of their web pages on the Internet. BBC serves more than 230 countries and regions in the world. In order to ensure the user experience around the world, BBC has adopted a series of optimization strategies in its publishing process. It analyzes the total amount of resource requests and the number of concurrent requests, and divides the subordinate columns into different directories for different peak response. For users in different countries and regions, load balancing forwards them to different CDN or application servers and discriminates resources of different types.

7. How does ThinkJS 3.0 support TypeScript

zhuanlan.zhihu.com/p/31057738

ThinkJS 3.0 is a future-oriented Node.js framework with a Koa 2.0 kernel. 3.0 is modularized compared to 2.0, so that the kernel itself contains only the minimum amount of code necessary, not even enough to form a complete Web MVC framework, except for the Controller implemented in the kernel. View and Model are implemented as extension modules think-view and think-Model. The benefits of this implementation are also obvious. If my Web service is just a simple RESTful API, I don’t need to introduce the View layer. Keep your code light.