Have a cheat sheet

[ghost]

The purpose, or rather the main benefit, is that people easily could try out the language. One for far-fetched idea, would be to have a cheat sheet available in a live compile environment (in another area of the visible screen) or even auto-fill when starting typing. However, this I would guess is way of scope. But a docs section containing comparisons between 'known', 'common' langs could be in scope, I would think. Just an idea!

Docs

• Filter and/or search field

• Table (comparisions) such as

  | 007/Alma  | Perl6 | C      | JS                              | Java  |
  |--------------|---------|--------|---------------------------|-------|
  | say           | print   | printf | process.stdout.write | print |
  

• Cheat sheet [name of operator, method (...)] - [short, simple example]

[masak]

Web

• Compile projects live! (Include field for 'inputs', similar to a browser console)

Gonna pare down this bit for now. It's a noble goal, but we already have it covered in other issues. (Loose plan: rewrite the compiler/interpreter in TypeScript, and then build a web frontend for it.) Better to keep issues separate and with a narrow focus.

[masak]

Not sure how front-and-center the comparison table should be. If we're talking about the cheat sheet, I think the room on there is too precious. Probably 25% of the cheat sheet would be spent on syntax/basics, and 75% on macro lore. (Which also seems to be the rough proportions for #67, even though most of it is as yet unpublished.)