[bjarkeck]

So what you're saying is that it's okay for Windows Modern photo app to take 3 seconds to boot up and show an image on the monitor? And it's okay for the image to be blurry and misplaced in the first couple of frame, then corrected in the next couple of frames. And it's okay that it crashes once in a while too, and it's okay for it to be frames behind when resizing, because all of those things is simply the result of features and layers of abstraction that have some little purpose whatever that purpose might be. And you're okay with your software suffering for it?

To me, it's completely unacceptable and not the userexperience I want to give. Where do you draw the line is the question, but I personally want to provide the best experience possible.

The quality of software these days are extremly bad, buggy, big, and slow. And I'm not okay with it, despite how many reasons there might be. And the reasons for it is usually massive amounts of code, frameworks, and layers up layers upon layers of abstractions.

So you want your software to check updates? Well find a way that doesn't make the start-up time or user-experience suffer for it- otherwise don't implement it. That would be my answer to that. I know standards like that can be hard achive in a business, but those are the goals I want to become better at achiving. And to me, that's what handmade is about; giving me the confidence to build my own systems, making them more responsive, and provide a BETTER user experience. Maybe with less features, yes. But at least the features that are there will be extremly good!

[PaulDavisThe1st]

I'm not saying that any of these things are OK.

I'm saying that I know that my application does not start up as quickly as the hardware I personally run it on would suggest, and that I know why that is, but that doesn't help me know what to do about it.