So I was fortunate enough to attend Palm's Developer Conference on Wednesday, February 9th.  And I am very happy to see that people are still behind WebOS after HP is putting more money into it.  I am more glad to see that HP is improving WebOS as a whole.  And now we have a new framework of WebOS to work with, Enyo.  I was a little skeptical first, but after explanation by Gary Norton in Q&A section, I was a lot more relieved.

Pros of WebOS 3.0

• Enyo framework is extremely easy to use, it uses DOM as a displaying device and saves you tons of time from DOM manipulation
• You can still use Mojo if you want, but company support is not 100% guaranteed on the legacy system.
• Ares will have some Enyo framework from the demo
• If you don't want any of these, you can still load up your web app into WebOS framework
• The IDE is your webkit inspector, this is my favorite part
• WebOS on HP Computers, which has a bigger install base than any cellphone manufacture

Cons of WebOS 3.0

• Too Many Frameworks, too many ways of doing the same thing, and it get's really confusing which route to take.

• Legacy support is unknown, for those who mastered Mojo, the skill sets that we spent a lot of time to learn are in jeopardy
• New skill to learn, in order for Enyo to mature and draw huge amount of developers, HP is really gotta show that they are willing to support them.

That's just my 2 cents from HP's Developer Conference.  I will be supporting it regardless, Enyo seems like a cool framework to work with not only for WebOS, but for Web as well because it takes out all the hassle on css/cross browser.  We'll see where this goes.  Good luck, HP!