nimlsp VS Nim

Downloading https://github.com/PMunch/nimlsp using git

Cloning into '.'... From https://github.com/pmunch/nimlsp * tag v0.4.4 -> FETCH_HEAD + nimble build -y --localdeps Warning: Using project local deps mode Verifying dependencies for [email protected] Prompt: No local packages.json found, download it from internet? -> [forced yes] Downloading Official package list Success Package list downloaded. Installing jsonschema@>= 0.2.1 Downloading https://github.com/PMunch/jsonschema using git Verifying dependencies for [email protected] Installing ast_pattern_matching@any version Downloading https://github.com/nim-lang/ast-pattern-matching using git Verifying dependencies for [email protected] Installing [email protected] Success: ast_pattern_matching installed successfully. Installing [email protected] Success: jsonschema installed successfully. Installing asynctools@>= 0.1.1 Downloading https://github.com/cheatfate/asynctools using git Verifying dependencies for [email protected] Installing [email protected] Success: asynctools installed successfully. Building nimlsp/nimlsp_debug using c backend [1m/home/terrior/.local/share/nvim/mason/.packages/nimlsp/src/nimlsppkg/suggestlib.nim(3, 18) [0m[31mError: [0mcannot open file: nimsuggest/nimsuggest[36m[0m[0m Tip: 30 messages have been suppressed, use --verbose to show them. Error: Build failed for package: nimlsp ... Execution failed with exit code 1 ... Command: /usr/bin/nim c --colors:on --noNimblePath -d:NimblePkgVersion=0.4.4 --path:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimbledeps/pkgs/ast_pattern_matching-1.0.0 --path:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimbledeps/pkgs/jsonschema-0.2.1 --path:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimbledeps/pkgs/asynctools-0.1.1 --hints:off -o:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimlsp_debug /home/terrior/.local/share/nvim/mason/.packages/nimlsp/src/nimlsp_debug.nim spawn: bash failed with exit code 1 and signal 0.

nimlangserver is an implementation of Language Server Protocol with the goal to make nim IDE experience more mature. The main difference between nimlangserver and the existing nimlsp is that nimlangserver runs nimsuggest in a separate process and that nimlangserver is using a newly introduced version of nimsuggest v3(see bellow). nimlangserver is currently integrated in VScode via vscode-nim and in Emacs via lsp-mode but adding integraion with other editors should be trivial.

Downloading https://github.com/PMunch/nimlsp using gitTVerifying dependencies for [email protected]: Dependency on jsonschema@>= 0.2.1 already satisfiedVerifying dependencies for [email protected]: Dependency on ast_pattern_matching@any version already satisfiedVerifying dependencies for [email protected]: Dependency on asynctools@any version already satisfiedVerifying dependencies for [email protected] [email protected] nimlsp/nimlsp using c backend/tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/baseprotocol.nim(2, 8) Warning: imported and not used: 'logger' [UnusedImport]/tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/suggestlib.nim(11, 8) template/generic instantiation of `mImport` from here/tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/suggestlib.nim(7, 14) Error: cannot open file: /usr/nimsuggest/nimsuggest.nimPrompt: Build failed for '[email protected]', would you like to try installing 'nimlsp@#head' (latest unstable)? [y/N]Answer: NTip: 10 messages have been suppressed, use --verbose to show them.Error: Aborting installation due to build failureimlsp using gitT Verifying dependencies for [email protected] Info: Dependency on jsonschema@>= 0.2.1 already satisfied Verifying dependencies for [email protected] Info: Dependency on ast_pattern_matching@any version already satisfied Verifying dependencies for [email protected] Info: Dependency on asynctools@any version already satisfied Verifying dependencies for [email protected] Installing [email protected] Building nimlsp/nimlsp using c backend /tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/baseprotocol.nim(2, 8) Warning: imported and not used: 'logger' [UnusedImport] /tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/suggestlib.nim(11, 8) template/generic instantiation of `mImport` from here /tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/suggestlib.nim(7, 14) Error: cannot open file: /usr/nimsuggest/nimsuggest.nim Prompt: Build failed for '[email protected]', would you like to try installing 'nimlsp@#head' (latest unstable)? [y/N] Answer: N Tip: 10 messages have been suppressed, use --verbose to show them. Error: Aborting installation due to build failure

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.