3 ms·
That's right, but we have to remember it's not really useful to optimize for binary size or RAM usage for a software that does not need multiple instances on se
by rpigab 2y ago
That's right, but we have to remember it's not really useful to optimize for binary size or RAM usage for a software that does not need multiple instances on servers, it's an end user app that you only need one of.
I think Java is a nice choice for a Solitaire game. If you're looking for efficiency, take a look at my command-line Solitaire that you can play in Gitlab pages or in a terminal : https://gitlab.com/rpigab/solitaire-cli https://gitlab.com/rpigab/solitaire-cli
It's written in Rust so by design, it should be blazingly fast wink wink. Well there are many ways to shrink the binary, I didn't try to yet, the WebAssembly part too is way bigger that it would need to, but still, it's smaller and there's less colors, shapes and animations to display.
- tjoff 2y ago... that sentiment is how we ended up requiring 1GB of ram for sending text...
- VelesDude 2y agoA slight tangent but it is kind of mind melting that smartphones now do need a minimum of 1GB just to send an SMS. I mean look at any Nokia phone form the 90's and none of them probably had more than 1MB of RAM, many way below that. Yes there is a lot of quality of life and security features but the bloat is real.
- rpigab 2y agoIs that true or just hyperbole? On what system? I love working towards making systems as efficient as possible, but in real life, engineer hours are limited and compromises exist. Also, if this is quantitative, we could make the same argument with 1MB, and 1KB, and less. Sending text doesn't require RAM at all, it requires carrier pigeons.
- trallnag 2y agoInstead you end up with 20 Java microservices each taking up a gig of memory