← Back to context Comment by wg0 7 days ago Is it 400mb? Could be V8 for plugins. 11 comments wg0 Reply _sinelaw_ 7 days ago Thanks for reminding me. Unfortunately yes, it's because of v8 (for Deno).For extensions, the choice was either TypeScript (and get this bloat) or go with Lua and a much smaller binary (but less popular language).But - I just realized stripping it brings it down to 76MB so I guess that's ok! Will push a commit :) WhereIsTheTruth 6 days ago > For extensions, the choice was either TypeScript (and get this bloat) or go with Lua and a much smaller binary (but less popular language).Incredible, the technical choice got overridden by popularity, leading straight to bloat _sinelaw_ 6 days ago I see extension language choice as a user-facing UX decision, and convenience is a leading concern. 1 reply → wg0 7 days ago Great! Just wondering maybe Bun (different JS engine) could do the job for plugins. _sinelaw_ 7 days ago Anthropic Bun? :) I didn't realize it was an engine as well. I can take a look but we should wait and see where the acquisition takes it 5 replies →
_sinelaw_ 7 days ago Thanks for reminding me. Unfortunately yes, it's because of v8 (for Deno).For extensions, the choice was either TypeScript (and get this bloat) or go with Lua and a much smaller binary (but less popular language).But - I just realized stripping it brings it down to 76MB so I guess that's ok! Will push a commit :) WhereIsTheTruth 6 days ago > For extensions, the choice was either TypeScript (and get this bloat) or go with Lua and a much smaller binary (but less popular language).Incredible, the technical choice got overridden by popularity, leading straight to bloat _sinelaw_ 6 days ago I see extension language choice as a user-facing UX decision, and convenience is a leading concern. 1 reply → wg0 7 days ago Great! Just wondering maybe Bun (different JS engine) could do the job for plugins. _sinelaw_ 7 days ago Anthropic Bun? :) I didn't realize it was an engine as well. I can take a look but we should wait and see where the acquisition takes it 5 replies →
WhereIsTheTruth 6 days ago > For extensions, the choice was either TypeScript (and get this bloat) or go with Lua and a much smaller binary (but less popular language).Incredible, the technical choice got overridden by popularity, leading straight to bloat _sinelaw_ 6 days ago I see extension language choice as a user-facing UX decision, and convenience is a leading concern. 1 reply →
_sinelaw_ 6 days ago I see extension language choice as a user-facing UX decision, and convenience is a leading concern. 1 reply →
wg0 7 days ago Great! Just wondering maybe Bun (different JS engine) could do the job for plugins. _sinelaw_ 7 days ago Anthropic Bun? :) I didn't realize it was an engine as well. I can take a look but we should wait and see where the acquisition takes it 5 replies →
_sinelaw_ 7 days ago Anthropic Bun? :) I didn't realize it was an engine as well. I can take a look but we should wait and see where the acquisition takes it 5 replies →
Thanks for reminding me. Unfortunately yes, it's because of v8 (for Deno).
For extensions, the choice was either TypeScript (and get this bloat) or go with Lua and a much smaller binary (but less popular language).
But - I just realized stripping it brings it down to 76MB so I guess that's ok! Will push a commit :)
> For extensions, the choice was either TypeScript (and get this bloat) or go with Lua and a much smaller binary (but less popular language).
Incredible, the technical choice got overridden by popularity, leading straight to bloat
I see extension language choice as a user-facing UX decision, and convenience is a leading concern.
1 reply →
Great! Just wondering maybe Bun (different JS engine) could do the job for plugins.
Anthropic Bun? :) I didn't realize it was an engine as well. I can take a look but we should wait and see where the acquisition takes it
5 replies →