I think it'll get optimized. We went from GWT apps needing like 250k to render a HelloWorld, to J2CL + Closure Compiler being able to do the same thing with a 1 line output.
Compose has an elegant, theoretically pleasant way of modeling reactive frameworks as pure functions with memoized state, and an explicit call stack.
But right now you're paying a giant tax for all this since you bring in the entire Kotlin runtime, coroutines, collections, etc plus the Compose runtime, plus the Widget library. Since Compose is only beta right now, this is clearly unoptimized.
It's definitely not eliminating all the dead code or metadata it could, there's a ton of code like this:
```
function(e, t) {
e.exports = function(e) {
return {
name: "Inform 7",
aliases: ["i7"],
case_insensitive: !0,
keywords: {
keyword: "thing room person man woman animal container supporter backdrop door scenery open closed locked inside gender is are say understand kind of rule"
},
contains: [{
className: "string",
begin: '"',
end: '"',
relevance: 0,
contains: [{
className: "subst",
begin: "\\[",
end: "\\]"
}]
}, {
className: "section",
begin: /^(Volume|Book|Part|Chapter|Section|Table)\b/,
end: "$"
}, {
begin: /^(Check|Carry out|Report|Instead of|To|Rule|When|Before|After)\b/,
end: ":",
contains: [{
begin: "\\(This",
end: "\\)"
}]
}, {
className: "comment",
begin: "\\[",
end: "\\]",
contains: ["self"]
}]
}
}
}
```
Which looks like some kind of parser embedded in it.