Well: If you read through this thread you will find out:
1. This add on has been released four years ago as beta and has not seen a single update since then.
2. The author of the add on
@Scandal has stopped participating in this thread or answering questions roughly 2,5 years ago. He is still active in the forum here and did not mark the add on as "unmaintained", so state and future of the add on are somewhat unclear.
3. A bunch of people are using the add on in their forums and are more than happy with it, smaller inconveniences aside
4. Until now noone seems to have tested or used it on XF2.3 (or if so not reported about it), so it is somewhat unclear if it will work flawlessly on 2.3 as well.
5. As with every add on that has a bit of complexity it is a wise idea to play with it on a test instance of the own forum before taking it live. There have been no showstopper issues reported, but one never knows if that's true for the own forum as well and if it fits the own expectations anyway.
So the situation is pretty clear. Nevertheless
@TheLaw grumbles about the add on being labeled as beta and associates whatever he personally associates with beta software and claims that there would potentially be massive hidden issues with it - despite not having tested or used it and ignoring all the positive feedback and reviews for the addon in this thread. He even claims there would be no feedback. This is what I would call
Plain phantasy with no relation to reality and even actively ignoring what's on the table.
Fact is in general: With XF add ons, especially free ones, you never know what you'll get w/o having used or tested them and you never know if and for how long they will be actively maintained, what quality the code may have and you never know if it will work on a future release. So at least in my eyes it is always a bit of a bet and one should try not to become dependent from a certain add on on the own forum and be aware that with a major XF update one might be in trouble and might have the need for alternatives or to loose the functionality the add on provides. There are some exceptions with some add ons where one can be quite sure that they will be supported in future, but even with those you do have the risk of the truck factor as most add on developers are a one man band and accidents and unforeseen life changes do happen.
With this add on in particular it may or may not turn out that it works or not on 2.3. Easy to test. If it doesn't work the four alternatives are:
1. Stay on 2.2
2. Try to convince the add on author to make it compatible (if necessary by throwing money at him)
3. Fix it yourself for yourself
4. Find an alternative way to deal with glossaries
Until now nobody knows if this is necessary at all, still one should be prepared that it might not work with 2.3 though no one knows the probability for that as no one seems to have tested it so far.
All the speculations could easily be ended if someone did a test on 2.3. I surely will do that at some point - until now no need as I am still happy on 2.2.