Hacker News Reader

I had the opposite reaction. They decided to reimplement almost everything and pushing hard on reactive stream, but their documentation is horrendous and the API is super complicated. After a month of tinkering I just gave up and used spring boot.

View on HN

Please don't use Reactive in Java. Stick to plain imperative - and you'll be compatible with Project Loom in the future.

I don't see how using Reactive makes you incompatible with Project Loom.

I meant using the Reactive API types like using Publiher<Response> in REST APIs. These will be un-necessary in the future.

I almost fall into the same trap. Lucky the documentation for reactive approach is very lacking, and I'm lazy, so I stick with traditional approach.

Reply on news.ycombinator.com