Recs.
Updated
SpecsUpdate
Pros
Pro Highly configurable
Awesome is highly configurable, allowing the user to change anything they see fit in order to make the WM work for them and their workflow.
Pro Tags instead of workspaces
With awesome, clients are organized with tags: one client can be on more than one tag, and multiple tags can be displayed at the same time.
Cons
Con You should have some skills to configure it
Awesome, like most window managers, is targeted at advanced users. Though is has sane defaults and easy to read documentation, it is still a far jump from the more common graphical UIs found in computing.
Con Pull requests for bug fixes take forever to get merged
Due to the number of devs required to do checks on the pull requests, they take upwards of 6 months before being merged into the main. This means if you need one of these features or fixes, you have to build from the source using that branch (which if you use the dev branch you probably already do).
Con Configuration uses Lua (Programming Language)
It is time-consuming to make changes to configuration. Though Lua is a good language, a plain text file to configure things would seem to be a better approach.
Con Difficult to google for solutions to problems
Awesome is a very common word, making searches for solutions to problems using Google very time-consuming as a lot of chaff has to be sifted through.
Recommendations
Comments
Flagged Pros + Cons
Con Re-size buggy
This is more a case of personal experience with awesome, that some Windows are not re-sized properly.
Issues can include: terminals not re-sized to the bottom of the screen to re-sizing back to 1 pixel size, awesome cannot move windows or re-size panes, and awesome doesn't re-size contained windows properly (observed with Hangouts Chrome extension, for example).