Modern OpenGL wrapper abstractions (shaders)
Use glDetachShader() after linking the program.

Shaders are ref-counted on the driver side and prevented from cleanup until they have been detached from all used programs. You are hogging GPU resources for no good reason.
GLchar info_log[log_length - 1]; : eeep!

On top of being dangerous (you could possibly end up allocating megabytes of memory on the stack), it's not even legal C++. Just use a std::vector&lt;char&gt;. 

Also, that -1 gives me the heeby-jeebies. It's just one byte, copy the null terminator.
Your way of loading an entire stream in a string is pretty awful and slow. You should figure out the length, make a single allocation, and read all the data at once like so:

input_stream.seekg(0, input_stream.end);
auto length = input_stream.tellg();
input_stream.seekg(0, input_stream.beg);
std::vector&lt;char&gt; source(length);
input_stream.read(source.data(), length);

Holding on to loggers as member variables is pretty bad in general. I have never seen a production system that requires that kind of granularity, and the multithreaded handling of these shared_ptr&lt;&gt;s could come and bite you in the future. Loggers are definitely one of those things that belong in singletons/global variables in my opinion.

Or even better: throw an exception with the error as its content. Let higher-level code handle the logging.
The create() functions should be invoked in the constructors (or just be the constructors). That's the whole point of RAII: bookending resource management in constructors and destructors. An additional benefit is that you won't need to keep the path and loggers around, just the GLuint.
On that same note, destroy() should just be the destructor, for the same reasons as above.
Speaking of destroy: in your current version, what would happen if destroy() is called and create() was not? Any sequence of invocations of the public interface of the class should be expected and handled (if only with an assert at worst).
void create(std::initializer_list&lt;Shader *&gt; shaders);


This is pretty constraining interface-wise. It's okay to have an initializer_list-based overload, but your primary interface should be a std::vector&lt;Shader*&gt;, or even better: a pair of iterators (or range if your code base has them).
I don't like the casts to GLuint as accessor for the programs. If you are going to have a wrapper, the wrapper should be handling all interactions that require the native handle if possible, and selectively give access using friend where absolutely necessary.
Finally, a heads up: this is pretty bare bones. You will find that once you start adding data-driven handling of Uniform Buffers Objects (you are talking about modern GL, after all) and vertex attribute bindings, a major refactor of all this code will almost certainly be needed.


Edit elaborating here instead of the comments:


  I've been told not to include too much work in constructors, and considering it's calling GL functions I figured that was considered a lot of work.


The primary role of a constructor is to establish the class invariant (the states the object is allowed to be in be in between public function calls), which you should always strive to keep as constrained as possible, because every public function should handle any and all valid invariant states. In your current code, the invariant for Shader is: The GLuint handle is either undefined, pointing to a valid shader, or pointing to a failed shader. 

A better alternative would be: The GLuint handle points to a valid shader. Note that you cannot establish that invariant without using exceptions. 

Limiting work done in the constructor is good, but not if it comes at the cost of a having to widen the invariant.

Similarly, keep in mind that unless there is a bug in the code, you can always count on the destructor being called, even in weird exception-handling scenarios. That's why releasing resources is always best done there. Doing the cleanup in there makes it so a user of the class can never forget to call destroy().


  I've also been told that initializer_lists are lightweight, thus its use. Thoughts on any of that?


They are lightweight, but fixed in size at compilation time. What if you wanted to load a list of shader to put in a program from a file? Again, they are fine as a secondary overload, but should not be the primary interface unless you can guarantee that the length will never be data-driven.