PaulStoffregen
Well-known member
I designed the Teensyduino installer to be completely stand-alone without any network communication. Same for Teensy Loader and every other part of the software. I personally don't like programs that "phone home". But I've been considering adding a version check, where it would do a network name lookup to discover if a newer version has been published.
I've also been debating whether a new version message ought to appear early, or do it only on "demand" when some error occurs. Also up for debate is whether to nag the user, or only show it when the installer can't recognize the folder or when compiling fails on any library or other files that aren't part of the user's sketch.
This won't happen anytime soon... but perhaps after Teensy 3.5 & 3.6 are shipping and libraries like Ethernet and USB Host are working....
In the meantime, what are your thoughts on this? Is phoning home something we pretty much accept software does these days? Is it worthwhile, if users can be given more relevant error messages advising them a new version is available which might address their issue?
I've also been debating whether a new version message ought to appear early, or do it only on "demand" when some error occurs. Also up for debate is whether to nag the user, or only show it when the installer can't recognize the folder or when compiling fails on any library or other files that aren't part of the user's sketch.
This won't happen anytime soon... but perhaps after Teensy 3.5 & 3.6 are shipping and libraries like Ethernet and USB Host are working....
In the meantime, what are your thoughts on this? Is phoning home something we pretty much accept software does these days? Is it worthwhile, if users can be given more relevant error messages advising them a new version is available which might address their issue?