rssguard

it) - PoweReader on my work iPhone https://powereader.app/ One neat thing about Miniflux is that it supports a number of APIs, including Fever and Google Reader. As long as your frontend works with one of these, you get a seamless experience. This level of choice is actually something I'm really enjoying-- I get a very native experience on whatever platform I use, as opposed to using the Inoreader app/website on each platform.

messaging). Plus, the UI/UX is pretty much regular Thunderbird as well, so nothing new there - it's familiar and usable.

with data races).

reason about than C++, since I know that unrelated function calls will never modify the target of a &mut T, and can only change the target of a &T if T has interior mutability. Nonetheless the increased complexity of Rust is a definite downside for simple/CRUD application code. On the other hand, when a programmer does write concurrent code with shared mutability (in any language), in my experience, the only way they'll write correct and understandable code is if they've either learned Rust, or were tutored by someone at the skill level of a Solaris kernel architect. And learning Rust is infinitely more scalable. Rust taught me to make concurrency tractable in C++. In Rust, it's standard practice to designate each piece of data as single-threaded, shared but immutable, atomic, or protected by a mutex, and separate single-threaded data and shared data into separate structs. The average C++ programmer who hasn't studied Rust (eg. the developers behind FamiTracker, BambooTracker, RtAudio, and RSS Guard) will write wrong and incomprehensible threading code which mixes atomic fields, data-raced fields, and accessing fields while holding a mutex, sometimes only holding a mutex on the writer but not reader, sometimes switching back and forth between these modes ad-hoc. Sometimes it only races on integer/flag fields and works most of the time on x86 (FamiTracker, BambooTracker, RtAudio), and sometimes it crashes due to a data race on collections (https://github.com/martinrotter/rssguard/issues/362).

ail/feeder-rss-feed-reader/jlkhefogiiibhgblliimeleiiiijbkjj) not an option, Windows Store app, i avoid that - Omea Reader (https://www.jetbrains.com/omea/reader/) by JetBrains, but requirements list Windows XP, so not updated in a long time - RSSOwl (http://www.rssowl.org/) based on Eclipse and fails to launch with new JDK versions - QuiteRSS (https://quiterss.org/en/screenshots) the layout absolutely breaks because image dimensions are not constrained, no one wants the header of the news story to fill up the entire screen - RSSGuard (https://github.com/martinrotter/rssguard) in the end i stuck with this, because just got tired because of so many bad options out there Apparently Google Reader was also pretty good but was retired. How is RSS supposed to survive if there is no good software for it out there? Give me something like LibreOffice that you just download, install and it works in surprisingly sane ways most of the time.