Reach UI is an accessible foundation for React applications and design systems.
The three equally important goals are to be:
- Accessible
- Composable
- Stylable
| ;;; package --- Fix permissions for Emacs.app on macOS Catalina | |
| ;;; Author: Artem Loenko | |
| ;;; Mail-To: <artyom.loenko@mac.com> | |
| ;;; Commentary: | |
| ;;; Code: | |
| (defconst _default-emacs-app-plist-path "/Applications/Emacs.app/Contents/Info.plist") | |
| (defconst _temp-buffer-name "*fixing Emacs permissions*") | |
| (defconst _temp-buffer (get-buffer-create _temp-buffer-name)) | |
| (with-current-buffer _temp-buffer (erase-buffer)) |
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
| # Please see the script's new home: https://github.com/alphapapa/magit.sh |
| @echo off | |
| REM Make sure that the path to the script is correct! | |
| @bash -l -c "~/bin/gitkraken-wsl-bash.sh %*" |
| function ProviderComposer({ contexts, children }) { | |
| return contexts.reduceRight( | |
| (kids, parent) => | |
| React.cloneElement(parent, { | |
| children: kids, | |
| }), | |
| children | |
| ); | |
| } |
[9:13 PM] harry : @acemarke are people still going to need to add Connect components to their jsx to use a redux hook? i couldnt tell where that ended up
[9:13 PM] harry : didnt 100% grok the whole thing
[9:13 PM] acemarke : awright, lemme recap the issue
[9:13 PM] acemarke : :)
[9:13 PM] harry : sweet
[9:13 PM] acemarke : from the top
[9:13 PM] harry : i kinda got the gist of the zombie child thing too. not sure how a child actually subscribes before a parent, though
[9:14 PM] acemarke : (drat... I can already tell this is gonna be one of those chats I have to export to a gist because I'm about to write a lot)
[9:15 PM] acemarke : up through v4, there was a potential bug due to the timing of store subscriptions
[9:15 PM] acemarke : wrapper components subscribe in componentDidMount, which fires bottom-up
| animated.DialogOverlay = animated(DialogOverlay) | |
| animated.DialogContent = animated(DialogContent) | |
| function NewPostDialog({ date, show, onDismiss }) { | |
| const rootRef = useRef(null) | |
| const transitions = useTransition(show, null, { | |
| from: { opacity: 0, y: -10, blur: 0 }, | |
| enter: { opacity: 1, y: 0, blur: 8 }, | |
| leave: { opacity: 0, y: -10, blur: 0 }, |
| # Summary | |
| A few notes I took to see if I could use MacOS as Hypevirsor in a similar fashion to Linux | |
| I wanted to see how few addons were needed instead of using Parallels, Virtual Box, VM Fsion etc. | |
| The idea is to use QEMU, Hypervisor Framework (https://developer.apple.com/documentation/hypervisor) and some custom host networking. | |
| # Installations | |
| brew install qemu (For controlling Hypervisor Framework) | |
| brew install cdrtools (For making cloud init iso's) | |
| http://tuntaposx.sourceforge.net/download.xhtml (For customer tap based networking) |
| // TypeScript Fundamentals For JavaScript Developers | |
| /* | |
| Tutorial for JavaScript Developers wanting to get started with TypeScript. | |
| Thorough walkthrough of all the basic features. | |
| We will go through the basic features to gain a better understanding of the fundamentals. | |
| You can uncomment the features one by one and work through this tutorial. | |
| If you have any questions or feedback please connect via Twitter: | |
| A. Sharif : https://twitter.com/sharifsbeat | |
| */ |