3 ms·
>And hardware is cheap nowadays. Cheap and available (and correctly setup) are not synonyms, however. In the years I observed how - generally speaking - progr
by jaclaz 7y ago
>And hardware is cheap nowadays.
Cheap and available (and correctly setup) are not synonyms, however.
In the years I observed how - generally speaking - programmers (correctly as it is their work) tend to have the best of the best in hardware (and a fast LAN, and a fast WAN, etc.) so locally where the program is developed it feels fast, responsive, etc.
But the user base may have older processors, less RAM, slower mass storage and slower WAN/Internet access, so at their end the same program will appear slow, in some cases so slow to make it unusable.
I always thought that at the developers there should exist a few reasonably old machines possibly with installed the same services/other tools that the client target machines normally have where the program should be tested for excessive increased slowness compared to what happens on the development machines.
- mratsim 7y agoThankfully, Travis, Azure Pipelines and Appveyor are slow as molasses and if you are forced to wait for them before merging a commit you will optimize the speed so that at least CI is reasonably fast.