| // GQL API docs => https://developers.cloudflare.com/analytics/graphql-api/ | |
| // tldr; => POST https://api.cloudflare.com/client/v4/graphql | |
| const requestBody = { | |
| query: ` | |
| query RequestsAndDataTransferByHostname($zoneTag: string, $filter: filter) { | |
| viewer { | |
| zones(filter: {zoneTag: $zoneTag}) { | |
| healthCheckEventsAdaptiveGroups(limit: 10000, filter: $filter) { | |
| dimensions { |
| #!/usr/bin/env bash | |
| function p() { | |
| jq -n \ | |
| --arg content "$*" \ | |
| '{ | |
| "model": "pplx-7b-online", | |
| "messages": [ | |
| { | |
| "role": "system", | |
| "content": "Be precise and concise." |
| { | |
| "apc.activityBar": { | |
| "position": "bottom", | |
| "hideSettings": true, | |
| "size": 20 | |
| }, | |
| "apc.statusBar": { | |
| "position": "editor-bottom", | |
| "height": 22, |
- Must Read/Watch Basics About Real-Time Audio Programming
- "Real-time audio programming 101: time waits for nothing": http://www.rossbencina.com/code/real-time-audio-programming-101-time-waits-for-nothing
- Video: Fabian Renn-Giles & Dave Rowland - Real-time 101
- Rust Audio Top Level Website: https://rust.audio/
- Awesome Audio DSP Link List: https://github.com/BillyDM/Awesome-Audio-DSP
| *.md diff=markdown |
Smallest possible CSS-in-JS library.
- Try demo
- 178 bytes (minified and gzipped)
- Source code fits in a tweet
- Dynamic 4th generation styling
- "jsxstyle" interface
- Pure React — no side effects
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
| // Written by @iclanzan | |
| // All credit goes to him! | |
| // You create the reducer like this: | |
| // var reducer = createTimelineReducer('someName', someReducer, ['foo', 'bar']); | |
| // And then whenever an action of type `foo` or `bar` happens it calls `someReducer` and adds the result to the timeline. | |
| // Then to undo/redo you trigger an action of type `someNameUndo`/`someNameRedo`. | |
| var defaults = require('lodash/object/defaults'); | |
| var capitalize = require('lodash/string/capitalize'); |
Kris Nuttycombe asks:
I genuinely wish I understood the appeal of unityped languages better. Can someone who really knows both well-typed and unityped explain?
I think the terms well-typed and unityped are a bit of question-begging here (you might as well say good-typed versus bad-typed), so instead I will say statically-typed and dynamically-typed.
I'm going to approach this article using Scala to stand-in for static typing and Python for dynamic typing. I feel like I am credibly proficient both languages: I don't currently write a lot of Python, but I still have affection for the language, and have probably written hundreds of thousands of lines of Python code over the years.