It's not like it isn't a useful thing to learn, I've had people ask me why I've used winapi in some of my programs, there are plenty of reasons.
If you're starting it is fine, but creating your own library all you're doing is what you have to do in the future that is to build your own things not using third party or open source libraries. Having full control of your application is essencial in my opinion
Mind explaining why you think it is essential to have "full control" over such a well defined and solved problem as windowing, which SDL (amongst other frameworks) provides a good (platform independant) solution to? I can understand wanting to do it, but I cannot see how it would be essential to have low level control over such a thing..?
My rule of thumb besides tinkering around with winapi to learn more about it, is only use it if I'm writing everything else from scratch anyway. I definitely would suggest SDL or SFML if your focus is more on just getting a game together though.
- SDL/SFML/Some windowing library, isn't always going to be good enough, it also introduces a dependency you may not want to have.
- It's good to do it a few times, IMO, too many people here comment like you should avoid things they already learned even though understanding.
- An example of learning might be: how the OS painting and GDI works is useful, or how raw OS messages are actually given and translated by libraries into a more friendly form. Things make a lot more sense after you learn them a bit.
If is just a game you should use an existing game engine to the job since is 10x higher level than libraries such SDL, SFML, etc.
Agreed, unless you got some other motive, like you want to do it for fun or as a learning excercise. I also understand the reasons listed by Satharis and I agree that it is indeed useful to learn. What I dont get is why it would be essential to have full control over windowing..