251–260 of 450 posts
Earlier quoted context omitted.
One of the things that drew me to Macs as I started to learn programming in '05 was that I could simply open any macbook and type python/ruby/perl and write some code.
Different time. Now you got Homebrew
I think this is great, but at the same time, auto-installing homebrew ought to be an option (perhaps enabled by default) when installing the “XCode command line tools”. Better yet, offer a “developer setup” app that sets up the command line tools, homebrew, iTerm2, updated bash/zsh, and more. Apple would do best to pave the cow paths developers have already worn into macOS, especially when it comes to command line ut…
I reject the persistent meme that iTerm2 is somehow essential. Apple do a great job with the builtin Terminal.app
I think this is great, but at the same time, auto-installing homebrew ought to be an option (perhaps enabled by default) when installing the “XCode command line tools”. Better yet, offer a “developer setup” app that sets up the command line tools, homebrew, iTerm2, updated bash/zsh, and more. Apple would do best to pave the cow paths developers have already worn into macOS, especially when it comes to command line ut…
I think / hope Apple will do their own package system, maybe as part of the app store, for developer tooling like that. If only for improved security.
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.
macOS is an evolution of NeXTSTEP and has its own way of doing things, based on BSD, Mach, Objective-C and Swift APIs.
Earlier quoted context omitted.
I'd prefer if Apple took care of security fixes instead of some third party. And they could ship newer versions if keeping the old ones secure is harder.
The problem is that updating to a new version isn’t possible if it breaks existing software - what happens is that the end user experience is “I installed these updates and Apple broke my program” so don't update in future, and tell others not to as well. The only way to stop the OS from including out of date software and libraries is to not ship them if they don’t have stable abi. That’s what Apple is doing: it can’…
Earlier quoted context omitted.
It's honestly terrible for newbies. If they try to use it, there's no pip included. So then they easy_install all their libraries which installs things into different places than most python devs will be used to. Or they easy_install pip first. But even still, everything is installing to system paths, so when they try to install things it fails with permission errors. They find a stack overflow post that says just "s…
So you're saying Apple should adopt brew as default package manager and install all system tools using brew? I could get behind that, but just dropping everything without replacement makes it harder for first-time programmers.
Earlier quoted context omitted.
Of course you are technicly right. Homebrew is a train wreck and should not be used. But people are using Windows also, they don't use the proper tools, like ports. Unfortunately it is the defacto packager. But still, people should not put out Homebrew installation recipes, and prefer macports instead. At least you can seperate the newbies from the experienced immidiately. If it's a Homebrew package only, avoid.
Can you explain further why you think Homebrew should not be used?
* installs into /usr/local/bin, which is now a protected path with SIP. Why do you think Apple itself protected themselves from Homebrew? So what do Homebrew users do now? Disable SIP. Sigh
* installs with users permissions, not a seperate user. /usr/local/bin is now open for every pwner. The very first path, not just ~/bin.
Never trust a newbie package manager which takes over your whole system and installs into the very first path. Even macports can override the pre-installed coreutils without messing with /usr/local/bin.
Besides the security nightmares:
* is a unicorn, esp. for darwin only. macports uses the de-facto standard ports framework instead, just with tcl, not the shell.
apt or rpm are also not the standard. ports was much earlier and is used on much more platforms than those unicorns. You won't get any brew recipes from other and better managed packages. Those with a bit more experience.
Earlier quoted context omitted.
Different time. Now you got Homebrew
Which installs itself based on the system Ruby. Will be interesting to see how that plays out.
Earlier quoted context omitted.
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.
How much slower?