Deciding between Buildroot & Yocto

As a user of an OE-derived and yocto-based platform I must say that it has matured a lot over the last few years.
The first versions I had to work with left a very bad taste in my mouth with regards to maintainability (why does this happen? where does that variable suddenly come from? Why can't I enable this for everything at once? ...)

However, as attested in the article, some debugging features were added to relieve those issues. One can now track where each part of a variable comes from, there's pkgconfig support and more.

Still, one must question if the addition of these debugging features aren't just a plaster on an open leg wound. One must truly understand how bitbake parses and operates, one must become very familiar with the layers used before you can effectively and efficiently make an image out of it. There's a very steep learning curve to go through to make a proper image. Apparently that's one of the prices to pay for the extreme flexibility it offers.

Another downside is that there's a ton of legacy. It's true that there are many layers and many packages in them. But you can scrap a lot of them as unusable as-is because they contain legacy cruft due to a lack of love and care.

Finally, one must see that, as far as I know, yocto is the go-to platform in the industry. All big embedded-distro vendors are using it. This is probably a result of the design-choices stated in the article.
My advice would be this: if this is for a hobby project and buildroot can fill your needs, use it. If it's for business and you have time/money to invest or if you require a lot of flexibility, go yocto.