gitonthescene

Which colleagues are you talking about in this context? In any event I’ve worked for over twenty years in companies with thousands of employees and I can’t remember a single time that the name of a source file made any practical difference in my day. I think the naysayers are having their own conversations distinct from actual reality of what’s happening here. “I wouldn’t do this” is a perfectly reasonable reaction but not at all useful in a public discussion.

Funnily enough, I don’t need a label for the drawer I keep my socks in. None of my drawers have labels. See what I’m saying here?

Are you saying this is a complex system or that any decisions made in the context of complex systems must be used for all software? Also, this was not in response to a post about documentation but rather a post about the file names. In any event, it says nothing about my experience and you are simply extrapolating.

You’re right. I don’t see any license mentioned in the source at all.

The author of Kona has written kerf which I believe is intended for this same space. I’ve never used it though. https://github.com/kevinlawler/kerf1

The K family of languages hew very closely to versions written by Arthur Whitney who famously rewrites the entire codebase from scratch with each major revision. Kona is largely modeled on K2 (the second major revision) and ngn/k is modeled on K6. K6 introduced a few more types, more flexible dictionaries and added/changed some primitives from earlier versions but the overall structure of the language is very similar.

Someone here has to post ngn’s survey of K languages: https://ngn.codeberg.page/k.html

oK is also modeled on K6 and its manual comes highly recommended.

I think this style of coding is decidedly less amenable to using a debugger on. With so much on a single line stepping becomes unclear. Heavy use of macros fights against the use of a debugger as well. I think proponents would argue that the extreme rigidity of the style means the code is more likely to fit expectations but you can decide how convincing that is. As for what people actually do, the catch phrase seems to be “use printfs”.

I think a diff is just as valuable with this code. Of course understanding a diff also requires understanding the code but if you’re interested the repository is linked at the root of this thread so you could poke around.

It’s odd, I seem to remember comments from you on a similar thread about a year ago. https://news.ycombinator.com/item?id=27220613 Are you still shocked or have you just forgotten?

I think you’re right that if you’ve already decided what the outcome will be then it’s not worth your time but also think it severely undermines the value of your opinion for others.

Or, or, and here me out here, you could learn the syntax in order to make a more informed assessment.

Do also seek out geocar’s posts. They are well written and to my mind convincing. https://news.ycombinator.com/item?id=27393682