| #!/usr/bin/env bash | |
| ### | |
| ## This mounts a (single) ephemral NVMe drive in an EC2 server. | |
| ## It's meant to be run once, within user-data | |
| ## For EBS drives (non-ephemeral storage), see: https://gist.github.com/jalaziz/c22c8464cb602bc2b8d0a339b013a9c4 | |
| # | |
| /// Adds a convenience initializer for loading scenes from framework targets. | |
| public extension GKScene { | |
| /// Loads the bundle-specific SpriteKit scene file, creating a GKScene object containing the SpriteKit scene and associated GameplayKit objects. | |
| /// - Parameters: | |
| /// - filename: The name of a scene file in the given bundle. | |
| /// - bundle: The bundle containing the scene file. | |
| /// | |
| /// - Returns: A new GameplayKit scene. | |
| /// |
| // Copyright © 2019 Ooma Inc. All rights reserved. | |
| import Foundation | |
| import RIBs | |
| import RxSwift | |
| // MARK: - Plugin | |
| public protocol Plugin: AnyObject { | |
| associatedtype Component = Dependency |
Hmm... I don't see any docs for 4.0 on https://webpack.js.org. I guess I'll just wing it.
All I need to do is npm i -D webpack@next, right?
+ [email protected]
sorted by rerender time
| Solution | Use CSS | Use Inline-Styles | Mount Time (ms) | Rerender time (ms) |
|---|---|---|---|---|
| react (without styles) | - | - | 16.11 | 29.96 |
| styled-jsx-static | + | - | 25.27 | 42.24 |
| emotion-extract-static | + | + | 52.29 | 44.79 |
| react-css | + | + | 28.17 | 46.18 |
| styletron | + | - | 53.03 | 47.36 |
Kong, Traefik, Caddy, Linkerd, Fabio, Vulcand, and Netflix Zuul seem to be the most common in microservice proxy/gateway solutions. Kubernetes Ingress is often a simple Ngnix, which is difficult to separate the popularity from other things.
This is just a picture of this link from March 2, 2019
Originally, I had included some other solution
| public struct TextSize { | |
| fileprivate struct CacheEntry: Hashable { | |
| let text: String | |
| let font: UIFont | |
| let width: CGFloat | |
| let insets: UIEdgeInsets | |
| fileprivate var hashValue: Int { | |
| return text.hashValue ^ Int(width) ^ Int(insets.top) ^ Int(insets.left) ^ Int(insets.bottom) ^ Int(insets.right) |
| import UIKit | |
| extension UIImage { | |
| // colorize image with given tint color | |
| // this is similar to Photoshop's "Color" layer blend mode | |
| // this is perfect for non-greyscale source images, and images that have both highlights and shadows that should be preserved | |
| // white will stay white and black will stay black as the lightness of the image is preserved | |
| func tint(tintColor: UIColor) -> UIImage { | |
A maintainable application architecture requires that the UI only contain the rendering logic and execute queries and mutations against the underlying data model on the server. A maintainable architecture must not contain any logic for composing "app state" on the client as that would necessarily embed business logic in the client. App state should be persisted to the database and the client projection of it should be composed in the mid tier, and refreshed as mutations occur on the server (and after network interruption) for a highly interactive, realtime UX.
With GraphQL we are able to define an easy-to-change application-level data schema on the server that captures the types and relationships in our data, and wiring it to data sources via resolvers that leverage our db's own query language (or data-oriented, uniform service APIs) to resolve client-specified "queries" and "mutations" against the schema.
We use GraphQL to dyn