If I paid for a device with a multicore processor I expect to take advantage of it through software. Otherwise, what's the point of multicore?
Sure, multithreaded code can be difficult to reason about but that only happens when you're not paying attention to what you're doing and, for whatever reason, want to release code as soon as possible.
My advice is to start small. And find a pattern suitable for your application. In your use case (an RSS reader) it makes perfect sense to distribute work among your cores as much as possible. You have a GUI, an I/O loop and some parsing. It's the perfect combo.
Please consider a future multithreaded version, your users will thank you.
Sure, multithreaded code can be difficult to reason about but that only happens when you're not paying attention to what you're doing and, for whatever reason, want to release code as soon as possible.
My advice is to start small. And find a pattern suitable for your application. In your use case (an RSS reader) it makes perfect sense to distribute work among your cores as much as possible. You have a GUI, an I/O loop and some parsing. It's the perfect combo.
Please consider a future multithreaded version, your users will thank you.