Dada, an experimental new programming language
dada-lang.org
Dada, an experimental new programming language
1–10 of 428 posts
Re: Dada, an experimental new programming language
#2As easy as JavaScript to write, as fast as Rust when the extra effort to write it justifies it.
Re: Dada, an experimental new programming language
#3Those are two very different feelings though!
Re: Dada, an experimental new programming language
#4If 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.
Rusts “difficulty” stems from its single ownership model, and this model is “different” not “easier”.
Re: Dada, an experimental new programming language
#5Re: Dada, an experimental new programming language
#6print("...").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
#7what does "creators of rust" mean? Graydon? niko? pcwalton?
Re: Dada, an experimental new programming language
#8Re: Dada, an experimental new programming language
#9If 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
#10Their 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.
'print()' should be async because it does IO. In the real world most likely you'd see the output once you yield.