Home

2018.11.05 - A Look at the Design of Lua

Pi

Ping Xia

March 21, 20225 min read

Title: 2018.11.05 – A Look at the Design of Lua

Industry Conferences

React Conf 2018 https://conf.reactjs.org/ Attachments: Conference Materials, React Conf recap: Hooks, Suspense, and Concurrent Rendering.

In‑Depth Reading

V8 release v7.1 https://v8.dev/blog/v8-release-71 V8 v7.1 is packed with all sorts of developer‑facing goodies. This post provides a preview of some of the highlights in anticipation of the release.

React Native – Open Source Roadmap http://facebook.github.io/react-native/blog/2018/11/01/oss-roadmap This year, the React Native team has focused on a large‑scale re‑architecture of React Native. As Sophie mentioned in her State of React Native post, we’ve sketched out a plan to better support the thriving community of React Native users and contributors outside of Facebook. It’s now time to share more details about what we’ve been working on. Before I do so, I’d like to lay out our long‑term vision for React Native in open source. Attachments: React Native Refactoring Roadmap Release.

Making Sense of React Hooks https://medium.com/@dan_abramov/making-sense-of-react-hooks-fdbde8803889 Hooks are an experimental proposal for React. You don’t need to learn about them right now. Also note that this post contains my personal opinions and doesn’t necessarily reflect the positions of the React team. Additional reading: What and How to Test with Jest and Enzyme.

An Annotated webpack 4 Config for Frontend Web Development https://nystudio107.com/blog/an-annotated-webpack-4-config-for-frontend-web-development As web development becomes more complex, we need tooling to help us build modern websites. Here’s a complete real‑world production example of a sophisticated webpack 4 configuration. Building a modern website has become custom application development. Sites are expected to do more than just serve as marketing pages; they now take on the functionality of traditional apps. Whenever a process becomes complicated, we break it down into manageable components and automate the build with tools. This is true whether we’re manufacturing cars, drafting legal documents, or building websites.

The Definitive TypeScript Guide https://www.sitepen.com/blog/2018/10/29/update-the-definitive-typescript-guide/ This article describes the features and functionality of TypeScript 3.1.

Splicing HTML’s DNA With CSS Attribute Selectors https://www.smashingmagazine.com/2018/10/attribute-selectors-splicing-html-dna-css/ Attribute selectors are magical. They can rescue you from sticky problems, help you avoid adding extra classes, and highlight issues in your code. Don’t worry—while attribute selectors are powerful, they’re easy to learn and use. In this article we’ll explain how they work and give you ideas for applying them.

Ke Jun: How to Become an Excellent Front‑End Engineer https://www.weibo.com/ttarticle/p/show?id=2309404300456787613157 Contains many growth‑oriented tips worth reading and practicing. Also see Ruan Yifeng’s piece: Software Development Is Like a Marathon—Save Your Best Form for the Most Important Race.

The Technical Evolution of Rich‑Text Editors https://mp.weixin.qq.com/s?__biz=MzU0Nzk1MTg5OA==&mid=2247484137&idx=1&sn=8dc25f8de7d359549520c9f198721408 Browsers provide two native features: contenteditable and document.execCommand(). The contenteditable attribute can turn a container into an editable region, allowing users to type or delete content directly inside it. The execCommand API can apply a command to a selected fragment—e.g., making it bold. With these, you can build the simplest rich‑text editor. Was it really that simple? Of course not! Additional reading: [Translation] Building a Text Editor for the “Digital‑First” Newsroom.

Atag – Web Components Best Practices http://taobaofed.org/blog/2018/10/31/a-tag/ Over the past few months I’ve been using Web Components to build the foundational component Atag for Taobao Mini‑Programs. This article aims to summarize the lessons learned while developing Atag with Web Components, helping others avoid common pitfalls. Additional reading: October 2018: A Big Month for Web Components.

Ant Financial Mobile Development Platform mPaaS https://juejin.im/post/5bd81cf2f265da0ab674096c Android containerization, changing the way aapt works.

Web Performance 101 https://3perf.com/talks/web-perf-101/ An introduction to modern web loading performance. Learn why performance matters, what optimizations exist, and which tools help you gauge whether your app is performing well.

You Might Not Need JavaScript http://youmightnotneedjs.com/ JavaScript is great, and you should use it when appropriate, but be aware that many functional UI components can be built without adding the extra dependency. You might get away with a few utility lines, a mixin, or none at all. If you’re targeting modern browsers, the native HTML and CSS capabilities (plus a bit of Sass sugar) may be sufficient—no scripts required.

Creating a QR Code Step by Step https://www.nayuki.io/page/creating-a-qr-code-step-by-step This JavaScript demo visualizes, in detailed steps, how a text string is encoded into a QR‑Code barcode symbol. The page also explains and justifies how my QR Code generator library works internally.

GraphQL – The Good and the Bad https://scotch.io/tutorials/graphql-the-good-and-the-bad GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. It provides a complete, understandable description of the data in your API and lets clients request exactly what they need—nothing more. It makes evolving APIs easier and enables powerful developer tools. At least that’s the common perception. In this post we’ll examine the wonderful aspects of GraphQL as well as the less‑popular “not‑so‑good” aspects. Additional reading: GraphQL Server Design @ Medium.

Best Practices for Setting SLOs and SLIs for Modern, Complex Systems https://blog.newrelic.com/engineering/best-practices-for-setting-slos-and-slis-for-modern-complex-systems/ At New Relic, defining and setting Service Level Indicators (SLIs) and Service Level Objectives (SLOs) is an increasingly important part of our Site Reliability Engineering (SRE) practice. It’s well known that SLIs and SLOs are crucial for high‑functioning reliability, but figuring out how to apply them in a real‑world, complex modern software architecture can be challenging—especially deciding what to measure and how. In this post we use a highly simplified version of New Relic’s architecture to walk through concrete, practical examples of defining and measuring SLIs and SLOs.

(content truncated)


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

Keep reading

More related articles from DriftSeas.