I don’t have experience with either and it’s likely they could overlap in some way. Their advertised features seem appealing on both sides. The reason I set it up as either/or is because I’m not sure how practical it would be to implement both. Likely not a sensible idea.
So it’s either/or.
More importantly it has a “theme wrapper” that reenforces DRY principles and avoids the tediousness of dealing with many template part files.
Timber on the other hand is not intended to dramatically improve workflow, instead it is a plugin that allows theme development to separate logic from HTML by using Twig. So now instead of doing the usual of writing php in HTML, now it’s separated. It enforces DRY and MVC. It’s similar to Django in that regard.
I’m not sure if these two projects can be combined (maybe someone could do that).
So does anyone have experience with either project? Any opinions?