> sudo curl -L git.io/weave -o /usr/local/bin/weave Do you want ants? Because that's how you get ants.
But it redirects to https. That's secure, right?
Weave and Docker for Mac: The bridge between local and remote services
31–40 of 45 posts
Re: Weave and Docker for Mac: The bridge between local and remote services
#32HN discussion about Weave being slow [0]. I dont know if the issue has been addressed since it was first posted. [0] https://news.ycombinator.com/item?id=9498139
It has, now Weave is kinda fast :) See http://weave.works/weave-docker-networking-performance-fast-... http://rp.delaat.net/2015-2016/p50/report.pdf Full disclosure: I work at Weaveworks
[deleted]
Re: Weave and Docker for Mac: The bridge between local and remote services
#33HN discussion about Weave being slow [0]. I dont know if the issue has been addressed since it was first posted. [0] https://news.ycombinator.com/item?id=9498139
It has, now Weave is kinda fast :) See http://weave.works/weave-docker-networking-performance-fast-... http://rp.delaat.net/2015-2016/p50/report.pdf Full disclosure: I work at Weaveworks
It's terribly slow unless you don't care about encryption: https://github.com/weaveworks/weave/issues/1925
The per-packet processing overhead is a real and unresolved problem.
I'm using Rancher's networking now instead. It uses ipsec between hosts, so everything gets handled by code paths which have been optimized in the kernel, and performance is good (especially if you have a not-ancient CPU and have the AES-NI instruction - then wirespeed gigabit works with acceptable overhead).
I like Weave's decentralized architecture and wish it were realistic to use it.
If they are going to stick with a user-space solution they probably need to use DPDK or one of the other high-performance software defined networking toolkits, which tend to process packets using a SIMD approach.
Re: Weave and Docker for Mac: The bridge between local and remote services
#34Earlier quoted context omitted.
>There's simply a large number of high quality tools which are not available for Linux Developer tools? Like what?
Visual Studio, XCode, Adobe , anything by Autodesk... As good as alternatives like GIMP are, they simply can't compete with their Mac/Windows alternatives like Photoshop.
Both XCode and VisualStudio are proprietary IDEs designed to support building apps for their respective operating systems. If you're writing a Windows native application, you will find Visual Studio on Windows to work the best, likewise if you're developing a Mac OS X native application then XCode on OS X is the smart choice.
In my opinion, neither one is well suited for building a native Linux application nor the sort of applications that would need a Docker container in which to run (web application, etc.)
Re: Weave and Docker for Mac: The bridge between local and remote services
#35Why 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. 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…
I love Linux, but saying that the desktop use is "superlative" is a bit, let me don my fire retardant suit, wrong. It's a decent enough desktop system, but it falls markedly behind in terms of tooling. There's simply a large number of high quality tools which are not available for Linux, which means that you have to resort to an open source tool which, while decent (and sometimes even fantastic), are still nowhere ne…
I build mostly web applications (Java, Ruby, etc.) and I have missed very little after moving from Mac OS X to Linux. OmniGraffle is the only thing that I really miss.
That said, I am not a graphic designer.
Re: Weave and Docker for Mac: The bridge between local and remote services
#36Earlier quoted context omitted.
It has, now Weave is kinda fast :) See http://weave.works/weave-docker-networking-performance-fast-... http://rp.delaat.net/2015-2016/p50/report.pdf Full disclosure: I work at Weaveworks
It's terribly slow unless you don't care about encryption: https://github.com/weaveworks/weave/issues/1925 The per-packet processing overhead is a real and unresolved problem. I'm using Rancher's networking now instead. It uses ipsec between hosts, so everything gets handled by code paths which have been optimized in the kernel, and performance is good (especially if you have a not-ancient CPU and have the AES-NI ins…
IPSec is still pretty slow. While it might be fine for X DC stuff, without a real private network you're not going to find the low latency that makes microservices attractive.
Re: Weave and Docker for Mac: The bridge between local and remote services
#37Earlier quoted context omitted.
I just took a new job in a company that uses Dell and Linux for the main OS, coming back from 4 years in another company where macs were the thing. Let me tell you: it sucks. - Lockscreen disapears when my session is locked, I have to type my password blind.. - Scrolling sucks, plainly. The trackpad registers clicks when I don't want him to, leading to me moving text around when I just want to move the pointer.. it's…
Indeed. Went from developing primarily on OS X to Ubuntu Linux for about 6 months before I couldn't take it any longer and switched back to a Mac. Biggest complaint by far was trackpad support in Linux. It's a mess out of the box: weird acceleration curves, bad scrolling, twitchy, overly sensitive clicking, the works. Luckily it's Linux, so it's Configurable™, and with enough tweaking I had a script that would feed a…
Completely agree. Run Linux on the desktop which mostly "just works" with a few minor tweaks required now and then. Laptops though? Forget about it. Abysmal battery life, constant issues with waking from sleep, driver issues, trackpad support and the list goes on. It truly is death by 1000 papercuts.
Every now and again I forget about the mess and try again and usually give up after a few days when I start remembering it all. I'm sure some people thrive in that kind of environment but I just need to get work done and when the OS gets in the way of that, it doesn't matter that "you just need to configure ..."
Re: Weave and Docker for Mac: The bridge between local and remote services
#38Re: Weave and Docker for Mac: The bridge between local and remote services
#39Earlier quoted context omitted.
Visual Studio, XCode, Adobe , anything by Autodesk... As good as alternatives like GIMP are, they simply can't compete with their Mac/Windows alternatives like Photoshop.
Both XCode and VisualStudio are proprietary IDEs designed to support building apps for their respective operating systems. If you're writing a Windows native application, you will find Visual Studio on Windows to work the best, likewise if you're developing a Mac OS X native application then XCode on OS X is the smart choice. In my opinion, neither one is well suited for building a native Linux application nor the so…
XCode has a fantastic interface for writing Swift, which is no longer specific to Apple hardware. It also has a decent (if not fantastic) IDE for basic C and C++ development. Visual Studio has some great plugins for not only generic C and C++ development, it also has great integrations available for JavaScript and Python (which many developers prefer to use over even JetBrains fantastic cross-platform offerings).
If you look at Go, Python, and Ruby web development, there is nothing special about the Linux environment that these programming languages do not provide built-in solutions to. Sockets, file handles, threading and process management are all abstracted to the level that you can run the same code on Windows, Mac, and Linux.
So, in _my_ opinion, it comes down to which OS you enjoy the most for your development work; you can make any of them work for whatever type of development you want to do (particularly something as high level as web development).
Re: Weave and Docker for Mac: The bridge between local and remote services
#40Must admit I thought this was the weave framework google/nest are pushing.