Home

2023.02.13 - A Historical Reference of React Criticism

Pi

Ping Xia

February 13, 20235 min read

Title: 2023.02.13 – A Historical Reference of React Criticism

GitHub’s new code search & AI journey & Electron 23 & 发心与立志 & 富贵与因果

This Week’s Highlights

A Historical Reference of React Criticismhttps://www.zachleat.com/web/react-criticism/
There have been a number of criticisms levied at the React project over the years, some of them handled and some of them still wavering in the wind. In this post, I’ll summarize the ones that are most prominent in my memory as a way of maintaining a record (primarily for my own use but maybe you’ll find it useful too). Related:

Future‑Proof Your Code: Top JavaScript Frameworks to Watch in 2023https://blog.greenroots.info/future-proof-your-code-top-javascript-frameworks-to-watch-in-2023
JavaScript is omnipresent. The web runs on JavaScript, and there are plenty to choose from. But how? Let's learn.

The evolution of Facebook’s iOS app architecturehttps://engineering.fb.com/2023/02/06/ios/facebook-ios-app-architecture/
FBiOS was never intentionally architected this way. The app’s codebase reflects 10 years of evolution, spurred by technical decisions necessary to support the growing number of engineers working on the app, its stability, and, above all, the user experience. Now, to celebrate the codebase’s 10‑year anniversary, we’re shedding some light on the technical decisions behind this evolution, as well as their historical context.

The technology behind GitHub’s new code searchhttps://github.blog/2023-02-06-the-technology-behind-githubs-new-code-search/
A look at what went into building the world’s largest public code‑search index.

An important next step on our AI journeyhttps://blog.google/technology/ai/bard-google-ai-search-updates/
AI is the most profound technology we are working on today. Whether it’s helping doctors detect diseases earlier or enabling people to access information in their own language, AI helps people, businesses and communities unlock their potential. And it opens up new opportunities that could significantly improve billions of lives. That’s why we re‑oriented the company around AI six years ago — and why we see it as the most important way we can deliver on our mission: to organize the world’s information and make it universally accessible and useful. Related:

In‑Depth Reading

Speeding up the JavaScript ecosystem – eslinthttps://marvinh.dev/blog/speeding-up-javascript-ecosystem-part-3/
Linting is the act of finding patterns in code that could lead to mistakes or ensure a consistent reading experience. It's a core piece of many JavaScript/TypeScript projects. We found lots of potential for time savings in their selector engine and AST conversion process and a perfect linter written in JS would be able to hit sub‑second run times.

Bringing JavaScript to WebAssembly for Shopify Functionshttps://shopify.engineering/javascript-in-webassembly-for-shopify-functions
While we’re working on getting our Shopify Functions infrastructure ready for the public beta, we thought we’d use this opportunity to shine some light on how we brought JavaScript to WebAssembly, how we made everything fit within our very tight Shopify Function constraints, and what our plans for the future look like.

A Gentle Introduction to CRDTshttps://vlcn.io/blog/gentle-intro-to-crdts.html
Conflict‑Free Replicated Data Types (CRDTs) can be tricky. You may spend months reading papers and implementing different algorithms before they finally click and become simple. Or they’ll seem simple at first and you’ll miss a bunch of nuance.

What Is API‑First Design?https://blog.postman.com/api-first-design-traits-postman/
An API‑first strategy involves leveraging APIs to save time and money and deliver maximum value. API‑first design can help organizations achieve that goal by improving the overall quality of their APIs. But what does API‑first design look like, and how does it relate to the API design‑first model? Let’s dive in.

Visual design rules you can safely follow every timehttps://anthonyhobday.com/sideprojects/saferules/
You do not have to follow these rules every time. If you have a good reason to break any of them, do. But they are safe to follow every time.

All Programming Philosophies Are About Statehttps://www.worldofbs.com/minimize-state/
What this shows is that every programming philosophy is about how to manage state, and each philosophy comes with trade‑offs. What this means is that there is no “one true way” to deal with state, and that each programming philosophy is useful and important in the correct domain. It also shows how important minimizing state is.

Three layers to secure a software development organizationhttps://stackoverflow.blog/2023/02/09/three-layers-to-secure-a-software-development-organization/
This affects the individual developer writing insecure code, the engineering team blindly trusting their dependencies, and the organization thinking that their best bet is to roll their own security controls.

Fresh Picks

Electron 23.0.0Google Touts Web‑Based Machine Learning with TensorFlow.js [Material React Table: A Full‑Featured React Table Component](Material React Table: A Full‑Featured React Table Componen) Ada: WHATWG‑compliant URL parser written in modern C++Yup: Dead‑simple object schema validation

Go: Profile‑guided optimization previewWhy We’re Rebuilding The Thunderbird Interface From Scratch

Products & Others

My Fifth Year as a Bootstrapped Founderhttps://mtlynch.io/solo-developer-year-5/
In this post, I’ll share what I’ve learned about being a bootstrapped founder from my fifth year at it.

Software Capabilities Vs Featureshttps://alexturek.com/2023-02-10-software-capabilities-vs-features/

(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.