Why are we still treating dynamic languages as "scripting languages" as if you can't do the same thing one does in Go?
Deno 1.0
31–40 of 598 posts
Re: Deno 1.0
#32For context:
Deno's lead is Ryan Dahl, the creator of Node.
In the past, Dahl's expressed regrets over choices he made early on in Node's development, and on the direction Node has gone since he left the project many years ago.
He bravely presented on this topic at jsconf eu, 2018: https://www.youtube.com/watch?v=M3BM9TB-8yA, it's a fantastic talk.
The last 10 minutes are a pitch for what a "better Node" would look like, if he were to start from scratch in 2018. The end result of that train of thought this project, which we should probably think of as bourne-again node.
Deno's development is (presumably) strongly influenced by his experience and furstrations with Node's shortcomings in both performance and developer ux.
Re: Deno 1.0
#33If you're getting into Deno and want to keep up with new stuff from the ecosystem on a regular basis, we're now publishing https://denoweekly.com/ .. issue 2 just went out minutes after the 1.0 release. I've been doing JavaScript Weekly for 487 issues now, so this is not a flash in the pan or anything :-D
Of course, Deno has an official Twitter account as well at https://twitter.com/deno_land :-)
Re: Deno 1.0
#34Earlier quoted context omitted.
For this sort of problem Rust's safety guarantees don't buy you all that much. If you're generating machine code and implementing a GC that's not the sort of thing that Rust's typesystem can prove correct. That said, a rust JS runtime would be amazing just because it's easier to integrate into rust projects.
Well, sure, but a big chunk of the bugs in JRE were in the library, not the code generation or GC.
Speaking of: Neon, a system for writing Node libraries in Rust is pretty cool:
Re: Deno 1.0
#35Why are we still treating dynamic languages as "scripting languages" as if you can't do the same thing one does in Go?
So at this fine grain of semantic detail, making strong statements about differing labels feels a little silly, but I have always thought that the difference is dynamic refers to typing, whereas scripting is usually a reference to the language being interpreted rather than compiled. Dynamically typed languages can certainly be compiled (I think Clojure qualifies here?).
Re: Deno 1.0
#36> We believe JavaScript is the natural choice for dynamic language tooling; whether in a browser environment or as standalone processes.
I disagree with this assessment. Lua is still far superior as an embed-able scripting language/runtime. I suspect the preference for JavaScript is mostly due to the Deno developers' familiarity and preference.
Re: Deno 1.0
#37For context: Deno's lead is Ryan Dahl, the creator of Node. In the past, Dahl's expressed regrets over choices he made early on in Node's development, and on the direction Node has gone since he left the project many years ago. He bravely presented on this topic at jsconf eu, 2018: https://www.youtube.com/watch?v=M3BM9TB-8yA , it's a fantastic talk. The last 10 minutes are a pitch for what a "better Node" would look…
And now, he'll make a whole different set of good and bad choices to potentially regret later.
Re: Deno 1.0
#38Why are we still treating dynamic languages as "scripting languages" as if you can't do the same thing one does in Go?
[deleted]
Re: Deno 1.0
#39For context: Deno's lead is Ryan Dahl, the creator of Node. In the past, Dahl's expressed regrets over choices he made early on in Node's development, and on the direction Node has gone since he left the project many years ago. He bravely presented on this topic at jsconf eu, 2018: https://www.youtube.com/watch?v=M3BM9TB-8yA , it's a fantastic talk. The last 10 minutes are a pitch for what a "better Node" would look…
And now, he'll make a whole different set of good and bad choices to potentially regret later.
such is the curse of having the audacity to develop software :)
Re: Deno 1.0
#40This sentence, five paragraphs below, says what this is about:
> Deno is a new runtime for executing JavaScript and TypeScript outside of the web browser.