Okay, so the memory thing might be off-topic depending on who is using the memory...
From my own experience: Windows code, even managed code in C# , can have horrible memory leaks You'd be astonished. Few are aware that certain types of managed C# code can leak memory like a sieve.
I only know this because of a robotics project I wrote years ago ... The control system was on Windows in C# with a GUI... After running for 30mins to 60mins , the system would crash. I finally noticed my process (all managed code) was steadily growing in footprint as you used the app.
There's a few ways this can happen.... If memory serves me... (1) The Microsoft OCR library leaked memory. (2) The worst offendor was Image or Bitmap (and their classes and superclasses), (3) A few other libraries that are standard in C#
You can easily find out by running your app and checking it periodically with a memory profiler.
I don't think this would apply to Go , as I seriously doubt Go leaks memory under normal circumstances
Wow your GUI looks slick ... That's Windows 8 , right? What are you developing it in?
I like your post "There is so much more information available through it and I like to see the status of my "mesh"" ... I agree with this .... However, I don't know if this will have 'mass appeal'. But it certainly appeals to me, heh.
"t should make the flows much easier, like adding a folder to multiple
instances does no longer need approval on every instance if you have
access through the REST-API."
That's actualy a clever idea. Would definitely make creating larger meshed networks easier (rather than log into each one via ssh and port forwarding for 8080).
Whoever put the Angular web services into Syncthing made a really really smart decision.