Readit NewsI think with majority of TypeScript projects using Prettier, 2 is more likely to be the default[0]
The linked page literally says to ignore it [1]
> STOP READING IMMEDIATELY THIS PAGE PROBABLY DOES NOT PERTAIN TO YOU > These are Coding Guidelines for Contributors to TypeScript. This is NOT a prescriptive guideline for the TypeScript community.
4 is a historical thing used as a default for all languages in VSCode [2]
[0] https://prettier.io/docs/options#tab-width
[1] https://github.com/microsoft/TypeScript/wiki/Coding-guidelin...
[2] https://github.com/Microsoft/vscode/issues/41200
Edit: found the TS style guide at https://github.com/basarat/typescript-book/blob/master/docs/... , it should be the correct link
P.S. did send a mail to author hopefully they fix it
They have since unrolled prod/dev db split and dB snapshots And restored that user's db from backup ofc
My nodejs projects have tests that run faster and have fewer breaking dependencies.
The two things I have to do are to always annotate type imports with type (I have a script for that), and to use file extensions on imports.
He has a very distinctive style and large amount of training data from all the reviews and emails he made while collaborating on Linux
And as he manages a huge project that's in development for decades, he has to be very strict about the quality
Add a "Check for updates" button that redirects to chamgelog page in browser for extra points
I'll take a look at improving rendering embedded font support. And that's a neat idea to be able to download it for offline, I'll give some thought to that. Appreciate your feedback!
PWAs are basically "installable" pages which open in their own browser window and generally can work offline
[1] https://developer.mozilla.org/en-US/docs/Web/Progressive_web...
Otherwise half of threads will be about Nazis by Godwin's law [0]
Like this one ¯\_(ツ)_/¯
My programmer brain immediately jumped away in disgust.
I'm sure there's many good reasons for choosing those, but it seems to me it could have easily have been done with 3 percentages (0-100% for the 3 numbers). Way easier to work with programmatically.
Chroma cap is dependent on Lightness and Hue, so it has to be unsized to preserve "equal delta leads to equal color distinction" concept
In color spaces you just don't have any math that can be done without following its structure
You may check https://oklch.com/ on how the color space looks like
You probably barely remember anything up to around 10, and then each doubling of age adds one logarithmical unit
So 10 is 1, 20 is 2, 40 is 3 and 80 is 4 (or maybe 0, 1 and 2?)
20 is already half of life passed by -_-