Lady of the Land @Lady@cat.family

i don’t ⁜like⁜ it but this is a situation where you just gotta bow to common practice

especially since i use a nonstandard 71‐char linelength

begrudgingly adopting 2‐space javascript in deno since you can just set up your own config file and run `deno fmt` if you have different spacing requirements

anyway you should use ᚴ for S so you don’t look like a nazi

it’s lice trjing tu write english lice this

that's not how we spell

honestly i have zero idea where anglophonic rune fanatics get their alphabet like i’m not sure they even realize the english and north germanic traditions are… different

why would you write english in runes using the bad S latter when you could write english in runes using the good S letter

for (
const nodeType of /** @type {(typeof NODE_TYPE.SECTION|typeof NODE_TYPE.HEADING|typeof NODE_TYPE.BLOCK)[]} */(
[
NODE_TYPE.SECTION,
NODE_TYPE.HEADING,
NODE_TYPE.BLOCK,
]
)
) { /* … */ }

this is one of those “things which are allowed in JavaScript which an ordinary language never would have allowed” moments

typescript didn’t seem to be able to handle my switch on false so here is what i’m doing instead

have you met me

✨compiler limitations✨

seems like a bad design approach if you ask me

seems to really like throwing errors for reasonable things i want to do, which does not make me want to not do those things, but does make me not want to use typescript

super not happy with typescript this second

this issue was opened in February and since it is blocking an entire class of quite reasonable code which the Ecmascript standard was specifically designed to support, one would think it would be a priority, however,

hey typescript fix your fuckin bugs people depend on your software

https://github.com/microsoft/TypeScript/issues/42887

“it’s my favourite time of day!” 😒

boosting for the twilight hour