Reputation: 2350
Is it ready for using in production? Especially for large applications.
As i understand - yes. But it would be great to get more details.
Also there are two ways to use it:
How much more time will take runtime execution than pre-compilation? As I tested, it is near x10-15 times but may be somebody has other info?
Upvotes: 2
Views: 581
Reputation:
Whether or not it's ready for production is a subjective issue. One needs to consider performance, reliability, and bandwidth. It's hard to see performance being an issue since it's just compiling down into ES5. As for reliablity, in all the time I've used traceur I've experienced no bugs whatsoever. Bandwidth-wise, you'll need to download the traceur runtime, but that's not large compared to all the other stuff we're downloading these days. So my own opinion would be yes.
With regard to pre-compilation, it's not a question of how many times slower. The compilation itself takes the same amount of time. The question is whether it happens in advance or each time you load the webpage. Although Traceur is remarkably fast, a medium-sized code base could still take several seconds to compile. That is probably not something you want your users to experience. So yes, best practice is absolutely to pre-compile for production.
Upvotes: 2