@be not gonna be a petty little shit about some probably pretty over-exaggerated & all-in-all mild technical constraints. yeah it'd be nicer if the mega huge os could build in a somewhat smaller confines. but it's not exactly that daunting a challenge, if you evaluate what that utility of computing really costs. I think there are probably hundreds of more real places to make a stand, that deserve real respect & attention.
@jauntywunderkind420 It's emblematic of Google's attitude of "fork everything, do it our way and if you don't like it too bad".
@be I very much despise them for always going it their own way, & for having tools & environments & stacks of other Android et centera dependencies that make their Software useless. to me that's a situation into it's own & I don't see high build "requirements" as emblematical or really related to that particular & seriously frequent curse.
I'm also used to kubernetes & knative decalaring they needed 16gb, for basically no cause. not no cause, kube took some space. but that requirement was so your app had 15gb. feeling like a swap space, even hd not ssd based, probably fills in similarly here.