Large binary sizes #1132
Closed
DanOverflow
started this conversation in
General
Replies: 5 comments 2 replies
-
This must caused by tree-sitter's for CodeEditor. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Now 22MB |
Beta Was this translation helpful? Give feedback.
0 replies
-
Now only 12MB |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Amazing progress! Thank you! I'll keep an eye out for that commit ( #1137 ) once it passes tests :) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Amazing work, thank you! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've been evaluating gpui-component for a bit and absolutely love it, great work!
One issue is that it seems to import quite a few large dependencies (even with default-features = false). For example, a simple hello_world application with a single gpui-component::Button takes 55MB (versus 8.2MB for the same using only GPUI, both compiled with --release and optimized for size).
It's not that big of an issue, but it still bugs me a little since my main use cases are to build small/simple utility-type applications that won't be using more advanced features like rich-text (which adds about 16MB to the binary) or code-editor...
I'd like to start a conversation to see if there's any interest in making an effort to keep the final binary size lower, and if so, what would be the preferred path (ie; splitting off advanced/heavy features into separate crates, or enable granular inclusion through feature flags...)
Beta Was this translation helpful? Give feedback.
All reactions