And… they’re basically all correct. Linux does run on all sort of machines, even really ancient ones. It has a solid command line environment, or rather lots of them. And it’s astounding powerful. Windows does still blue screen, is currently the best place for gaming, and wow is MS fucking you with Win11. Macs can have a cool setup, are really simplified for most users and expensive.
I don’t think I’ll ever be a Mac user but I’ve seen how fast these newer MacBooks edit video on battery power without breaking a sweat (and without eating through the battery).
People focus on “software magic” with Apple but the M chips are serious hardware that a lot of us don’t take seriously because the company that killed the iPod made them.
What’s interesting is the Apple CoreAudio system on iOS and macOS is as good as it is from their experience developing the iPod. For years after the iPod was discontinued, audiophiles were paying top dollar for used iPod Classics, just for the high quality DAC. The low-latency and high quality of CoreAudio is one of the reasons Pro Tools works better on Mac than on Windows.
Yeah, the people at Pixar have no clue how to use a computer. Lol
In all seriousness, even the same media software, like Pro Tools, is more versatile on Mac than on Windows. I can say that with first-hand experience.
The “dumbed-down” Apple device is the iPhone. You get admin privileges on MacOS like a big boy. You can use bash or zsh commands in Terminal all you want.
Yeah, the people at Pixar have no clue how to use a computer. Lol
Do you really expect their artists to be IT experts? You seem to be stuck in the early 90s mindset when “knowing how to use a computer” covered all disciplines.
You get admin privileges on MacOS like a big boy. You can use bash or zsh commands in Terminal all you want.
Cool. So try updating to a version of Bash from the last 15 years, because the pre-installed one is Bash 3, because Bash 4 and 5 are under the GPLv3 license, which Apple won’t comply with.
…ah, no, you can’t update the pre-installed Bash, because it’s on a section of the file system that is read-only even with admin access. You can install Bash 5 as a separate shell, and use that as your default terminal shell, but any scripts written with the standard #!/bin/bash instead of the more flexible #!/usr/bin/env bash will still use Bash 3.
This “handholding” (or really, a safety net) is arguably a good thing, or at least a positive tradeoff; but you can’t claim it doesn’t exist.
It’s not so much a problem of there being things you “can’t do” in other shells or older Bash, as that it breaks existing shell scripts, which is frustrating.
I get that this is an Apples to Oranges comparison, but Powershell 7 is way easier to use than the default Windows Powershell because of autocomplete. I imagine that newer versions of Bash have made improvements that are similarly powerful.
If it’s anything like when I used a Mac regularly 7y ago, Homebrew doesn’t install to /bin, it installs to /usr/local/bin, which only works for scripts that use env in their shell “marker” (if you don’t call it directly with the shell). You’re just putting a higher bash in the path, not truly updating the one that comes with the system.
It’s been a long time since I even did this, and I’ve gotten at least one new machine since. I got several replies so I’ll just link my original response: https://lemmy.world/comment/11431853
That’s mostly still true, with the small caveat that the default prefix on arm64 macOS is /opt/homebrew rather than /usr/local, so you might have to add it explicitly to your PATH
Oh thank goodness, that was one of my main complaints with the system. Did they ever get around to requiring sudo like Macports (and any other reasonable system level packages manager on BSD/Linux)?
Ok, yeah, I can see that there would be times this could matter but like 90% of the time this wouldn’t have mattered for my use case afaik. I didn’t realize you couldn’t backup the old copy in /bin and symlink to the brew one from there. In fact I thought I did do that long ago.
And… they’re basically all correct. Linux does run on all sort of machines, even really ancient ones. It has a solid command line environment, or rather lots of them. And it’s astounding powerful. Windows does still blue screen, is currently the best place for gaming, and wow is MS fucking you with Win11. Macs can have a cool setup, are really simplified for most users and expensive.
Macs excel in multimedia creation. It’s not just a cool setup. Yes, I’m prepared for the inevitable downvotes.
I don’t think I’ll ever be a Mac user but I’ve seen how fast these newer MacBooks edit video on battery power without breaking a sweat (and without eating through the battery).
People focus on “software magic” with Apple but the M chips are serious hardware that a lot of us don’t take seriously because the company that killed the iPod made them.
What’s interesting is the Apple CoreAudio system on iOS and macOS is as good as it is from their experience developing the iPod. For years after the iPod was discontinued, audiophiles were paying top dollar for used iPod Classics, just for the high quality DAC. The low-latency and high quality of CoreAudio is one of the reasons Pro Tools works better on Mac than on Windows.
Yeah, more software was written for the more user-friendly computers with the (generally) less-technical userbase.
Yeah, the people at Pixar have no clue how to use a computer. Lol
In all seriousness, even the same media software, like Pro Tools, is more versatile on Mac than on Windows. I can say that with first-hand experience.
The “dumbed-down” Apple device is the iPhone. You get admin privileges on MacOS like a big boy. You can use bash or zsh commands in Terminal all you want.
Do you really expect their artists to be IT experts? You seem to be stuck in the early 90s mindset when “knowing how to use a computer” covered all disciplines.
Cool. So try updating to a version of Bash from the last 15 years, because the pre-installed one is Bash 3, because Bash 4 and 5 are under the GPLv3 license, which Apple won’t comply with.
…ah, no, you can’t update the pre-installed Bash, because it’s on a section of the file system that is read-only even with admin access. You can install Bash 5 as a separate shell, and use that as your default terminal shell, but any scripts written with the standard
#!/bin/bashinstead of the more flexible#!/usr/bin/env bashwill still use Bash 3.This “handholding” (or really, a safety net) is arguably a good thing, or at least a positive tradeoff; but you can’t claim it doesn’t exist.
I agree it’s not as limitless as Linux, but there’s plenty of room for advanced users.
I’ve never needed to use a newer version of Bash. What is an example of something one couldn’t do with Bash 3 or zsh?
It’s not so much a problem of there being things you “can’t do” in other shells or older Bash, as that it breaks existing shell scripts, which is frustrating.
I get that this is an Apples to Oranges comparison, but Powershell 7 is way easier to use than the default Windows Powershell because of autocomplete. I imagine that newer versions of Bash have made improvements that are similarly powerful.
I’m not sure what you mean. I have updated bash with a single homebrew command.
If it’s anything like when I used a Mac regularly 7y ago, Homebrew doesn’t install to /bin, it installs to /usr/local/bin, which only works for scripts that use env in their shell “marker” (if you don’t call it directly with the shell). You’re just putting a higher bash in the path, not truly updating the one that comes with the system.
It’s been a long time since I even did this, and I’ve gotten at least one new machine since. I got several replies so I’ll just link my original response: https://lemmy.world/comment/11431853
Gotcha. Yeah low level Unix has some weird stuff going on sometimes.
That’s mostly still true, with the small caveat that the default prefix on arm64 macOS is /opt/homebrew rather than /usr/local, so you might have to add it explicitly to your PATH
Oh thank goodness, that was one of my main complaints with the system. Did they ever get around to requiring sudo like Macports (and any other reasonable system level packages manager on BSD/Linux)?
The poster you’re replying to was not referring to 3rd party software in user space.
Ok, yeah, I can see that there would be times this could matter but like 90% of the time this wouldn’t have mattered for my use case afaik. I didn’t realize you couldn’t backup the old copy in /bin and symlink to the brew one from there. In fact I thought I did do that long ago.
they actually use linux for render
Weren’t they the guys who made Gimp to Gimp Studio or something like that?
Did you miss the word “generally?”
Having a familiar console is nice, but you still can’t truly tinker with all the nuts and bolts.