4 ms·
> What, exactly, is wrong or selfish with saving dev time to work on something more important to the end user? Even if that's another product entirely? It's si
by lazyjones 8y ago
> What, exactly, is wrong or selfish with saving dev time to work on something more important to the end user? Even if that's another product entirely?
It's simply completely irrelevant what the developer might or might not be working on also in your imagination, when we are judging the product based on its technical merits.
Inventing some extremely important better use of the developer's time to justify inflicting a wasteful 55MB download on the world, is a strawman argument of the same quality you complained about.
- MaulingMonkey 8y agoI deal with programs that crash OOM on 32GB+ machines. I deal with products that actually have a million users, with gigabytes of download. I don't need to invent anything that the developer could be working on, existing problems to work on are abundant. And I don't even work on anything important! But more important than this color picker? I'm pretty sure you could think of concrete examples of that too, without resorting to imagining anything. And if we're limiting the discussion to just the technical merits of a product, I'm not sure why you started discussing developer time and expense at all. You're the one who brought up "dev time vs millions of users hardware", and I'm just pointing out that it's perhaps more realistic to view this as "dev time" vs "thousands of users hardware" in this particular case, and that there's a lot of mildly important things the developer could work on instead.