cedro VS Nim

I’ve built it for now in a separate branch called “self”:

    git clone -b self https://github.com/Sentido-Labs/cedro.git

Currently, it does not make any difference whether this is one token or more because it is sent to the compiler exactly the same as it came in, but you could write a macro/plugin (src/macros/] that recognized this pattern and inserted a space right before the minus “-” sign.

Hi, when I presented the first release here 8 months ago (https://news.ycombinator.com/item?id=28166125) it got interesting comments and today I’ve made a new release with additional features:

- Break out of nested loops: break label; (https://sentido-labs.com/en/library/cedro/202106171400/#labe...)

- Notation for array slices: array[start..end] (https://sentido-labs.com/en/library/cedro/202106171400/#slic...)

- Loop macros: #foreach { ... #foreach } (https://sentido-labs.com/en/library/cedro/202106171400/#loop...)

The possibility of loop macros was discussed in this thread: https://news.ycombinator.com/item?id=28166698

At the time I hadn’t figured out how to make it useful without type information, but now it works. The same for the array slice notation: it took me a while to figure out how to make it do something useful without reflection, with a purely syntantical transformation.

Loop macros are useful for the kind of things for which you would use x-macros (https://en.wikipedia.org/wiki/X_Macro), with the advantage that it does not pollute the global namespace with macro names and the body of the macro stays more similar to the final result, which makes big macros easier to read.

Since it runs before the standard C preprocessor it can do things like building up `_Generic` macros as shown in the loop macro vec example: https://sentido-labs.com/en/library/cedro/202106171400/#loop...

Source code (Apache 2.0 license): https://sentido-labs.com/en/library/ or https://github.com/Sentido-Labs/cedro

If pre-processing your code is an acceptable compromise, my Cedro pre-processor has that feature: passing a file through it produces standard C code for your compiler, and it includes a wrapper cedrocc that can be used in Unix/POSIX-style systems like Linux as a drop-in replacement for GCC: https://github.com/Sentido-Labs/cedro/

What I’d like to do is a quick proof-of-concept to see whether whatever instructions are available in my CPU can be leveraged for UTF-8 en-/decoding.

For instance, does it work any better than my C implementation? https://github.com/Sentido-Labs/cedro/blob/master/src/cedro....

Maybe the compiler already compiles that to an optimal SIMD version, I don’t know.

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.