Originally Posted by Chuck S
When it comes down to it that is the deciding factor. We can not control what goes on outside our program. We must do what is in the best interest of our software for all of our customers benefit.
With the modrewrite rule above I don't think this is a major problem, but I do feel I should put my two cents in based on this quote.
I don't know for sure, but I would think a lot
of your customers do use photopost (as a web application) integrated with other software and applications. As such, no matter how great the change is in theory, if it makes the overall customers website break over and over, it wont be such a great application to use. So if there are ways to maintain "legacy" functionallity that will make photopost all the better over time.
For example, if Nikon or Canon came out with the best new $5k DLSR camera body but changed the lens mount for a better "in theory" design making it only work with one new lens, it wouldn't sell nearly as well as bodies that work with all the standard mount lenses that people have built up over time.
Anyway, photopost is great
software. But in my opinion, it's ability to integrate into websites is a big part of what makes it so great, and that should never be forgotten.