Well absolutely. I think there's some really strong developers here; it's a good way to learn from others.
In terms of ClickOnce, it's been about 4 years since I deployed it on a corporate LAN. If there's better stuff out there, then by all means use the best. I'm not familiar with Inno , but it sounds like you are on top of all of that. So I've no idea what Inno Setup is but it sounds newer than ClickOnce, haha. I must be dating myself here
"So yeah I'm thinking we write a FORTRAN client next...it's really blowing up on AIX systems these days..."
Currently I'm reverse-engineering the protocol with Wireshark. I got all the traffic decrypted thanks to some help from the main developers, and right now I'm writing a Wireshark plugin for the BEP protocol. I'd like to be able to see exactly what's happening under the hood -- perhaps there can be enhancements made... Or at the very least, for my own understanding, I'd like to contribute some additional documentation for BEP and the REST API, and open-source the Wireshark protocol decoder module. That way people can debug their own code over the network, and we can make some slick developer documentation.
I do really enjoy creating UIs in Windows (C#) or Java (cross-platform) ... It's more art than programming (for me anyway) to get a nice user experience... That said, since all development has moved to this whole Web2.0 world, there are fewer and fewer desktop apps. The only place where apps are blowing up is in mobile. I suppose the whole REST API will come in very useful for all of this.
I do know that I have been mulling over the BEP protocol for awhile . . . Just as a thought experiment to see where this can go.
One thing I am 100% confident in (besides the ability of the developers here) ... I'm very confident in the desgn and structure of the Angular REST code and the control protocol. It's absolutely fantastic. I've been very surprised and impressed. It's not easy to write good Angular.js code, but this is really state of the art.
So my overall point is this: I get the reasoning for not bothing with a native GUI. It might be fun, and I've been toying with the idea as well, but the usefulness is questionable... HOWEVER... since the REST API is so robust, really we can make a GUI client in just about anything pretty quickly. Any language, more or less. And I'm sure the UX/UI will continue to evolve and improve, for all the clients.
Github is great -- I agree. The only problem with Github is it can be confusing for the end user who doesn't work in the indusry. I like the idea of dumping everything on github so developers can fork and issue pull requests , etc... And then for a 'release' cycle... You have a rolling weekly release that's auto-built, and then you have official 'stable' releases linked off the main web site. I think that's more or less how things are set up now, so that's cool.
No no... I don't speak another language besides conversational Spanish. "Dame más cerveza" . I meant I'm polylingual in everything except the more modern languages like Scala and Go. Mainly Python, Java, and C/C++/C#.
When I get the opportunity, I'd love to install and check out your code in detail. From the brief look I took at it, it seems really cool. I meant more if you get bugfixes or feature requests as open Github issues, I can probably knock those out pretty quickly since I know C#, then issue a pull request back to your repo with whatever issue is open.
But anyway, great job, and kudos to everyone who's been coding on this project , whether for Syncthing Tray, Syncthing GTK, or the reference Go implementation. Not easy work, but certainly something to be proud of.