Hello all.
Concerning the Reactor speed issues, I'll just post our response to that here as well:
Yes we are noticing the same. Rest assured we're looking into this, everyone. Unfortunately there's a bit of bad luck involved here. One of the new features of Reactor 2.0 is that it
does have a working caching system that updates content only as needed. There are a few small core files left to receive the same treatment plus there's obviously a check on startup for new content with an active internet connection. Those files are so small and our many tests ran so smoothly that we did not consider that step a critical priority.
But, I kid you not - on the very day of the release, GitLab
started having major issues with API access and they have been lasting for days now. It's been a while since I've seen 1kb/s download speeds... So we're looking for alternatives there, too, with the obvious choice being GitHub.
It's a shame really, because when GitLab is optimal - the issues are intermittent - Reactor really flies.
So please bear with us and let's for the moment hope that the GitLab issues are only very temporary.