Sure. There are a lot of scenarios where the 300k overhead hit isn't going to matter all that much.
Not that 300K should be considered a huge amount by today's standards anyway.
Not that 300K should be considered a huge amount by today's standards anyway.
I'm sure it's fine for a SPA, and for a mobile app it's a total non issue. Actually I'm planning to use it for one with React Native myself.
Luckily, people will probably not be including the full compiler lightly; I just wanted to point out that it's not as cheap as a jpg of the same size would be, an impression I thought the parent comment was giving.
On the other hand - in case of single page webapps it would only be loaded once and could be made to load only once thanks to browser caching.