deno_std VS kakoune

For reference (for the issues you mentioned): 1. This issue was opened almost immediately to solve the weird .only function not working https://github.com/denoland/deno_std/issues/2979 2. That looks weird to me, will get back to you on this one since it should work I think 3. Generally polluting the global namespace isn't great, but because we're only polluting the namespace of a module (and we choose what parts to import), I personally find it quite freeing. I entirely understand how that might feel awkward. 4. you CAN specifying only writing to certain directories! --allow-write=/path/to/dir would allow that!

At least for the ones related to trees, it's just a renaming. Below is a link to the PR. When I initially implemented these trees, I chose the names BSTree and RBTree to keep the names short. I'm guessing the person that proposed renaming them did so to make it more obvious what they are.

https://github.com/denoland/deno_std/pull/2400

The standard library is separate from the runtime. It wouldn't break backward compatibility if you were to update. For example, if you were importing RBTree and upgraded Deno to the latest release, it would keep working just fine. You would only really need to switch to using RedBlackTree instead if there was a change made to it that you wanted.

I think the only time you would need to update your standard module imports to be able to use newer versions of the Deno runtime if the standard module were depending on runtime APIs that have a breaking change.

It is like Demo deprecating fs.exists().[1]

[1]https://github.com/denoland/deno_std/discussions/2102

This was fun to read through.

I would need to profile the code, but the startup time being bad for Deno seems like maybe a combination of the code in here being unoptimized:

https://github.com/denoland/deno_std/blob/0ce558fec1a1beeda3...

(Ex. Lots of temporaries)

And usage of the readFileSync+TextDecoder API instead of readTextFile (which is also a docs issue since it's suggests the first one). It seems the code loads the 100MB into memory, then converts to another 100MB of utf8, then parses with that inefficient csv decoder. The rust and go versions look to be doing stream/incremental processing instead.

But it there's some talk to reconsider it

Sorry to hear that. I want to provide expect API in deno_std in the future: https://github.com/denoland/deno_std/issues/1779

I just migrated the module to Deno and rewrote the test cases using the Deno test runner. Also contributed a bug fix to the test runner that I encountered during the migration. An npm version is still available and automatically generated from the Deno code via a small bash script (rewriting imports, adding an index.ts, etc.).

Much of Node.js is written in C, yet it's still called Node.js.

Deno has some JavaScript/TypeScript in it. On GitHub https://github.com/denoland/deno is 22.8% JavaScript and 13.2% TypeScript, and https://github.com/denoland/deno_std is 68.2% JavaScript and 31.6% TypeScript.

So to me it's misleading about the name, but not about what Deno is written in.

Helix's modal editing is based on Kakoune's modal editing which is like an evolution to Vim's modal editing. You can think of it as being always in selection (visual) mode. https://github.com/mawww/kakoune?tab=readme-ov-file#selectio...

And while it doesn’t use the sam language precisely, I think in the broader “postfix Vi with visual feedback” category Kakoune[1] also warrants mentioning. The command language, in my experience, feels much more logical than that of Vis coming from a blank slate (things might be different if you come from Vim, but even when I used Vim regularly I never used the editing language that much exactly because I could never remember the damn thing).

And having mentioned Kakoune it’d probably be unfair to then not mention Helix[2]. It has a very similar editing language, but it’s a fairly anti-Unix everything-bolted-in affair on the inside (“everything works out of the box” being the advertising take) compared to Kakoune’s Acme-inspired no-scripting scripting (there’s an ex-style command to exec a user program that can then drive the editor over stdio RPC, a set of hooks, and that’s it). So if you’ve come for the Plan 9 feels, I don’t expect Helix to be that appealing. It’s still a good editor, nevertheless.

[1] https://kakoune.org/

[2] https://helix-editor.com/

You can take a look at kakoune. The source code (excluding documentations, test cases, customizations etc.) is less than 40k. It is, IMHO, a show case of a C++ project in use.

> I wonder if the author has ever heard of vis[0]

Yes.

https://github.com/martanne/vis/wiki/Differences-from-Kakoun...

https://github.com/mawww/kakoune/wiki#onboarding

> which imho fulfills far better each one of those premises

Not very motivated for such a harsh critic..

I've been using Vim for years, but if there was one thing I could change, it would be the verb-noun order. The Kakoune[1] editor behaves mostly like Vim, but where Vim has `dw` as "delete word", Kakoune has it backwards: `wd`.

It might sound minor, but by placing the range first, Kakoune can give a preview of what will be changed. The longer or more complicated the command, the more this feature shines.

Strictly better as far as I know. A shame my muscle memory, and all default installations, are still stuck with Vim.

[1] https://kakoune.org/

Helix is a postmodern text editor built in Rust built for the terminal. It is inspired by Kakoune, another Rust based text editor. Helix has got multiple selections, built-in Tree-sitter integration, powerful code manipulation and Language server support.