You bought the wrong phone and/or put the wrong distribution on it. Having said this it does take more than 30 seconds to get a new device up to your personal specs unless you're fine with whatever vendor distribution runs on it - which can work if you choose the right vendor but mostly ends up with your device serving someone else. I'd say it takes closer to 30 minutes than 30 seconds but I'm fine with taking this time given that my average Android phone lifetime is a bit over 8 years. I'm currently using a Redmi Note 5 Pro from 2018 which I'll soon relegate to second device status once I have a replacement, probably a Motorola G75 or something similar. That device should also last me around 8 years. Before the Redmi I'm using now I used a Motorola Defy from 2010 which, incidentally, is still in use as a trailer camera. Android devices can last a very long time because the firmware is open. Eventually they'll be too slow or lack the memory to support more recent Android distributions - which is what made me replace the Defy with the Redmi - but that does not mean they end up taking space in a drawer somewhere. They're in use here as trailer camera, media player, 3D printer controller and more.
Well to be fair Hackernews posts can get flagged too by the community itself where people then later talk about how or why a particular post gets flagged and discussion starts moving about the moderation/flag issues in HN.
(But this isn't to say that the fault's within the moderation community of HN which are great but just the issue which to me is imo that if many users flag a post, it can get flagged and the friction of getting it back is hard or a post typically ends up dying usually if it gets flagged in general imho)
That changelog is wild; it closes out dozens of issues that have been open on Github for 5+ years. I assume that's related to this being the first new major version in years.
Has anyone done any benchmarks yet to see how jQuery 4 compares to jQuery 3.7?
It seems to work fine on a scaled down desktop browser though, and the existing game UI should be suitable enough to fit on a standard phone screen, even if the text is a bit hard to read.
I think OP just made a small mistake with some of the CSS/JS that handles resizing the game window on mobile viewports. In some cases the buttons are outside of the game, and in some cases the game window isn't using up the full screen real estate.
