diff options
Diffstat (limited to '_posts')
| -rw-r--r-- | _posts/2022-10-30-taxonomy-of-open-source.md | 5 | ||||
| -rw-r--r-- | _posts/2023-02-12-uuid-versions.md | 3 |
2 files changed, 3 insertions, 5 deletions
diff --git a/_posts/2022-10-30-taxonomy-of-open-source.md b/_posts/2022-10-30-taxonomy-of-open-source.md index cfe2a4e..895a22d 100644 --- a/_posts/2022-10-30-taxonomy-of-open-source.md +++ b/_posts/2022-10-30-taxonomy-of-open-source.md @@ -9,8 +9,7 @@ description: a list - license standards: bare minimum / give code back / don't be evil / be specifically good - how bills get paid: not users' problem / crowdfunding / selling support / we productized the hosting so if you also productize the hosting you're being a dick -<details> -<summary>for example</summary> +for example: - React is professionally maintained, owner-driven, PRs welcome, bare minimum, not users' problem - MongoDB is the same but give code back and we productized the hosting @@ -21,5 +20,3 @@ description: a list - anti-licenses are the secret fifth tier of license standards, Good Fucking Luck - some projects are actually community-driven but I can't think of one off the top of my head - most of my side projects are not maintained, owner-driven, view-only, Good Fucking Luck, and crowdfunding at the time they were written but currently not your problem. - -</details> diff --git a/_posts/2023-02-12-uuid-versions.md b/_posts/2023-02-12-uuid-versions.md index 9293056..52d5fde 100644 --- a/_posts/2023-02-12-uuid-versions.md +++ b/_posts/2023-02-12-uuid-versions.md @@ -17,11 +17,12 @@ in the early 90s, some UNIX people ran into this problem when drawing up their D the UUID format has two control fields and three data fields. the version field is pretty straightforward - it's 1 for UUIDv1, 2 for UUIDv2, etc. at this point, they only had 1 and 2, but they left room in the spec for up to 15 just in case. there's also a variant field, which says whether it's a normal UUID (`10`, hex value `8` through `b`) or some other bullshit that may or may not adhere to any of the rest of this spec. <details> - <summary>other bullshit</summary> +<aside> if the variant field is `0` then it's a UUID from Apollo Computer's Network Computing System, which had UUIDs before DCE but defined them in a slightly different way. if it's `110` then it's a UUID but the wrong endian, which Microsoft does sometimes when it makes UUIDs (it calls them GUIDs, because they're thinking too small, merely Global rather than Universal). if it's `111` then you're living in the future where they assigned a meaning to variant `111`. what's it like? how's the whole climate change thing going? +</aside> </details> the data fields are |