Jan Kodeš johnkodes
State machines are everywhere in interactive systems, but they're rarely defined clearly and explicitly. Given some big blob of code including implicit state machines, which transitions are possible and under what conditions? What effects take place on what transitions?
There are existing design patterns for state machines, but all the patterns I've seen complect side effects with the structure of the state machine itself. Instances of these patterns are difficult to test without mocking, and they end up with more dependencies. Worse, the classic patterns compose poorly: hierarchical state machines are typically not straightforward extensions. The functional programming world has solutions, but they don't transpose neatly enough to be broadly usable in mainstream languages.
Here I present a composable pattern for pure state machiness with effects,
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
| Emoji | Name | Text example |
|---|---|---|
| 🚀 | Rocket | You're up |
| 📦 | Package | Installing additional dependencies... |
| ⚓ | Hook | Running completion hooks... |
| 📄 | Document | Generating README.md... |
| 🎉 | Party | Successfully created project hello-vue. |
| 👉 | Next | Get started with the following commands: |
| ✔ | Tick | Task completed |
| ✨ | Magic | Assembling project... |
Foundation offers a Thread class, internally based on pthread, that can be used to create new threads and execute closures.
// Detaches a new thread and uses the specified selector as the thread entry point.
Thread.detachNewThreadSelector(selector: Selector>, toTarget: Any, with: Any)
// Subclass
class MyThread: Thread {
| RN < 0.50 - watchman watch-del-all && rm -rf $TMPDIR/react-* && rm -rf node_modules/ && npm cache clean && npm install && npm start -- --reset-cache | |
| RN >= 0.50 - watchman watch-del-all && rm -rf $TMPDIR/react-native-packager-cache-* && rm -rf $TMPDIR/metro-bundler-cache-* && rm -rf node_modules/ && npm cache clean && npm install && npm start -- --reset-cache | |
| RN >= 0.63 - watchman watch-del-all && rm -rf node_modules && npm install && rm -rf /tmp/metro-* && npm run start --reset-cache | |
| npm >= 5 - watchman watch-del-all && rm -rf $TMPDIR/react-* && rm -rf node_modules/ && npm cache verify && npm install && npm start -- --reset-cache | |
| Windows - del %appdata%\Temp\react-native-* & cd android & gradlew clean & cd .. & del node_modules/ & npm cache clean --force & npm install & npm start -- --reset-cache |
| class BlurryOverlayView: UIVisualEffectView { | |
| private var animator: UIViewPropertyAnimator! | |
| private var delta: CGFloat = 0 // The amount to change fractionComplete for each tick | |
| private var target: CGFloat = 0 // The fractionComplete we're animating to | |
| private(set) var isBlurred = false | |
| private var displayLink: CADisplayLink! | |
| override init(effect: UIVisualEffect?) { | |
| super.init(effect: effect) | |
| setup() |
This is my constantly updated CS:GO autoexec config. Changelogs can be found under revisions here
Put autoexec.cfg in ...\Steam\steamapps\common\Counter-Strike Global Offensive\csgo\cfg or take what you want from it and add to your autoexec config!
After the Wild West Simulator 2015 update, video.txt needs to be put in ...\Steam\userdata\<Steam3 ID>\730\local\cfg
| // | |
| // InfiniteScrollChart.swift | |
| // ChartsGallery | |
| // | |
| // Created by beader on 2022/11/3. | |
| // | |
| import SwiftUI | |
| import Charts |