Though the thing is, can't you put in more functionality into it somehow? Maybe like extract what graphics card is being used or something like that. Just having an object exist feels inappropriate. If some functionality like that is put into it then Environment would be a perfect fit also give it a more logical existence.
Could be confusing, people would focus on these members (because they are the only ones) and forget that the main purpose of the class is to create a valid graphics context.
Moreover, they wouldn't get these features with "regular", contexts created through sf::Window.
Just came up with a use of this, if you can get a hold of the drivers version number, you can do a check-up and look if the drivers are old and warn the end user to upgrade his drivers. League of Legends does that when you enter a new game.
Hum... Assuming that I leave the definition of "tool old" to the end user, and simply provide the version number, it's already quite difficult.
Maybe I can get something interesting with glGetString, but then it would probably require parsing the result according to the graphics card vendor.
