News for hackers. Stuff that matters.
Re:ngn/k, an AGPL K interpreter by saagarjha on Friday January 10, 2020 @05:00AM (#22009831)
> I've spent a fair amount of time digging my teeth into it

I tend to label code that makes me do that "unreadable"; it's not that I literally can't read it (I routinely deal with worse) but it requires more effort than I consider reasonable for the medium it is presented in.

Re:ngn/k, an AGPL K interpreter by kick on Friday January 10, 2020 @05:04AM (#22009858)
"digging my teeth into it" wasn't meant to imply difficulty in any way, it was meant to imply depth: it's easier to read than most C codebases.
Re:ngn/k, an AGPL K interpreter by saagarjha on Friday January 10, 2020 @05:09AM (#22009879)
Please point me at these C codebases so I can steer clear of them except for when I need inspiration while writing reversing CTF challenges.
Re:ngn/k, an AGPL K interpreter by anonymoushn on Friday January 10, 2020 @06:38AM (#22010279)
You might try nginx?
Re:ngn/k, an AGPL K interpreter by saagarjha on Friday January 10, 2020 @07:09AM (#22010403)
Seems fairly reasonable to me?
Re:ngn/k, an AGPL K interpreter by anonymoushn on Friday January 10, 2020 @07:54PM (#22017206)
it's totally full of unwritten assumptions and the same header is usually parsed in several places slightly differently. it's a spooky action at a distance playground.
Re:ngn/k, an AGPL K interpreter by tluyben2 on Friday January 10, 2020 @09:48AM (#22011261)
But it conveys far more information for one page than you have in other styles, so obviously it will take you more time to read + understand it. It's far more content dense. If you change the style, you probably spend more time reading it, spread over more pages & files and personally that takes me more time to read + understand (depending on the functionality, much more).