treesitter-unit VS Nim

It's also relatively easy to write plugins based on the parsed AST. I wrote treesitter-unit[1] making it easy to select/modify the subtree of the selection.

[1]: https://github.com/David-Kunz/treesitter-unit

I built a plugin to select units of tree-sitter objects https://github.com/David-Kunz/treesitter-unit

To delete/yank the node, the combination would be `diu`, using this plugin: https://github.com/David-Kunz/treesitter-unit

Hi, I also think treesitter-textobjects are a bit overspecific, that's why I created https://github.com/David-Kunz/treesitter-unit/ .

In this video I create a Neovim plugin called 'treesitter-unit' using Lua. You can find the final plugin here: https://github.com/David-Kunz/treesitter-unit/

I tried it with operator mode maps and it works perfectly! I updated the README to include: vim.api.nvim_set_keymap('o', 'x', ':lua require"treesitter-unit".select()', {noremap=true})

22. Nim - $80,000

I think the right answer to your question would be NimLang[0]. In reality, if you're seeking to use this in any enterprise context, you'd most likely want to select the subset of C++ that makes sense for you or just use C#.

[0]https://nim-lang.org/

I don't think it's a rust-inspired language, but since it has strong typing and compiles to javascript, did you give a look at nim [0] ?

For what it takes, I find the language very expressive without the verbosity in rust that reminds me java. And it is also very flexible.

[0] : https://nim-lang.org/

I see a valid cert for https://nim-lang.org/

FYI, on the front page, https://nim-lang.org, in large type you have this:

> Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula.

You better off with using a compiled language.

If you interested in a language that's compiled, fast, but as easy and pleasant as Python - I'd recommend you take a look at [Nim](https://nim-lang.org).

And to prove what Nim's capable of - here's a cool repo with 100+ cli apps someone wrote in Nim: [c-blake/bu](https://github.com/c-blake/bu)

Chapel has at least several full-time developers at Cray/HPE and (I think) the US national labs, and has had some for almost two decades. That's much more than $100k.

Chapel is also just one of many other projects broadly interested in developing new programming languages for "high performance" programming. Out of that large field, Chapel is not especially related to the specific ideas or design goals of Mojo. Much more related are things like Codon (https://exaloop.io), and the metaprogramming models in Terra (https://terralang.org), Nim (https://nim-lang.org), and Zig (https://ziglang.org).

But Chapel is great! It has a lot of good ideas, especially for distributed-memory programming, which is its historical focus. It is more related to Legion (https://legion.stanford.edu, https://regent-lang.org), parallel & distributed Fortran, ZPL, etc.