View Single Post
Old 09-28-2014, 05:15 PM   #146
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,096
Karma: 148565303
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by eschwartz View Post
Just backwards compatibility, on the reasoning that there is no good reason to cut off support for old versions simply because you can, and because some people are legitimately stuck on old versions... although if you need to use Qt5-only features in order to make the plugin more useful, there is no reason to cripple it just for backwards compatibility -- and it isn't callous to do so.
But it is callous when backwards compatibility is removed for no other reason then you can do so. I fully understand when you cannot use Qt4 do to something in the plugin not working with Qt4. But if there's no reason it won't work with Qt4, then (IMHO) there's no real reason to remove (or not add in) Qt4 compatibility.
JSWolf is offline   Reply With Quote