As I understand it, QT is good for embedded applications because it uses a very direct, weakly/efficiently abstracted API. You can do a lot with minimal computi

As I understand it, QT is good for embedded applications because it uses a very direct, weakly/efficiently abstracted API. You can do a lot with minimal computing resources. Putting something like chrome or firefox's rendering engine in embedded devices means carrying across lots of costly bloat or doing absurd work to slim them down. The only thing that might make QT hard to get into is the lack of enthusiasm for it, the sparseness of expertise, stagnant job market, etc. Things that are "not hip" in development usually have similar obstacles.