Re:How I made a 3D game in 2 KB of JavaScript
by meheleventyone on Monday March 09, 2020 @03:23PM
(#22528769)
Binary size is a drop in the ocean most of the size of game installs is in assets.
Re:How I made a 3D game in 2 KB of JavaScript
by Sohcahtoa82 on Monday March 09, 2020 @05:56PM
(#22530298)
While true, you do have to ask how the hell there could possibly be 100 MB of just code.
Consider Windows calculator. In Windows 10, it consumes 15+ MB of RAM. When desktops have 8+ GB of RAM, 15 MB is essentially nothing. And yet, 15 MB is an astronomical amount of RAM considering the functionality Calculator offers. There's really no reason it should be more than a couple hundred kilobytes.
Re:How I made a 3D game in 2 KB of JavaScript
by rafaelvasco on Tuesday March 10, 2020 @04:08PM
(#22539131)
I didn't have a look at the code but the binaries aren't just code. Apart from things like embedded icons and stuff, there can be lots of engine embedded resources inside;
Re:How I made a 3D game in 2 KB of JavaScript
by meheleventyone on Tuesday March 10, 2020 @06:13AM
(#22534203)
You can actually look at the UE4 source and see.
Re:How I made a 3D game in 2 KB of JavaScript
by nineteen999 on Monday March 09, 2020 @07:35PM
(#22531119)
There is a reason for that, which is that UE4 has an absolutely massive amount of features out-of-the-box compared to most other engines.
If you were to add all the stuff from the Unity marketplace you need to be equivalent to a base UE4 install, it would probably approach that size as well, presuming all those features were even available.
As a dev, one problem I saw often is UE4 is massive, well over a hundred meg for just the base engine.