Live data from Hacker News

Dada, an experimental new programming language

dada-lang.org

1–10 of 428 posts

Re: Dada, an experimental new programming language

#4
post #2

If the claim that its performance will be similar to Rust's if you add type annotations, this could become a really attractive language! As easy as JavaScript to write, as fast as Rust when the extra effort to write it justifies it.

There’s no claim to be as easy as javascript to write.

Rusts “difficulty” stems from its single ownership model, and this model is “different” not “easier”.

https://dada-lang.org/docs/dyn_tutorial/permissions

Re: Dada, an experimental new programming language

#6
Their Hello, Dada! example:

print("...").await

I'm coming from Python, and I can't help but ask: If my goal as a programmer is to simply print to the console, why should I care about the await? This already starts with a non zero complexity and some cognitive load, like the `public static void main` from Java.

Re: Dada, an experimental new programming language

#8
post #7

what does "creators of rust" mean? Graydon? niko? pcwalton?

niko judging from Github commits https://github.com/dada-lang/dada/graphs/contributors

ah, thank you! I couldn't find anything on the website itself, should have thought to look at the code.

Re: Dada, an experimental new programming language

#9
post #2

If the claim that its performance will be similar to Rust's if you add type annotations, this could become a really attractive language! As easy as JavaScript to write, as fast as Rust when the extra effort to write it justifies it.

There’s no claim to be as easy as javascript to write. Rusts “difficulty” stems from its single ownership model, and this model is “different” not “easier”. https://dada-lang.org/docs/dyn_tutorial/permissions

From what it looks more expressive and seems intuitive to me.

Re: Dada, an experimental new programming language

#10
post #6

Their Hello, Dada! example: print("...").await I'm coming from Python, and I can't help but ask: If my goal as a programmer is to simply print to the console, why should I care about the await? This already starts with a non zero complexity and some cognitive load, like the `public static void main` from Java.

I'd say you want something like 'debug_msg()' for this.

'print()' should be async because it does IO. In the real world most likely you'd see the output once you yield.

Post reply on HN