Will Haiku fall flat on its face ?

Recently we were all excited about the discussion of Haiku going Beta. All we needed to do was merge the Package Management branch into the main development branch and we would be good to go. Then....

The Package Management merge happened. This was a mistake.

The Haiku devs forgot that their work was so well received that Haiku has been slowly, steadily adding more and more users. With more users comes more applications development and more ported apps. Haiku was poised to launch into Beta with all thrusters firing. The Package Management changed all of that.

With Package management, The devs chose to make disruptive changes to the well established file system structure. They removed /boot/common, a directory tree that they have been attempting to get applications devs to use, with more success than they know. They also made most of /boot/home/config read-only. The exception is /boot/home/config/settings witch seems to now be poised to hold a lot of stuff that should be held in other locations under the ~/config tree. They added ~/config/non-packaged for add-ons, data, bin, and libs for non-packaged applications. They removed /boot/apps, part of the original BeOS file structure, and where most applications that have an installer place their binaries.

Right when Haiku was gaining a respectable applications portfolio, The devs broke most of it. One must consider the recent nightly images as pre-alpha quality and no where near the hoped for Beta.

At this point Haiku has stumbled like Microsoft did with Windows 8. Now the question is, Will they listen to the user and developer communities that are so desparately needed to succeed, or will they let Haiku fall flat on its face?