For servers, you don't want each server to do its own optimizations on the fly. Better off getting types from test runs and share.
-
-
Replying to @sebmarkbage
This feels like assuming a lot about what programs you care about to conclude something before any results are in.
2 replies 0 retweets 1 like -
Replying to @samth
My scope is tainted by my experience. In my world there's two categories: Short lived dynamic UI code. Long lived perf critical code.
2 replies 0 retweets 1 like -
Replying to @sebmarkbage @samth
Long lived perf critical code is worth while using a different language for. I'd argue that dynamic languages aren't the right choice
2 replies 0 retweets 0 likes -
Replying to @sebmarkbage @samth
Especially with such awesome inferred type systems we have these days.
1 reply 0 retweets 1 like -
Replying to @sebmarkbage @samth
Agreed, hell, we are "AoT Compiling" our web assets etc. with bundlers anyways.
2 replies 0 retweets 2 likes -
Replying to @TheLarkInn @samth
A goal of JITs was to load platform agnostic code. I think we should AOT compile to multiple platforms. iOS/Android does.
2 replies 0 retweets 2 likes -
AOT compilation is the future. I talked about this with
@littlecalculist the first EmberConf.1 reply 1 retweet 3 likes -
Replying to @wycats @sebmarkbage and
The future of what? Also what kind of AOT compilation?
1 reply 0 retweets 1 like -
Replying to @bmeurer @sebmarkbage and
I really mean something like .pyc, not total AOT.
2 replies 0 retweets 1 like
Glimmer already compiles HTML to opcodes today. I forsee more of this.
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.