| APB: Ansible Playbook Bundle (Ansible, Framework) | |
| FCOS: Fedora CoreOS (Red Hat, Host/Container OS) | |
| CRD: Custom Resource Definition (Kubernetes, Concept) | |
| CDK: Red Hat Container Development Kit (Red Hat, Tooling) | |
| DC: DeploymentConfig (Kubernetes, Concept, Tooling) | |
| OKD: Kubernetes distribution that powers Openshift Origin | |
| CNS: Container Native Storage (https://keithtenzer.com/2017/03/29/storage-for-containers-using-container-native-storage-part-iii/) | |
| PVC: PersistentVolumeClaim (https://kubernetes.io/docs/concepts/storage/persistent-volumes/) | |
| CSI: Container Storage Interface (Standard, Concept) | |
| RC: ReplicationController (Kubernetes, Framework) |
Security Advisories / Bulletins / vendors Responses linked to Log4Shell (CVE-2021-44228)
A couple of weeks ago I played (and finished) A Plague Tale, a game by Asobo Studio. I was really captivated by the game, not only by the beautiful graphics but also by the story and the locations in the game. I decided to investigate a bit about the game tech and I was surprised to see it was developed with a custom engine by a relatively small studio. I know there are some companies using custom engines but it's very difficult to find a detailed market study with that kind of information curated and updated. So this article.
Nowadays lots of companies choose engines like Unreal or Unity for their games (or that's what lot of people think) because d
J. S. Choi, 2022
All programmers must manipulate text; JavaScript programmers are no exception. Text manipulation often refers to specific characters, usually by their code points in hexadecimal – or by embedding the characters directly in source code.
| { | |
| "ignition": { | |
| "version": "2.0.0", | |
| "config": {} | |
| }, | |
| "storage": { | |
| }, | |
| "systemd": {}, | |
| "networkd": {}, | |
| "passwd": { |
| Service | SSL | status | Response Type | Allowed methods | Allowed headers |
|---|
These use separate document structures instead of HTML, some are more modular libraries than full editors
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
This is a pattern I use fairly frequently for administrative APIs. It's a sort of OAuth lite for non-public APIs that produces good quality tokens. Once you build it a few times, it's not any harder than using arbitrary basic auth in your APIs.
The client and the app share a secret, which is never transmitted across the wire. The client uses this secret to create an HMAC digest of a payload consisting of the current time and a random nonce value. The nonce is provided as the Basic Authorization user, and the resulting HMAC digest is provided as the Basic Authorization password.
A similar process is followed on the server side. The server uses the supplied nonce, its own time, and its own copy of the shared secret. It may want to check against several tokens across a small window of times to account for clock drift.