On Monday, 19 June 2017 at 02:02:05 UTC, rikki cattermole wrote:
On 19/06/2017 2:57 AM, Laeeth Isharc wrote:
On Sunday, 18 June 2017 at 23:11:25 UTC, rikki cattermole
wrote:
On 18/06/2017 5:29 PM, Meta wrote:
We should be careful not to make *too* close a comparison.
While Javascript is a necessary evil for web applications
and some people do like it, I get the feeling that it's
becoming less and less liked. It's not quite a fractal of
bad design like PHP, but it has more than a few drastic
shortcomings and design flaws.
The moment webasm becomes a realistic target, I will do
EVERYTHING in my power to get Lua in the browser (yes there
already is solutions).
Stuff Javascript, kill it, replace it with something actually
properly designed!
Why not D? And why wait till it's a realistic target? Wasm is
clearly going to be the answer and it's an answer to a problem
that exists, so what does one gain by waiting?
(1) eval
(2) time+not all API's required are available just yet.
Why do you choose Lua? Whatever replaces Javascript (and compiles
to wasm) will be used for large apps, like how Javascript is
currently used. My understanding is that Lua is not particularly
well suited for building large apps.