Deno: Is stacking gc languages really the best idea?

[ForsakenHarmony]

I feel like go is not the best choice

[TomasHubelbauer]

Ryan seems to be considering Rust and C++, too, which would address this. (I'm particularly fond of the thought of rewriting this in Rust.)

[monkingxue]

The existing solutions are mainly considered from the perspective of easy implementation. It is less difficult to achieve with go.

[lukeed]

Nothing new here, but Rust seems like the obvious choice -- especially given that Deno has/will have a renewed focus on systems APIs. Personally, Rust _feels_ closer to JavaScript, too~!

Either way, curious to see how deno & all its experiments along the way take shape 👍

[jacktuck]

@lukeed I think you're absolutely right! Rust feels closer to Javascript when you look at generics and such. Don't think Ryan is sold on Go yet and the codebase is lean enough to change languages most likely. https://github.com/ry/deno/search?l=go&p=1

[lukeed]

Aye, definitely. The possibility of switching (and to Rust, specifically) has been mentioned a few times already across other issues, as well as in the introductory talk too.

I'm just echoing my preference 😄I recently resolved my own 6-mo internal debate of Go-v-Rust for some of my own projects, some of which share deno's need for secure boxes & systems integrations. Just thought I'd help push in the _right_ (😉kidding) direction.

[benjamingr]

From what I understand after talking to Ryan, there is serious consideration of using C++ (or rust) exactly for this reason.

Let's respect his wishes, this project is in a very early stage and we're creating a lot of noise.

[rurban]

Yes, it's the best idea.
First GC languages are safe, refcounted typically not. Esp. rust is unsafe with memory and concurrency, C++ ditto. This projects goal is safety first.

A good point for rust would be abstractions with macros and generics. But there are safe and fast languages for these. ATS or Pony would come to my mind.

[TomasHubelbauer]

As per #94, this is not a time and place to discuss this, but would you please consider emailing me (email is in my profile) elaborating on how Rust is unsafe with memory and concurrency? The language was designed with the stated goal of the exact opposite, safety, so I am curious to see why you think it's failing at that.

[qti3e]

This subject has been discussed many times on many issues; please do not open design issues for now.

[ry]

https://github.com/ry/deno/issues/208#issuecomment-395739171