Live data from Hacker News

WebOS 3.0.4 released

jaaksi.blogspot.com

11–20 of 33 posts

Re: WebOS 3.0.4 released

#11
post #10

Hi. I don't understand anymore. Didn't HP kill the tablet and WebOS? What does this mean? Will there new tablets? If not, why WebOS is being updated?

HP probably wants to keep it updated in case they can sell the WebOS unit.

Re: WebOS 3.0.4 released

#12

I am lucky enough to own a tablet of each breed, and my TouchPad is by far my favorite. Sure there are less apps by an order of magnitude, but HP nailed most of the core services. For example, mark all as read -- I've yet to find this basic feature on my Honeycomb tab or iPad.

You can now mark multiple emails as read in iOS5.

Re: WebOS 3.0.4 released

#13
Great for the many HP employees like myself who got a TouchPad in the employee fire sale, supposedly there will be a lot of TouchPads going out as Christmas presents. If nothing else, the current TouchPad population is one giant, if expensive, beta program for WebOS - let's hope someone does something awesome with it.

Re: WebOS 3.0.4 released

#14
post #12

I am lucky enough to own a tablet of each breed, and my TouchPad is by far my favorite. Sure there are less apps by an order of magnitude, but HP nailed most of the core services. For example, mark all as read -- I've yet to find this basic feature on my Honeycomb tab or iPad.

You can now mark multiple emails as read in iOS5.

mark multiple emails = O(n), mark all = O(1)

Re: WebOS 3.0.4 released

#16
post #10

Hi. I don't understand anymore. Didn't HP kill the tablet and WebOS? What does this mean? Will there new tablets? If not, why WebOS is being updated?

They killed the hardware. They have the #2 tablet by user base (admittedly due to selling many tablets at a loss during the fire sale) and do need to support them for a reasonable period of time, bug fixes and such, which is what this release is. They always said they wanted to keep the software alive.

Re: WebOS 3.0.4 released

#17
post #9

Yet did HP not announce there would be no more Web OS devices, HP needs to open source this. The more choice the better! I can see Samsung or HTC producing some slick devices running Web OS. Hardware was always a key issue for me, the Pre was slow and boring.

I forget, didn't people demo Android running much quicker on touchpad hardware? If so, it's the decision to depend too much on the JavaScript stack and not the hardware that's the ultimate problem.

Re: WebOS 3.0.4 released

#18
post #14
post #12

Earlier quoted context omitted.

You can now mark multiple emails as read in iOS5.

mark multiple emails = O(n), mark all = O(1)

"Mark read" is a broken interaction anyway. You only ever use it when you haven't read the message.

So why do people do it? I do it to clear out messages that aren't worth reading, to get that number of unread emails in my Inbox folder down to 0.

Why do I care about unread messages? What I'm really worried about are unseen messages, and the set of unread messages contains these.

"Read/unread" and "Seen/unseen" are really just labels anyway, right? These could be automatically applied on seeing the message in a list view and on reading the message.

Now I have some sort of cool multiple-select label filter in place, and all I need to do is select the "Inbox" and "unseen" labels to get to email that I need to peruse. Every time I look at this label combination, all mail is marked "seen" and I never have to check off messages or apply a "read" state to messages that I have not read.

Notmuch (notmuchmail.org) gets close to what I want. I want to see its ideas adopted by the major webmail/mobile interfaces, so I don't have to contend with the legacy of email sorting.

Re: WebOS 3.0.4 released

#19
post #9

Yet did HP not announce there would be no more Web OS devices, HP needs to open source this. The more choice the better! I can see Samsung or HTC producing some slick devices running Web OS. Hardware was always a key issue for me, the Pre was slow and boring.

I forget, didn't people demo Android running much quicker on touchpad hardware? If so, it's the decision to depend too much on the JavaScript stack and not the hardware that's the ultimate problem.

Android really doesn't run quicker than WebOS yet. There isn't any 2D hardware acceleration (last I knew, a few days ago). This means that sometimes Android is really fluid, but then it starts studdering and kind of ruins the experience.

I also had a ton of Force-Close's on the browser. I'm back to WebOS until the Android CM7 builds get past Alpha. It looks like it'll be usable, but not really yet.

Post reply on HN