Docs: Add key features for nim

[ynfle]

Closes #270

[ynfle]

The value of key_features.title that starts with Customizable Memory Manag... is 30 characters, but it must not exceed 25 characters

I'm not sure what to do about this configlet check, I can't think of anything else.

[ynfle]

@AmjadHD I'd be interested to hear your opinion

[ErikSchierboom]

@ynfle What about "Custom Memory Management"? That's 24 characters.

[ErikSchierboom]

With one suggestion for the title.

[ee7]

Cool, thanks.

I think writing the list of key features is pretty hard for Nim - there's a lot to squeeze in.

[ee7]

Suggested change

	"content": "Compiles to C/C++/ObjC with no run time or virtual machine for blazing fast results.",
	"content": "Compiles to C/C++/ObjC with no runtime or virtual machine for blazing fast results.",

[ee7]

There's a possible misreading of "with no runtime or virtual machine for blazing fast results" -> "with no blazing fast results" -> "it's slow". Also some potential confusion due to "with no virtual machine", since we have the Nim VM at compile time.

Maybe something like this?

"Compiles to a small, blazing-fast binary (no runtime or virtual machine overhead)".

I think it's better to mention "small binary" (which many people care about, even outside embedded - it's also an advantage over Go) than mentioning C++ and ObjC. But this wording does lose out on "compiles to C" (and JavaScript). Can we find a wording that conveys everything?

[ynfle]

How about

"Compiles using C/C++/JS to a small, blazing-fast binary (no runtime or virtual machine overhead)."

[ee7]

The problem is that compiling to JS isn't compiling to a binary :)

[ynfle]

How about this?

"Compiles using C/C++/Objc to a small, blazing-fast binary (no runtime or virtual machine overhead)."

I think we can leave out JS for now

EDIT

[ynfle]

Bump

[ynfle]

Bump

[ee7]

Sorry for the delay. I'll try to review tomorrow.

[ee7]

OK - I've stared at it for quite a while. I was hoping to make a few more suggestions regarding wording, but I'm finding it difficult to get to something I like more.

I was also hoping to squeeze in "productive" somewhere - I think the "productivity to performance ratio" or ("productivity + performance + readability" balance) is one of Nim's biggest strengths. It's easy to write code that's essentially as fast as anything, but is very readable.

But that's sort of trying to combine at least three separate "key features" at once, and I don't see how to squeeze it in. I can't even identify the least important of the current features.

I'll see if I have any wording inspiration tomorrow, but otherwise I'll merge and we can always follow-up later. Sorry again for the delay.

[ynfle]

Let's give it some time then

[kytrinyx]

@ynfle @ee7 Any chance we can get this merged? It doesn't have to be perfect. These are meant to entice people to try the track, not teach them about a fundamental truth about the language.

Having something on the site is better than having nothing on the site.

[ynfle]

For some reason, because I force pushed after closing, it won't reopen. #447 will supersede this, then