叉叉咖 halftrue

I've been deceiving you all. I had you believe that Svelte was a UI framework — unlike React and Vue etc, because it shifts work out of the client and into the compiler, but a framework nonetheless.

But that's not exactly accurate. In my defense, I didn't realise it myself until very recently. But with Svelte 3 around the corner, it's time to come clean about what Svelte really is.

Svelte is a language.

Specifically, Svelte is an attempt to answer a question that many people have asked, and a few have answered: what would it look like if we had a language for describing reactive user interfaces?

A few projects that have answered this question:

This API was removed in React 17

Interaction tracing with React

React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".

With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.

libdispatch efficiency tips

The libdispatch is one of the most misused API due to the way it was presented to us when it was introduced and for many years after that, and due to the confusing documentation and API. This page is a compilation of important things to know if you're going to use this library. Many references are available at the end of this document pointing to comments from Apple's very own libdispatch maintainer (Pierre Habouzit).

My take-aways are:

You should create very few, long-lived, well-defined queues. These queues should be seen as execution contexts in your program (gui, background work, ...) that benefit from executing in parallel. An important thing to note is that if these queues are all active at once, you will get as many threads running. In most apps, you probably do not need to create more than 3 or 4 queues.
Go serial first, and as you find performance bottle necks, measure why, and if concurrency helps, apply with care, always validating under system pressure. Reuse

Swift Concurrency Manifesto

Author: Chris Lattner

Chinese Translation by Jason Yu

Usage

Execute pip3 install -r requirements.txt to install dependencies
Execute followers_clear.py and follow instructions.

Notes

Consumer keys can be found here. Use these keys instead of applying yourself can get rid of rate limit.

	// Created by Baye Wayly on 2020/3/13.
	// Copyright © 2020 Baye. All rights reserved.

	import SwiftUI

	struct Measure<Content: View>: View {
	@State var cost: TimeInterval = 0
	var content: Content

	init(@ViewBuilder builder: () -> Content) {

	i386 : iPhone Simulator
	x86_64 : iPhone Simulator
	arm64 : iPhone Simulator
	iPhone1,1 : iPhone
	iPhone1,2 : iPhone 3G
	iPhone2,1 : iPhone 3GS
	iPhone3,1 : iPhone 4
	iPhone3,2 : iPhone 4 GSM Rev A
	iPhone3,3 : iPhone 4 CDMA
	iPhone4,1 : iPhone 4S