News for hackers. Stuff that matters.

A comment on Files UWP: An enthusiast’s take on what Windows File Explorer explorer should be. Parent comment

Re:Files UWP: An enthusiast’s take on what Windows File Expl... by Veen on Saturday June 08, 2019 @10:45AM (#20132648)
I’m curious why it matters to you. 55MB is a trivially inexpensive amount of storage and bandwidth in 2019. It simply doesn’t make a practical difference to the vast majority of people who will use this whether it’s 55MB or 5MB.
[ Parent | on HN ]
Re:Files UWP: An enthusiast’s take on what Windows File Expl... by badsectoracula on Saturday June 08, 2019 @11:57AM (#20133051)
It is a hint that the code sucks.
[ Parent | on HN ]
Re:Files UWP: An enthusiast’s take on what Windows File Expl... by 8note on Saturday June 08, 2019 @02:40PM (#20134199)
Is it? I feel like it's a question of prioritizing. Why focus on application size when you could instead polish a feature?
[ Parent | on HN ]
Re:Files UWP: An enthusiast’s take on what Windows File Expl... by badsectoracula on Sunday June 09, 2019 @04:12PM (#20141592)
Yes it is, if someone doesn't care about creating bloated applications they wont care about creating good applications either - which includes said polishing.
[ Parent | on HN ]
Re:Files UWP: An enthusiast’s take on what Windows File Expl... by Veen on Monday June 10, 2019 @04:09AM (#20144753)
A lack of concern for "bloating" does not entail a lack of concern for user experience.

Optimizing for size may be less of a priority when a developer is focused on creating a positive user experience and adding useful features. Obsessive optimization of factors that users don't care about can lead to crappy applications — see quite a few open source GUI applications as an example.

[ Parent | on HN ]