I haven't used it myself, and I've only just learned about it through this post.
Reading through the docs, though, it seems more beneficial if you are on a team of people. Seems like it basically combines Compose and a custom run/build script into one idea.
Personally, for my solo projects, I will likely continue using just compose for multi-service projects and basic docker run for stupid stuff. Unless I'm missing something, it doesn't seem like there is too much of a benefit with Bake if you're solo. It just adds more config files and json to your project IMO.
They even state as much in the introduction:
For simple builds, the difference between
docker buildanddocker buildx bakeis minimal. However, as your build configuration grows more complex, Bake provides a more structured way to manage that complexity, that would be difficult to manage with CLI flags for the docker build. It also provides a way to share build configurations across your team, so that everyone is building images in a consistent way, with the same configuration.
~~Reading the docs a little can go a long way in understanding.~~ My bad, didn't seem like you had read up on it.
ETA: Thinking on it more, it seems less useful to implement unless your project is 100% inside Docker. If you need to do other things besides build a Docker image or two from a compose file, it is much easier to accomplish what you need through a bash script that can interact with more than just Docker. Even if I did implement this, I'm going to end up wrapping the bake commands with a bash script any way.