Skip to content
This repository has been archived by the owner on May 8, 2019. It is now read-only.

RSSOwl is pretty much unmaintained #8

Open
genodeftest opened this issue Aug 12, 2016 · 5 comments
Open

RSSOwl is pretty much unmaintained #8

genodeftest opened this issue Aug 12, 2016 · 5 comments

Comments

@genodeftest
Copy link
Member

genodeftest commented Aug 12, 2016

RSSOwl hasn't seen any updates in years. This results in some problems:

  1. At least on Linux, there are major security bugs within RSSOwl. See Internal browser on Linux (XULRunner) has many known security issues #7 for details.
  2. RSSOwl really needs to get ported to a more recent version of SWT and the Eclipse platform to support at least some of the now commonly used technologies such as touch devices, HiDPI displays and so on.
  3. There are many known bugs. Just have a look at RSSOwl freezes when trying to open PDF files/links #6 or the forums for Discussion, Help or Developers.

How do we fix this? or do we discontinue RSSOwl?

Although I am a repository owner to RSSOwl I haven't used it in years any I won't have time to get anywhere near fixing RSSOwl myself. And I think it would be a good idea to stop developing and using RSSOwl in favor of one of the other >100 open source alternatives to RSSOwl.

@isomorphisms
Copy link

thanks @genodeftest , I will check those out.

@isomorphisms
Copy link

I like having a desktop client (everything is on the web these days, so my browser crashes with too many things open). The first couple I tried on alternative.to cost $$.

@Albirew
Copy link

Albirew commented Jun 30, 2017

I'm still sticking to RSSOwl mainly because there's no other cross-platform RSS reader that support something as simple as feeds sub-subfolders.

@ghost
Copy link

ghost commented Oct 6, 2017

I sitll use and prefer RSSOwl. It was my replacement for the even more defunct Sharpreader. How much work are we talking about with regard to #2, a port to a more recent version of SWT and the Eclipse platform? Perhaps accomplishing #2 would fix some of the other bugs. I'm not a developer myself. What options are available for farming the work out and being able to put money toward it?

@genodeftest
Copy link
Member Author

I'd guess that about 50% of all classes need to be touched. Maybe 10%…20% of code needs to be rewritten. Out of ~300k lines of code that would still be >30k lines. If you pay someone to do that, I guess that's several months of full-time work.

You may try a kickstarter campaign.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants