I still use SlickEdit 32-bit because I have to maintain some old embedded products where the tools require 32-bit. The 32-bit requirement isn't for the software so much as the JTAG debuggers they use (drivers). That said, the current SE 32-bit probably does all I need it to do for that legacy support.
Currently, I also have a tool chain that we run in an XP VM. I am still running SE v16.0.3.0 32-bit for that. I would like to run the last version of SE for XP in that, but I don't know what version that is. And, I did not have maintenance in those days to get it.
That said, SE 32-bit today probably does all I need for legacy work. However, the embedded systems I work with don't use things like GDB, etc. that others might need. I just use SE as a strong editor, not a debug and scripting environment.
If SE does go 64-bit only, you could keep the last XP compatible version and the last 32-bit, non-XP, version available for customers that need it for legacy support. That is, (in the 64-bit only future) if you purchase SE, these two 32-bit versions are available to the customer as well. Of course, the legacy version will not have new improvements which is how I deal with XP now.
Regards,
Jim