okay then tell me how long you need to finish your projects?
I made a snake game in Assembly in about two weeks. I used no third-party APIs, no high-level control, nothing. I'm very proud of the game.
All I needed was Assembly and Windows OS for some slightly "higher" graphics control.
Now, let's compare it to a C++ snake game ...
1.C++ snake game probably has a higher tendency of getting stuck, having a bug due to complicating high-level codes/functions, eating up more RAM and putting your CPU through torture.
2.C++ snake game needed endless additional files for additional support for keyboard input, timing, an input output stream(crappy one), etc.
3.C++ snake game probably doesn't perform in the exact, 100% way you'd expect it to and although the code is more readable it isn't more efficient.
Now, let's change it to Assembly's snake game ...
1.Assembly's snake game has almost no possibility of getting stuck due to low-level access of hardware, controls and operating at a bit-level way better than you would in C++ or other high-level languages.
2.Assembly's snake game doesn't need thousands of DLL files, .lib files, .h files, .win files, etc. All of that can be optimized directly and requires less storage of shit! Plus, files can be written all into one source and controlled through one executable output rather than having tons of damned files roaming all over endless directories!
3.Assembly's snake game is not only going to be faster, will have less likelihood of acting up of failing to catch input, but will perform more smooth, efficient and will require less complication and waste of space and will have EVERYTHING put to use rather than tons of crappy files that just "sit there in case I need them".
Assembly > high-level.