| export class Cache<T extends object, K> { | |
| items = new WeakMap<T, K>() | |
| get<P extends T>(item: P, cb: (item: P) => K) { | |
| if (!this.items.has(item)) { | |
| this.items.set(item, cb(item)) | |
| } | |
| return this.items.get(item)! | |
| } |
| (fn gl -> | |
| :dbg.stop_clear() | |
| repr = fn | |
| %Phoenix.LiveView.Socket{} -> "socket" | |
| v -> inspect(v) | |
| end | |
| {:ok, _} = | |
| :dbg.tracer( |
| let Uploaders = {} | |
| Uploaders.S3 = function (entries, onViewError) { | |
| entries.forEach(entry => { | |
| let xhr = new XMLHttpRequest() | |
| onViewError(() => xhr.abort()) | |
| xhr.onload = () => (xhr.status === 200 ? entry.done() : entry.error()) | |
| xhr.onerror = () => entry.error() | |
| xhr.upload.addEventListener("progress", event => { | |
| if (event.lengthComputable) { |
Various search databases and backends as alternatives to Elasticsearch.
But they all have issues (vegan, gluten intolerance, peanut allergy) So they all went to the bar -> examples of constraints : making people happy is the objective, you adapt to the constraints
Constraints makes us more creative : Mihaly Csikszentmihaly Nietzsche : "Dancing in chains"
DevOps started out as "Agile Systems Administration". In 2008, at the Agile Conference in Toronto, Andrew Shafer posted an offer to moderate an ad hoc "Birds of a Feather" meeting to discuss the topic of "Agile Infrastructure". Only one person showed up to discuss the topic: Patrick Debois. Their discussions and sharing of ideas with others advanced the concept of "agile systems administration". Debois and Shafer formed an Agile Systems Administrator group on Google, with limited success. Patrick Debois did a presentation called "Infrastructure and Operations" addressing
I’m currently working (I’m just at the beginning, and I’m quite slow) on a personal project that will use Keepass files (kdb and kdbx).
I tried to find some documentation about .kdb and .kdbx format, but I didn’t find anything, even in the Keepass official website. I you want to know how these file formats are structured, you must read Keepass’s source code. So I wrote this article that explains how Keepass file format are structured, maybe it will help someone.
| #!/usr/bin/env ruby | |
| ### | |
| # This utility adds missing parentheses to single word function calls | |
| # that are now treated as warnings on Elixir 1.4. | |
| # | |
| # Download this file on your project repo and execute | |
| # ruby ex14parens.rb --help | |
| #### | |
| require('fileutils') |
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
| defmodule StageInspector do | |
| alias Experimental.{GenStage} | |
| use GenStage | |
| def init(type) when type in [:consumer, :producer_consumer] do | |
| {type, type} | |
| end | |
| def handle_events(events, _from, state = :consumer) do | |
| Enum.each events, &inspect_event/1 |
