The current 3DSlicer only supports Qt5.15 version, which is embarrassing.

Correct.

I would recommend to use VTK’s stable, high-level, platform-independent APIs as much as possible. These years is not a good time to develop anything with lower-level APIs, because OpenGL is going away and WebGPU is not yet fully supported in high-level toolkits, such as VTK. If you have some very special needs that require lower-level access now then probably OpenGL is your best bet, VTK offers many extension points (e.g., shader replacements), but it is not easy to learn and in a few years you probably need to redevelop everything in WebGPU.

Because by building on a platform they can save tens of millions of $ of development and maintenance costs. They don’t have to reimplement all the essential features that nowadays everyone expects from a medical imaging software, and they get continuous updates for free, so they don’t need to worry about their application not working on a new version operating system version, new hardware, new graphics APIs, etc. The tremendous amount of money saved in this way can be used instead for doing developments that matter, that differentiates the software from the others, that bring value to the customer.

1 Like