Absolutely not. Compiled code is small, really small. I’d be surprised if the engine* itself as a whole was more than a gigabyte in size. It’s all about the assets that are included, how badly they’re compressed and how uselessly detailed some of them are.
*The embedded one of course. The editors are unruly beasts that’ll guzzle up your disk space, but then again it’s probably a similar situation…
We’re only talking about 80MB though, at work just the core Grape City Active Reports dlls are 32MB that’s not even including the dependencies (everything seems to use extra system. Dlls on windows). A simple aspx web forms project I’m looking at with maybe 1MB images is still 120MB, granted it’s not optimized or anything and 32MB is from Active Reports
Oops I’m stupid. I didn’t notice this was about Balatro, I lost track of the comment indentation and thought it was a general discussion. Yeah it’s probably the runtime and the other stuff then, my bad…
Absolutely not. Compiled code is small, really small. I’d be surprised if the engine* itself as a whole was more than a gigabyte in size. It’s all about the assets that are included, how badly they’re compressed and how uselessly detailed some of them are.
*The embedded one of course. The editors are unruly beasts that’ll guzzle up your disk space, but then again it’s probably a similar situation…
We’re only talking about 80MB though, at work just the core Grape City Active Reports dlls are 32MB that’s not even including the dependencies (everything seems to use extra system. Dlls on windows). A simple aspx web forms project I’m looking at with maybe 1MB images is still 120MB, granted it’s not optimized or anything and 32MB is from Active Reports
Oops I’m stupid. I didn’t notice this was about Balatro, I lost track of the comment indentation and thought it was a general discussion. Yeah it’s probably the runtime and the other stuff then, my bad…