Shawn Dempsey shwanton

I heard some points of criticism to how React deals with reactivity and it's focus on "purity". It's interesting because there are really two approaches evolving. There's a mutable + change tracking approach and there's an immutability + referential equality testing approach. It's difficult to mix and match them when you build new features on top. So that's why React has been pushing a bit harder on immutability lately to be able to build on top of it. Both have various tradeoffs but others are doing good research in other areas, so we've decided to focus on this direction and see where it leads us.

I did want to address a few points that I didn't see get enough consideration around the tradeoffs. So here's a small brain dump.

"Compiled output results in smaller apps" - E.g. Svelte apps start smaller but the compiler output is 3-4x larger per component than the equivalent VDOM approach. This is mostly due to the code that is usually shared in the VDOM "VM" needs to be inlined into each component. The tr

Install and Create Emulators using AVDMANAGER and SDKMANAGER

TL;DR

For an emulator that mimics a Pixel 5 Device with Google APIs and ARM architecture (for an M1/M2 Macbook):

List All System Images Available for Download: sdkmanager --list | grep system-images
Download Image: sdkmanager --install "system-images;android-30;google_atd;arm64-v8a"

	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE keyboard SYSTEM "file://localhost/System/Library/DTDs/KeyboardLayout.dtd">
	<keyboard group="0" id="5000" name="QWERTY no option" maxout="1">
	<layouts>
	<layout first="0" last="0" modifiers="48" mapSet="312" />
	</layouts>
	<modifierMap id="48" defaultIndex="0">
	<keyMapSelect mapIndex="0">
	<modifier keys="" />
	</keyMapSelect>

	import { useMachine } from "@xstate/react/lib";
	import { assign, createMachine } from "xstate";

	import { uniqueId } from "lodash";
	import React from "react";

	import { makeMachineRoutable } from "./makeMachineRoutable";

	type PromiseContext<TData, TParameters> = {
	parameters?: TParameters;

	/*
	PUT THIS FILE IN ~/Library/KeyBindings/DefaultKeyBinding.dict
	This file remaps the key bindings of a single user on Mac OS X 10.5 to more closely
	match default behavior on Windows systems. This particular mapping assumes
	that you have also switched the Control and Command keys already.

	This key mapping is more appropriate after switching Ctrl for Command in this menu:
	Apple->System Preferences->Keyboard & Mouse->Keyboard->Modifier Keys...->
	Change Control Key to Command
	Change Command key to Control

	import { useEffect, useState } from 'react'
	import { API, graphqlOperation } from 'aws-amplify'

	const ListTalks = `
	query {
	listTalks {
	items {
	name
	description
	presenter {

	//
	// ABLLinkManager.swift
	//
	// Created by Cem Olcay on 5.03.2018.
	// Copyright © 2018 cemolcay. All rights reserved.
	//

	import Foundation
	import AVFoundation

	import React from 'react'
	import { withRouter, Link } from 'react-router-dom'
	import { graphql, compose } from 'react-apollo'
	import { Formik } from 'formik'
	import Yup from 'yup'

	import FormWideError from '../elements/form/FormWideError'
	import TextInput from '../elements/form/TextInput'
	import Button from '../elements/form/Button'
	import { H2 } from '../elements/text/Headings'

	{
	"global": {
	"check_for_updates_on_startup": true,
	"show_in_menu_bar": false,
	"show_profile_name_in_menu_bar": false
	},
	"profiles": [
	{
	"complex_modifications": {
	"parameters": {