4 ms·

Looks pretty neat. Question: Why is this thing 170MB? Does it include the CDF player or something? Suggestion: I use WA for nutritional info, so I make mishma

Looks pretty neat. Question: Why is this thing 170MB? Does it include the CDF player or something? Suggestion: I use WA for nutritional info, so I make mishmash, then I do a search like: http://www.wolframalpha.com/input/?i=2+onions+and+5+cloves+garlic+and+3+tomatoes+and+1lb+chicken+breast+and+30ml+oil http://www.wolframalpha.com/input/?i=2+onions+and+5+cloves+g... This gives me same custom-made nutrition label as on food packaging, but for whatever I just made. Nimble returns one of the caloric-breakdown tables instead, which isn't as useful.

probablyjosh 11y ago
The size is primarily due to Electron, Nimble's backbone. Unfortunately, a large portion of Nimble's size is due to to Electron, and there's not a whole lot we can do about that aside from shifting the project to a completely different framework, rebuilding Nimble from the ground up. Although this is true, we're still doing everything we can to bring the size down. The information provided by Wolfram's API is rather limiting, and definitely not as extensive as the information provided through its web service. We'll see what we can do about this problem.