@BRIAN_____ @BrendanEich Is the revolution Rust? :)
-
-
Replying to @Caspy7
@Caspy7@BrendanEich All the post-use-after-free-by-default languages are part of it, I including Rust, Go, and others.1 reply 0 retweets 1 like -
Replying to @BRIAN_____
@BRIAN_____@Caspy7 JS too? :-P You need something on C++'s low level, which rules out Go.2 replies 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@Caspy7 RE: low-level, I am convinced almost all of a browser, almost all of an OS, could be in a GC'd language.1 reply 0 retweets 1 like -
Replying to @BRIAN_____
@BRIAN_____ Where's your pauseless GC you've been developing in secret? Github link or tarball, I'm old-sk00l.@Caspy71 reply 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@Caspy7 The Go people seem to think they can get close enough. People worry about pauses too much.1 reply 0 retweets 1 like -
Replying to @BRIAN_____
@BRIAN_____ Au contraire, latency & throughput trade off. TANSTAAFL. GC requires more mem (2x+), pauseless wants more square-ish duty cycle.1 reply 0 retweets 0 likes -
Replying to @BrendanEich
@BRIAN_____ Go used in throughput-optimized servers more than latency-optimized clients. Games, browsers, other native apps shun GC via C++.2 replies 0 retweets 0 likes -
Replying to @BrendanEich
@BrendanEich@BRIAN_____ for many cases where "pause" is considered the big problem, can't you just manually do memory management?2 replies 0 retweets 0 likes -
Replying to @frgx
@BrendanEich @BRIAN_____js apps do this today. there might still be cases where no-gc is needed but not sure how many such cases there are3 replies 0 retweets 0 likes
@frgx @BrendanEich I agree. Go's pauses are already short enough for almost everybody, if their claims are true.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.