On 4/21/13 4:51 PM, Justin Lebar wrote:
What I'd like to come out of this thread is a consensus one way or another as to whether we continue along our current path of writing many features that are enabled on B2G in JS, or whether we change course.
First -- B2G should clearly do whatever it needs to in order to get acceptable memory/perf/whatever in the short term. If B2G flops, it doesn't matter a damn what it's written in.
That said, I think it's critically important that we're working to make JS a acceptable -- nay, _excellent_ -- language/runtime for application development for the long run. We can't tell a credible story about why people should write HTML5 apps, if we're tearing out swaths of JS in our own products. Sometimes dogfooding is unpleasant or hard, but that's the whole point.
There will always be a place for C++ (well, until Rust, amirite? ;). Either as being the right tool for a specific job, or just because someone happens to know it better. But if we end up avoiding JS because it's inherently JS, then that's a big strategic problem.
Justin _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
