Return to Answer

added 4 characters in body

Source Link

edited Oct 27, 2013 at 20:13

31.6k
12
6

There are a lot of loaded terms in the description in this question.

There are no easy answers to compatibility. My own packages tend to be very stable and backward compatible but they also have bug reports that have been open for 20 years as they can't really be fixed in a compatible way. Not everyone would say that is better. As @percusse says in his answer it's the package author's call, and in any case an existing document can always use the current package. tabutabu has some good ideas but it reuses the syntax of the standard arrayarray package in an incompatible way, which is an unfortunate choice, but neither that, nor the fact that the package author indicated he had changes planned, makes the package "dangerous".

There are a lot of loaded terms in the description in this question.

There are no easy answers to compatibility. My own packages tend to be very stable and backward compatible but they also have bug reports that have been open for 20 years as they can't really be fixed in a compatible way. Not everyone would say that is better. As @percusse says in his answer it's the package author's call, and in any case an existing document can always use the current package. tabu has some good ideas but it reuses the syntax of the standard array package in an incompatible way, which is an unfortunate choice, but neither that, nor the fact that the package author indicated he had changes planned, makes the package "dangerous".

There are a lot of loaded terms in the description in this question.

There are no easy answers to compatibility. My own packages tend to be very stable and backward compatible but they also have bug reports that have been open for 20 years as they can't really be fixed in a compatible way. Not everyone would say that is better. As @percusse says in his answer it's the package author's call, and in any case an existing document can always use the current package. tabu has some good ideas but it reuses the syntax of the standard array package in an incompatible way, which is an unfortunate choice, but neither that, nor the fact that the package author indicated he had changes planned, makes the package "dangerous".

Source Link

created Oct 22, 2013 at 18:11

David Carlisle

788.1k
2
48
73

There are a lot of loaded terms in the description in this question.

There are no easy answers to compatibility. My own packages tend to be very stable and backward compatible but they also have bug reports that have been open for 20 years as they can't really be fixed in a compatible way. Not everyone would say that is better. As @percusse says in his answer it's the package author's call, and in any case an existing document can always use the current package. tabu has some good ideas but it reuses the syntax of the standard array package in an incompatible way, which is an unfortunate choice, but neither that, nor the fact that the package author indicated he had changes planned, makes the package "dangerous".