Roland Tepp

After seeing the version with _soft keyword_ ‘it’, I tend to agree to a degree with @jensli here that the keyword ‘it’ does not really bring out the fact that...

Well, your example could easily be rewritten like this: ```ceylon foo?.string else "null" ``` Much simpler imho.

For the record. I like ‘then’ and ‘else’ in if expressions. Much regular. Plus it affords nice formatting: ```ceylon value v = if (someBooleanExpression()) then someValueExpression() else alternativeExpression(); ```

@Zambonifofex Regarding regularity, I am not really talking about making _if statement_ syntax similar to _if expression_. This is not the regularity I am looking for. (they are different syntactic...

Let's not digress into formatting flame war!

Just to play a devils advocate here - what is the proposed migration path from double backticks to this new syntax?

There's lots of good information here, but could I sugest adding installation instructions to README documentation per editor?

May I add here that what is missing currently is a view that displays a list of work items (epics, user stories, tasks and issues) with a set of information...

See [compose profiles](https://docs.docker.com/compose/profiles/). Those might be helpful.

Also, while at it, it would be awesome if site documentation would mention deno as well. It already does this for bun.