On 2/5/15 3:08 PM, Robert J. Hansen wrote:
will create _some_ support burden. Is the code to support 1.x in
Enigmail really *that* difficult to work with/work around that it
justifies taking on these burdens now, rather than some time down
the road when more people have already transitioned?
Ah, the broccoli argument.
"I hate broccoli, but it's on my plate, and Mom and Dad won't let me
have ice cream until I finish all my food. So do I want to eat the
broccoli now or later?"
My vote: eat the broccoli now and enjoy the rest of your meal, rather
than try to enjoy your meal while dreading the broccoli.
Sorry, that's a poor analogy. In your example there is no cost
associated with eating the broccoli, other than your mythical child
having to choke down a food they don't like. You also ignore more
attractive alternatives, like the perennial favorite, just put some
ketchup on it. :)
Also, users have had eight years to transition. What are we supposed to
do, wait another seven years?
Straw man, argumentum ad absurdum ... should I go on? I didn't suggest
this, and agree that it's not practical.
Letting Enigmail users know today, "in
about a year you'll have to be using GnuPG 2.x with Enigmail," is hardly
ripping the rug out from beneath people's feet.
I'm not suggesting that either. What I have said several times now is
that there are still a large number of users on 1.x, and that making
this change at this time will create a large inconvenience to them, and
a large support burden for the Enigmail team.
You're saying, "I'm Ok with that," which is fine ... but Patrick
specifically asked for feedback, so I'm providing some. If the Enigmail
team is prepared to take on the support burden, and endure/ignore the
backlash from angry users, that's their choice, and not my problem. :)
Doug
_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
