| with recursive | |
| dims (r1, r2, i1, i2, s, it, p) as (values (-2::float, 1::float, -1.5::float, 1.5::float, 0.01::float, 100, 256.0::float)), | |
| sprites (s) as (values (st_makepolygon(st_geomfromtext('linestring (0 0, 0 1, 1 1, 1 0, 0 0)')))), | |
| n1 (r, i) as (select r, i from dims, generate_series((r1 / s)::int, (r2 / s)::int) r, generate_series((i1 / s)::int, (i2 / s)::int) i), | |
| n2 (r, i) as (select r::float * s::float, i::float * s::float from dims, n1), | |
| l (cr, ci, zr, zi, g, it, p) as ( | |
| select r, i, 0::float, 0::float, 0, it, p from n2, dims | |
| union all | |
| select cr, ci, zr*zr - zi*zi + cr, 2 * zr * zi + ci, g + 1, it, p from l where g < it and zr*zr + zi*zi < p | |
| ), |
This should make True Color (24-bit) and italics work in your tmux session and vim/neovim when using Alacritty (and should be compatible with any other terminal emulator, including Kitty).
Running this script should look the same in tmux as without.
curl -s https://gist.githubusercontent.com/lifepillar/09a44b8cf0f9397465614e622979107f/raw/24-bit-color.sh >24-bit-color.sh
type StringBool = "true"|"false";
interface AnyNumber { prev?: any, isZero: StringBool };
interface PositiveNumber { prev: any, isZero: "false" };
type IsZero<TNumber extends AnyNumber> = TNumber["isZero"];
type Next<TNumber extends AnyNumber> = { prev: TNumber, isZero: "false" };
type Prev<TNumber extends PositiveNumber> = TNumber["prev"];
| import { Fetch, Utils } from 'teambition-sdk' | |
| import { Observable } from 'rxjs/Observable' | |
| import { Subject } from 'rxjs/Subject' | |
| import { ReplaySubject } from 'rxjs/ReplaySubject' | |
| import { AjaxResponse } from 'rxjs/observable/dom/AjaxObservable' | |
| import { Subscriber } from 'rxjs/Subscriber' | |
| import * as config from 'config' | |
| export interface ChunkMeta { | |
| fileType: string |
Important: At the time of writing (2019-11-11) Immutable.js is effectively abandonware, so I can no longer recommend anyone to follow the advice given here. I'll leave the article here for posterity, since it's still getting some traffic.
Functional programming principles and with it immutable data are changing the way we write frontend applications. If the recent de-facto frontend stack of React and Redux feels like it goes perfectly together with immutable data, that's because it's specifically designed for that.
There's several interesting implementations of immutable data for JavaScript, but here I'll be focusing on Facebook's own Immutable.js, and specifically on one of i
git clone git://github.com/hilverd/vagrant-ubuntu-oracle-xe
| // Author: Nathan B. Evans | |
| // Twitter: @nbevans | |
| // Blog: http://nbevans.wordpress.com/2014/03/13/pbkdf2-hash-function-for-fsharp/ | |
| // License: MIT | |
| module Crypto.Pbkdf2 | |
| open System | |
| open System.Security.Cryptography | |
| let private subkeyLength = 32 |
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real