4 ms·
And sometimes your engineers need to be a LOT less stingy. 1GB is clearly overkill for an app such as this, but ~300MB is perfectly acceptable if it works well,
by keicwifjwud 2mo ago
And sometimes your engineers need to be a LOT less stingy. 1GB is clearly overkill for an app such as this, but ~300MB is perfectly acceptable if it works well, looks good and does what it should do.
There is such a thing as overdesign, but when you’re building a modern application, you must trust your designer’s sense of aesthetics and knowledge of UX patterns—two things engineers are often notoriously bad at.
- christophilus 2mo agoDunno. Many designers are pretty bad at UX. They’re OK at aesthetics, but that’s not the same thing.
- kasabali 2mo ago> ~300MB is perfectly acceptable if it works well, looks good and does what it should do. No it isn't. It isn't a word process for gods sake. It has one literally one job and 300 MB is like an order of magnitude off for that. This mentalty is the slippery slope that led us to the situation in the OP today.
- gruturo 2mo agoYou're off by 2 orders of magnitude if you think that a not completely incompetently coded weather app genuinely needs that kind of resources - even allowing for aesthetic choices and modern UX patterns.
- zeratax 2mo agogp was talking about 87MB without animations how do you end up at your estimate?
- mrheosuper 2mo agoAh yes, Microsoft is famous for good modern UI/UX.