I keep stumbling across references to the language E. I can find basic tutorials, but nothing describing the overall design goals.
miniblog.
Related Posts
I'm trying to decide the best voice for PL documentation.
Passive: "`let` can be used with destructuring."
Reader focused: "You can use `let` with destructuring."
Describing the PL: "FooLang supports destructuring with `let`."
Anyone have opinions or best practices?
It's rare to see ANSI escape codes for URLs in the wild, but cargo has it!
This example links to https://doc.rust-lang.org/cargo/reference/profiles.html#default-profiles, describing the different profiles.
Considering releases vs debug is a source of confusion for new users expecting better performance, this seems wise.
The Ruby on Rails guides use "please" when suggesting other resource to read or best practices to follow. For example: https://guides.rubyonrails.org/autoloading_and_reloading_constants.html
I've not seen this docs convention before. I certainly see the appeal for describing best practices: "your collaborators will appreciate it!"
