Kristian: For the same reason they can't use Steamworks as is. You have use GPL incompatibly licensed libraries. If instead GOG were to distribute GOG Galaxy(including source code) under the MIT license this wouldn't be a problem.
JMich: Haven't really checked the GPL license, but what do you mean "incompatibility licensed libraries"? Assume that the client side API is available (packets require to be formatted as X, send to Y address) but the server side isn't available. Doesn't that cover GPL? If you send the server the packets it expects, it parses them and responds, if you send different packets, it ignores them.
Basically, the GPL says the following:
1. You can do whatever you want as long as you give credit where credit is due and anyone who gets the binaries can request the source code you built them from.
2. You cannot add new restrictions.
3. If a project contains any GPL code, then all code which links against it must also be available under GPL terms.
4. Do whatever you want with network protocols. The GPL stops at the edge of the program and imposes no restrictions on talking to other programs.
Points 2 and 3 are what force GPLed games to reinvent client libraries if they're proprietary. GPLed code is not allowed to be crippled by being shackled to components under more restrictive licenses. (The MIT requires a subset of the GPL and doesn't forbid adding new rules down the line.)
Point #3 is also why companies can get away with "open-source engine but you still gotta buy the CD-ROM for the art/music/sounds/levels/etc.". GPLed code has nothing to say about non-code stuff you distribute alongside it.
It works that way because the GPL was designed to protect what its creators call "the four software freedoms":
0. Freedom to run the program as you wish.
1. Freedom to study the source code of the program and then change it so the program does what you wish.
2. Freedom to help your neighbour. That’s the freedom to redistribute the exact copies of the software when you wish.
3. Freedom to contribute to your community. That’s the freedom to distribute copies or modified versions when you wish.
Fenixp: b) Developers! If GOG provides both API AND source code for the application, devs can actually make their own additions of features they would expect of the client - again, with no cost for GOG, but with the benefit of GOG saying whether or not that particular feature is acceptable.
Piranjade: To explain it to somebody like me (who has no clue) - there could be something the "Barefoot Essentials for GOG" for the client, modifying it in some ways? Or did I misunderstand that?
Barefoot Essentials is only possible because, by design, unless the entire site is written as one big Flash applet, the bits of a website that get sent to your browser are unavoidably open-source. (There's no way to compile the stuff the browser sees and nothing can be done to prevent Barefoot Essentials from playing around with the browser's internal representation of the site.)