Recs.
Updated
SpecsUpdate
Pros
Pro A visual scripting system for non-coders enables quick prototyping
Blueprints are authoring tools designed for non programmers so designers and other team members can help tweak and prototype. UE4's Blueprint scripts resemble flowcharts where each box represents a function or value, with connections between them representing program flow. This provides a better at-a-glance indication of game logic than a simple list of events, and makes complex behaviors easier to accomplish and games a lot faster to prototype.
Pro Free development license, including source code
The engine, including full access to source code, is free to use; a 5% royalty is due only when you monetize your game or other interactive off-the-shelf product and your gross revenues from that product exceed $1,000,000 USD.
Pro Fast compilation for quick iteration
Recompiling an entire game to test a small change takes up a lot of time. UE4 quickly compiles in seconds instead of minutes improving iteration time by an order of magnitude.
Pro Professional feature set for all aspects of game development
Almost everything a game developer wants has a deep and sophisticated tool waiting for them in UE4. No external plugins are needed to make powerful materials, FX, terrain, cinematics, gameplay logic, AI, animation graphs, post process effects, lighting etc.
Cons
Con Slow
Compared to other engines, UE4 seems to perform various actions considerably slower. Actions like starting the engine, opening the editor, opening a project, rebuilding shaders, updating references, calculating lightmaps, saving projects, etc take long enough to get irritating and end up wasting precious development time.
Con C++ - oriented development cycle: slow turn-around times
The Unreal Editor is the main place to do stuff (of course), so if someone wants to do a lot of C++ stuff, the compilation and linking turn-around times can be painful. Still they probably are quite fast in comparison to the provided featureset.. Still ,they are far from optimal.
Con Poor documentation
Most of the "documentation" for code is actually just automatically generated from the source. If you're interested in knowing how things are supposed to work, you must either go to their answers site or pay for UDN.
Often their examples won't even compile, since they were written for now outdated versions.
Con C# not natively supported
UE4 does not support C# natively, but this can be achieved through MonoUE, although it requires using the MonoUE fork instead of UE itself.
Con Unreal Engine crashes a lot if you don't have the required system requirements
Con Extremely poorly designed
The code is a mess.
Everything is connected, a single Actor is 1500 bytes, because it contains a million things that Epic once needed in a game.
Inheritance for AActor: AActor > UObject > UObjectBaseUtility > UObjectBase
Con Tutorials do not go in-depth enough
The blueprint tutorial just teaches how to turn on a light when you press f.