Cross-platform GUI framework for C++

So far I've only done command line programs in C++. I want to make GUI programs in it now though. Should I use Qt or GTK+? Or something else?

It's almost 2019. Just use Electronjs

>>2
Very funny.

>>2
what if I don't want to use too much ram and have memory leaks?

Win32 or GTFO.

>>5
Win32? Buddy, it's been renamed to Windows API.

(Note that this was formerly called the Win32 API. The name Windows API more accurately reflects its roots in 16-bit Windows and its support on 64-bit Windows.)

https://docs.microsoft.com/en-us/windows/desktop/apiindex/windows-api-list

>>1
The rule is to never use gtk for anything.
Go for basically anything else, Qt is a good choice as it also has a great IDE (Qt Creator) which also allows you to design your GUIs in a way similar to Visual Studio.

>>5
how is this cross platform?

>>8
Wine

>>1
Probably SDL+some simple GUI lib, like one of these:
https://github.com/dalerank/nanogui-sdl
https://github.com/vurtun/nuklear
Note that I haven't actually tried one of these, so yeah, try at your own risk I guess.

>>10
Please avoid SDL. It is one of the worst libraries.

>>11
Why?

>>12
Many reasons actually. It has all kinds of useless bloat in it that pollute the namespace and make it harder to port (threads, Uint32, etc). It forcefully installs handlers for multiple signals, removing your own in the process (they removed the option to disable that recently), it lacks the ability to draw filled polygons - which is literally the only thing that one would want to use a bloated library like that, with the version 2.0 they split up the nice and cool surfaces into surfaces and textures which created a giant mess, some functions (such as SDL_AddEventWatch) do not return an error if they fail, etc.

So... GTK+ or Qt?

Why do you need it to be xplatform? Windows is the only env that matters. Mac is a closed market and Ubanto boys will default to the command line.

>>14
Qt