With all the fuzz about Vibe Programming, I, a 59 years old software veteran, had a look at what's happening.
I'm kind of frustrated. Am I getting old?
Anyways, here is a short description of the StructEnv benchmark.
The repo provides the draft RFC for a new format for configurations. Environment variables are used a lot these days and they miss structure. On the other hand json is hard to read. So here a proposal for a fix. But I'm too lazy to code it myself ;)
I would love to have "news paper like columns" in my editor. I have been looking for it since 2007...
Another thing I would like is the ability to inject multiple files into the same "edit buffer" so that "search" works over these related files as whole, transparently.
I wrote quite a lot of TurboProlog code for a while some 25 years ago. I always wondered why there were no syntax sugar for nested 'or' Horn clauses.
Now it's fixed. Cool. So is the rest of Cosmos syntax sugar, cool, kudos.
I guess some OO would be a nice addition. And, that's the thing of the day: an efficient JS transpiler and a decent IDE with a stepping debugger. That's asking a lot. I know.
If effects from causes occurred immediately, versus with a distinct delay, everything would occur at once (or loop forever, that's a bug).
Hence, because we can observe that things happen "in sequence", there is a "propagation delay". That's what time is: "Time: the process whereby effects occur after causes, in a step by step manner".
That's another attempt to fix the "representative democracy" crisis.
Unfortunately I saw nothing about "Liquid Democracy" delegations? With pure direct votes only, participation will suffer because voting often on many matters is inconvenient to most people.
The "tagging" of proposals is nice. However, who define the "tag hierarchy"? Is it even necessary to have such a hieararchy, I don't think so.
With all the fuzz about Vibe Programming, I, a 59 years old software veteran, had a look at what's happening.
I'm kind of frustrated. Am I getting old?
Anyways, here is a short description of the StructEnv benchmark.
The repo provides the draft RFC for a new format for configurations. Environment variables are used a lot these days and they miss structure. On the other hand json is hard to read. So here a proposal for a fix. But I'm too lazy to code it myself ;)