I've been routinely building ports with it over the last week. It's not bump-free *yet* but it works, and it's going to get better.
One good reason it's useful is because it allows people to use the same platform to build ports that they're running stuff on. Keeping the ports isolated in a corner. Another good reason is that it's *clean*. Create a chroot environment, put *exactly what you need in it* and build ports. No needs to depend on anything else. Also, it's intended to allow you to move to the new dpb model with several users painlessly, so that privilege violations (*cough cough* trojans) get caught up. You can also use it to quickly test experiments: assuming you've got a proot'd ports tree, doing a 2nd one *on the same partition* is very cheap: just links for files, so you mostly need inodes. Especially on ssd machines, this is very very quick. For instance, I'm going to play with chroot'd builds *without the .ph files*. Takes me about 10mn to set up, I can do it alongside "normal" bulk on the same machine... and that's cool. So far, I've been underwhelmed by the response to proot. Seems people don't get the picture yet. Rough edges, a bit. Definitely workable, as at least one other person can attest. It's not going to get better without more experiments. Mid-term, there should be better integration with dpb... and there are crazier long-term plans.
