(In reply to comment #6)
> Given my opinion of web-based applications (both performance and
> convenience-wise), It's really an embarassment to KDE
Yeah, this bug basically renders the Akregator useless, i've started browsing pages with standalone browser again.
Somehow in opensource model where everyone can focus to tasks they see themselves interesting, this kind of showstopper issues don't get the attention they would deserve and whole movement suffers. With this I mean that KDE4 already has all kind of bells and whistles which most of people would be happy without, but then again we failed to even fullfill the core functionality of KDE3. Yes, we all know it's coming, but it should have landed already.
I even tried to get tags enabled in bugs.kde.org so that we could get an overview to the regression items, but that request got buried since KDE uses tags for release process instead of milestones.
(In reply to comment #6)
> Given my opinion of web-based applications (both performance and
> convenience-wise), It's really an embarassment to KDE
Yeah, this bug basically renders the Akregator useless, i've started browsing pages with standalone browser again.
Somehow in opensource model where everyone can focus to tasks they see themselves interesting, this kind of showstopper issues don't get the attention they would deserve and whole movement suffers. With this I mean that KDE4 already has all kind of bells and whistles which most of people would be happy without, but then again we failed to even fullfill the core functionality of KDE3. Yes, we all know it's coming, but it should have landed already.
I even tried to get tags enabled in bugs.kde.org so that we could get an overview to the regression items, but that request got buried since KDE uses tags for release process instead of milestones.