41–50 of 450 posts
Earlier quoted context omitted.
> Does anyone actually use Docker on Mac? What? We use it at work every day for local development, and my previous employer did as well. It has issues, definitely, but they have more to do with Docker than with xhyve.
But doesn’t Docker on Mac run a Linux VM? I don’t think it uses any of MacOS’s isolation features.
Earlier quoted context omitted.
Does OSX offer reasonable container technology? chroot?
macOS has a native hypervisor framework, Docker and xhyve uses it. https://developer.apple.com/documentation/hypervisor https://github.com/moby/hyperkit
Further, there's no decent solution for shipping a macOS container image to run in a VM. Linux, yes, Mac, no.
Finally, good luck getting your virtualized macOS app to interact reasonably with your main OS (no drag and drop, no OpenGL, etc.).
I would rather chroot.
So, what's the point of using Macs as a better Linux, if they are continuing to strip out the parts of Linux that are useful? Might as well use WSL or Cygwin and save a bunch of money.
There is no real loss here; no sane users would use the built-in versions due to their age. It has been preferable to download and install newer versions for a long time, this changes nothing.
And if it's fine to spend a tiny amount of effort to install WSL or Cygwin on Windows, then it's surely also no effort at all to install Homebrew or MacPorts (or other) — with the benefit of not working in a contrived, separate environment.
This comment betrays a fundamental lack of understanding of modern developer workflows in macOS and feels just slightly like a troll comment from someone who likely doesn't use macOS to begin with.
Earlier quoted context omitted.
No - the problem with the misc other interpreters is that they don’t provide sufficient binary stability for Apple to simply include the newest one in every update (which I suspect they would happily do). They’re not removing the commandline (although moving to zsh? :-/), or banning interpreters. They’re just not including them built into the os anymore. As for the AppleScript and JavaScript questions: Apple makes th…
I think you read more into my question than what I meant. I was asking literally about the best way to install it was without a system level ruby. Once you have homebrew, you can install ruby; but what about before that? Download and install ruby from ruby-lang.org, install homebrew and a brewed ruby, then uninstall the one from ruby-lang.org?
Earlier quoted context omitted.
macOS has a native hypervisor framework, Docker and xhyve uses it. https://developer.apple.com/documentation/hypervisor https://github.com/moby/hyperkit
A hypervisor is not exactly a container. Definitely not in the Linux sense. It may be more secure, but it is also slower. Further, there's no decent solution for shipping a macOS container image to run in a VM. Linux, yes, Mac, no. Finally, good luck getting your virtualized macOS app to interact reasonably with your main OS (no drag and drop, no OpenGL, etc.). I would rather chroot.
Earlier quoted context omitted.
https://brew.sh
Right... /usr/bin/ruby -e ...
But let's be real, they're either going to make a .pkg, or just use a shell script or .. really, there's dozens of ways. They've been using an alternative version of ruby packaged in the homebrew folder for a while now. The only part of the process that requires System Ruby is the installer, now.
Congratulations, Python 3!
This has been a topic brought up internally at Apple many times over the past decade. Glad to see it finally moving forward. Although I see the benefits to having a system-version of these packages.. if you're doing anything serious for production then the environment should be containerized.