Hypothetical (that’s not so hypothetical at the moment):
MacOS and Windows both include code to a certain thing. (We’ll call that the “platform code”.) It’s fast and works for the vast majority of cases, but fails the standard unit test provided by the maker of the thing. The failures range from some (Mac) to lots (Windows), but are not representative of typical use in either case.
Meanwhile, I’ve created code that is cross-platform and passes all the tests, but is somewhat slower than the platform code. (We’ll call mine “Xojo code”.) (“Slower” means a high percentage on the microsecond scale, like 3 µs vs 6 µs per usage.) It also requires more memory upon first usage, let’s say about 5 MB that persists.
It’s come time for me to publish my package for general use, so I have to decide which way to go. What would you do?
- Include just the slower but better Xojo code
- Default to the Xojo code but include the platform code as an option
- Default to the platform code with the Xojo code as an option
- You have too much time on your hands
0 voters
