Hacker News post about this: https://news.ycombinator.com/item?id=39309783 (source available)
this post was submitted on 11 Feb 2024
303 points (98.4% liked)
Programmer Humor
32558 readers
557 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This doesn't actually read as serious TypeScript, moreso as someone trying to showcase unhinged code.
I'd be happy to be proven wrong with a link to the source code so that I can look the beast in the eye.
Take a look at some typescript libraries and frameworks and you will see stuff like this. Completely unreadable mess.
I have seen image recognition or text RPGs with type script types, but
const ok:true = true as Grid< 4, 9, 2Wtfnote that it continues onto the next line
Styled Components' type system is one of the most impressive and most fucked up things I've ever had to dive into.
For example?
Not OP, and these examples are not unreadable, but they are a few steps up from your typical generics.
https://effect-ts.github.io/effect/effect/Unify.ts.html#unify
https://effect-ts.github.io/effect/effect/Pipeable.ts.html
Creating basic functionality for the language always leads to unreadable code.
The C++ version would be much, much worse, and the Lisp version is Lisp.
Agree. What I linked provides core type support for that library. The pipe one is just a bunch of overloads to support a specific way of handling function composition to appease the TypeScript type checker.
There are a lot of typing hacks in that library to simulate higher kinded types.
Right to jail. Right now.