Míla Kuchta

I quite often think of koka as one of the best languages for the web, because it has compatible syntax that allow dashes in indentifiers. I image a future where...

Yes, I think using configurable delimiters are probably the best way how to go about it. I was also thinking about inverted parenthesis 🙌🏻, but it probably could visually distract...

Regarding current syntax, it should be even possible to write something like this, right? ``` fun some-component(attr1="default", attr2="default" attr3="default", children={}) div(attr1=att1, attr2=attr2) span(att3=att3) children() other-component() ``` With all nested blocks...

@TimWhiting: "You could create an intermediate AST, but that wastes time." - Not if that's what you'll need to update the DOM on the client...

@TimWhiting Exactly and those advanced server-side renderers might want to have features like React Server Components (RCS) for which some form of (build-time) code transformation (compilation) would be probably needed...

I though it wouldn't be so easy, since practically nobody is using it. I will leave here some prior art that led me to angle brackets. Unix man pages syntax...

@TimWhiting Wow, I'm really looking forward to it. 🤗 Yesterday I found out that my koka installation is quite outdated, since homebrew channel is probably no longer maintained...

Why not use join right away? 🙂 ``` [ "Result: " match err { Ok() -> ""; Error(err) -> "Error! &err" } ">" ].join/concat/... ``` But I like it. It's...

@TimWhiting I don't know if I would call it argument separation by whitespace if there could be just one trailing argument, but making them optional would leave that decision to...

Oh, true... You are right. But wouldn't it then be more consistent to allow even non-trailing arguments to be also separated by whitespace? All separeted by whitespace, just trailing arguments...