This post states
B-trees supersede T-trees and are far more concurrent for multi-threaded, multi-core, multi-user data access and thus scale a lot better.
The above post is the only resource I could with much detail between the types. The TT documentation just says that B+tree indexes are the 'newer option that can offer concurrency benefits'. The two types of range index are not mentioned in the documentation's
So my question is - is there any reason at all that when using range indexes we should not exclusively use B+tree indexes in place of T-tree? It sounds like it's a no-brainer.