<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<blockquote type="cite"
cite="mid:dbe9cf62-06a0-c14e-461a-9660933090d1@yahoo.ca">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<font face="Bitstream Charter">I'm also looking to learn a new
language. As start, I've decided on Dart/Flutter.<br>
<br>
I don't know Javascript, and I've only added few functions via
simple cut/paste of existing code. At least on the part I was
working on, you define function, and it is triggered when some
event happens.</font></blockquote>
<p><font face="Bitstream Charter">Focusing remark on</font></p>
<blockquote type="cite"
cite="mid:dbe9cf62-06a0-c14e-461a-9660933090d1@yahoo.ca"><font
face="Bitstream Charter"> I don't like "callback" really. <br>
</font></blockquote>
<p>you have no choice.</p>
<p>Everything around us has been made with functions and closures.
Give someone a function to call you back, and they call it a
callback. Phrase "Observables and Promises are fancy callbacks"
I've heard in pure form from Rust guy. Precisely. It comes from
Lisp and builds the future in Rust. We either do assembly with
jumps, or we do callbacks.</p>
<p>Granted, I love to consume cakes (Observables and Promises)
instead of straight sugar (callbacks).</p>
<p>Not loving and groking callbacks is not an option -- debugging
becomes nuts :) . Yet, there is not need to take it pure all the
time.<br>
</p>
<blockquote type="cite"
cite="mid:dbe9cf62-06a0-c14e-461a-9660933090d1@yahoo.ca"><font
face="Bitstream Charter"> One reason I choose to start with
Dart/Flutter is that it can compile to native code, rather than
just Javascript which requires webserver and browser.</font></blockquote>
<br>
</body>
</html>