Why not just run Linux locally? Mac OS X is BSD, not Linux, which means its build tools & environment are subtly incompatible. You're always going to be chafing if you develop anywhere other than in your deployment environment.<p>Linux is superlative for desktop & development use. It supports things like tiling window managers far better than does a Mac. It's free. The hardware is far more affordable. Although this is definitely a matter of taste, I find Linux far more <i>usable</i> than a Mac. I will grant that Mac laptops are lightweight & thin.<p>It just seems weird to me to go through all these contortions to develop software for Linux on a Mac or Windows box when it's far easier IMHO to just … run Linux.
Hey,<p>We provide an alternate solution ([1]Wormhole) that covers this scenario (and others). The main differences with e.g. Weave are:<p>- Non Docker-specific<p>- Easier to deploy, in my opinion ofc :-)<p>- Based on Open Source (You can just deploy SoftEhter's vanilla client as the agent)<p>- We don't use vxlan, just SSL encapsulation.<p>- Actually, every client will only generate outbound SSL connections, so chances are you won't need to reconfigure any firewalls or network gear for Wormhole to work.<p>- By default, chances are you won't overlap with the provided IP addressing (non-public, non-RFC1918 IP space)<p>- Multiplatform Windows / Linux / Os X<p>- API available to create and deploy networks and clients<p>- Our architecture requires traffic to go up to a central server and down to destination, so there's added latency. In my tests I've found this to not penalise performance for most applications as other solutions based on extra layers (I.e. Vxlan) like Weave.<p>Don't get me wrong, I think Weave is brilliant. We're just an alternative that aims for simplicity. There's some overlapping, but we probably have different markets.<p>[1]: <a href="https://wormhole.network" rel="nofollow">https://wormhole.network</a>
Offtopic, but does anybody know how the diagrams in this article were generated? I'd love a simple piece of software to generate beautiful, straightforward pictures like this to explain architectural problems.
Why do you need to connect to remote services using weave? Should the stage environment be separated from you development one?
Anyway nice article.
Thanks
I dream of a company that installs Linux on some of the most popular desktops PROPERLY, and charges users 100$ to install it, and helps you maintain your Linux desktop over the years.<p>Many have tried, no one has succeeded.<p>Canonical had an opportunity to do this... Instead, they had to do "Enterprise" stuff. Bah.
HN discussion about Weave being slow [0]. I dont know if the issue has been addressed since it was first posted.<p>[0] <a href="https://news.ycombinator.com/item?id=9498139" rel="nofollow">https://news.ycombinator.com/item?id=9498139</a>