Sarcasm obviously. As an Apple enthusiast it’s so annoying how they sniff farts.
Sarcasm obviously. As an Apple enthusiast it’s so annoying how they sniff farts.
What is this for? Games? I avoided this to save money the last time I bought a phone. I honestly can't think of use case where a phone display needs to update higher than 60 Hz
Instead VFR allows saving battery by slowing down the refresh rates, down to as low as 1FPS for static or high latency content. That's part of why always on display is only available on the 15 Pro: at 60Hz it's a battery killer.
> Sort of like going from a slowly accelerating station wagon to a Porsche/sports car even when (capped by the speed limit) if you've experienced that.
So... functionally useless.
(Disclaimer, I haven't driven a sports car but I have driven cars between "nice" and "struggles to reach the speed limit")
While it might appear to be very similar, having a sports car that you're capable of driving well/defensively can literally be a life saver. There was this video from a few years back on reddit of this guy in a 911. Vehicle in front suddenly stops/crashes, he needs to rapidly change lanes at highway speeds. The little 911 unsurprisingly handled it excellently. A slow/heavy car would've very likely spun out and crashed.
Having more power if you don't need it doesn't hurt (if you're trained well). Less can hurt.
Or it can be a life ender by planting you into the side of the road, something mustangs and BMWs are well known for, amongst others.
> that you're capable of driving well/defensively
If you need to be a skilled pilot to face the situation, it's less the car and more the pilot which does the life saving. And even skilled pilots who know their cars well can fuck it up. Rowan Atkinson famously spun his F1 into a tree, after 14 years of ownership, having been racing for 2 if not 3 decades.
> There was this video from a few years back on reddit of this guy in a 911. Vehicle in front suddenly stops/crashes, he needs to rapidly change lanes at highway speeds.
Something which ends up in a collision as often as not.
> The little 911 unsurprisingly handled it excellently. A slow/heavy car would've very likely spun out and crashed.
Or not. Or maybe with a less capable machine they'd have driven more prudently and would have kept more space.
> Having more power if you don't need it doesn't hurt (if you're trained well).
So having more power can literally hurt. And routinely does.
The bigger difference I notice is in loading times for apps.
Anecdotally, I use the last gen pre-120hz iPad Pro as my daily driver and I notice the difference immediately when I switch from my phone to the iPad. It’s not annoying enough to force me to upgrade immediately, but it’ll absolutely be a requirement for me going forward.
Variable refresh rates should be standard across the board however, not restricted to high refresh panels. There’s no more reason for a static screen to be redrawing at 60hz than there is for it to be redrawing at 120hz or 240hz.
This analogy is also flawed, of course.
Depends on the device, but often the difference is a very minimal few point percent, perhaps 3-5%. I would think it can easily be compensated for by undervolting/powerlimiting on laptops.
The win is lesser eye strain/headaches for a lot of people. No harm in turning it off if you don't need it, but many do benefit.
not necessarily. on promotion iPhones (fancy name for variable refresh rates), the panel is not stuck at 120Hz all the time. it varies from 1Hz when the screen is static up to 120Hz when it's getting animated, down to whatever framerate your content is at (e.g. movies and videos). it actually is a battery saver whenever the phone's screen is static (common on most apps with text) or with <60Hz content (youtube, movies, etc).
This is obviously not a critical feature, mind you, but it does add to the experience of using a device, even if it's just productivity-related tasks.
UI is very buggy and inconsistent.
CLI tools/shell is attempting to follow more-or-less standardish unix/linux setup but fails pretty hard, with many of the same commands existing but behaving just differently enough to be annoying.
Uses it's own set of shortcuts, different from what's standard on windows/linux and most other operating systems.
Not sure what people mean when they say completely vague and ambiguous things like 'usability' and 'comfort' - are you referring to the fact that it has rounded buttons and corners and pretty ads?
It basically falls in between a standard windows and highly modified ubuntu setup, but does far worse at both. The UI, apps, etc is far more buggy and unintuitive than windows, and the os is far less 'unix' and far less customizable than ubuntu.
I'm pretty sure this is simply you expecting GNU and actually getting FreeBSD-based tooling. It's not wrong, it's just different than what you expected.
But if you want to contend that anything that is solveable via customization/3rd party packages is a 'total non-issue', then I fail to see how you could argue that Linux isn't superior to MacOS in every single way.
Or you mean, you work at FAANG and you can run your web application which is 0.01% of the stack on your mac?
> they do not even focus on desktop software and are mostly web companies and the tooling is all backend where SWE machines do not do any heavy lifting.
The web frontend/ui is a relatively small portion of the development that goes on at typical FAANG. And the reason the macs 'do not do any heavy lifting' is because they literally can't - most of the complex backend systems, low low level/high performance code, etc can't be run on macos.
Of course it will if it's a linux laptop. Companies even give exceptions for linux laptops for exactly this reason.
> This is a stupid position to take, because people care more about whether they can spin up a development environment, not run all the code that goes to production.
You think being able to run the code you're working on is not a requirement for a good development environment? Or you think nobody writes this code, it just magically appears in production when you deploy your html page? Lmao.
> Many software companies (including FAANGs) have basically given up trying to support building/running most of their software on mac for these exact reasons
Why would Amazon or Google waste a single minute trying to get software to build on Macs that are targeted to run on Linux servers?
Exactly what point are you attempting to make?
Running the entire AWS stack on macos is literally impossible at this point because major pieces aren't even built for macos (and can't be without major rewrites).
Amazon “suppprting” Macs mean outside developer support like AWS CLI, CDK, SAM, Amazon Chime, etc.
Of course we all spun up Isengard accounts when we needed a lot of CPU horsepower or to run some dependencies instead of running something locally. Why wouldn’t you? You worked at the only company that never had to worry about a large AWS bill.
Also all of the internally written MDM tools also supported Macs.
You literally just claimed everyone at Amazon uses macs for development and runs their code on their macs. This is not the case for the vast majority of code written at Amazon.
> Amazon “suppprting” Macs mean outside developer support like AWS CLI, CDK, SAM, Amazon Chime, etc.
Nobody said anything about 'amazon "supporting" macs' and what that means except you, just now, when you moved the goalpost.
> Of course we all spun up Isengard accounts when we needed a lot of CPU horsepower or to run some dependencies instead of running something locally.
What? Using remote development environments/ec2 boxes is literally the default at AWS and it has nothing to do with 'CPU horsepower'. Most of the ec2 instances used for development are far less powerful than a macbook pro.
When a developer puts a laptop in their Amazon issued backpack, what type of laptop do most of them use?
I’ll never install homebrew as long as the dev continues this amateur hour bullshit.
Otherwise, you have no way to control versioning anyway. When the OS version is tied to the version of so many other tools, it's a nightmare. Apple is trying to push you in the right direction by basically not updating the CLI tools ever, even when upstream didn't change the license to something unacceptable for them to distribute as in the case of bash.
Why? Why do I need to use 3rd party package managers, or manual installations from 3rd party sources to install common tools that aren't a decade+ outdated?
> When the OS version is tied to the version of so many other tools, it's a nightmare.
It doesn't need to be tied to anything. If the OS needs specific libraries/tools then they can be installed in a separate location. If there are new major versions of user-level tools (like bash) those should come by default, not some 15 year old version of the same tool, with the same license. Multiple linux distros have solved these problems in different ways 10+ years ago.
> Apple is trying to push you in the right direction by basically not updating the CLI tools ever
No, they are just neglecting the CLI ecosystem, the package management, and the many many outstanding bugs that have existed and been ignored for years.
GPL2 was viral, but the terms were easier to stomach. Apple is allergic to GPLv3 code because there is a clause in the license requiring you provide a way to run modified version of the software which would require Apple to let users self sign executables.
This is a simple result of the GPL going where Apple will not, so OSX is stuck with whatever is MIT, BSD, Apache, or GPL2 licensed.
I like the GPL, I license my open source stuff under it, but it doesn’t work for all cases. Apple is fine with not using software licensed under the GPL, when it conflicts with other company principles.
Simple as.
Wow, I don't know this before. Good job FSF! This, should, be, a, basic, right.
I don't believe the license allows them to charge an extra fee for this, and for good reason. It deters hobbyists from doing it.
> You can’t alter them sign a system binary.
What's a "system binary"? The bash executable runs entirely in user mode.
Does that really add up though? You can install and run 3rd party software on macos without any signing needed.
Apple can be fine with whatever they want and choose whatever principles they want. Doesn't mean it leads to good software or that I need to like it.
- Apple is shipping stuff out to customers.
- Whatever is shipped has to satisfy corporate policy.
- The GPLv3 does not do so.
That’s what matters. The only way what you care about has any impact on the above is if there is a meaningful impact for Apple for following the policy, and Apple suffering some sort of loss (be it monetary, PR, legal etc).
Thus far, the non-presence of GPLv3 software does not appear to have hit that bar.
Because you want to control the version of 3rd party software.
> It doesn't need to be tied to anything. If the OS needs specific libraries/tools then they can be installed in a separate location
The OS installs tools in /usr/bin and you should install tools in a separate location. Apple provides a commercial UNIX, not a Linux distribution. /usr/local or /opt are traditional locations for you to place the 3rd party software you want to use on your commercial UNIX.
If you want the OS to ship with updated tools, of course it's tied to the OS version. Then if you want bash 70, you'll need to run macOs Fresno or later, or install bash 70 in /usr/local. You should just install your version anyway, and then you won't have to worry about OS versions (unless bash 70 requires kernel apis unavailable before macOs Fresno, in which case you're stuck; but most software isn't intimately tied to kernel versions)
Not that they were going to update bash regularly anyway. So if you needed a new version in the base, you'd need a new version of the OS. And then you're back to the same problem you have now. Apple doesn't distribute the version of the 3rd party tool you want for the OS you're on.
Right, so scripts written for bash4+ don't work - which is most of modern bash scripts..
> but why would you write a bash4 script for macOs?
The problem is that you have to write special scripts (among other things) just for macos. This is very real problem because most modern software companies run their stuff on linux, while the dev laptops/workstations are often macos.
It would be better to have a dev vm or use an os that you can run a real server on. FreeBSD, Linux, Windows, maybe Solaris.
Scoop, Chocolatey on Windows. Brew on MacOS. Amethyst on Arch.
Linux package managers eviscerate whatever is available on MacOS and Windows by a long shot.
Frankly if there’s one thing I want my OSes (excluding Linux) to keep their greasy paws off of, it would be my CLI and build environments.
I want to install and manage what I need, not be force fed whatever sludge comes out of Microsoft’s or Apple’s tainted teats. Manage and update the OS, don’t touch anything else.
> I want to install and manage what I need
Good luck installing what you need if someone hasn't made a port explicitly for macos.
I hate it.
https://en.wikipedia.org/wiki/Server_Message_Block#Netsmb:
“NSMB (Netsmb and SMBFS) is a family of in-kernel SMB client implementations in BSD operating systems. It was first contributed to FreeBSD 4.4 by Boris Popov, and is now found in a wide range of other BSD systems including NetBSD and macOS“
https://appleinsider.com/articles/11/03/23/inside_mac_os_x_1...:
“The upcoming release of Mac OS X 10.7 Lion Server will remove the formerly bundled open source Samba software and replace it with Apple's own tools for Windows file sharing and network directory services”
I also think they complete removed AFP support.
There actually is a reason. It's not lack of maintenance.
It's because Bash 3.2 is the last version licensed as GPLv2. Bash 4.0 and later changed license to GPLv3.
Apple decided it's not safe for them to ship any software with GPLv3 with macOS, because of stronger legal conditions in GPLv3. This is also the reason they stopped updating Samba.
They changed the default shell to Zsh long ago. The old Bash is kept around, so that users who want to stick with Bash can still use it as their shell, and so that existing scripts for macOS (for example in installers) continue to work. If nobody cared about Bash, I expect they would have dropped it from macOS when switching to Zsh, rather than keeping the old version.
So from a certain point of view, Bash 3.2 is the most recent version they can ship.
As for other tools like "cp", "ls", "rm", "touch", etc. I agree they are annoying on macOS, when you are used to the versatile GNU/Linux command line options. I sometimes type options after filename arguments due to habit on Linux. macOS commands very annoyingly treats those options as filenames instead. And I miss options like "touch --date".
However, this is not due to old tools. Those differences are just how up current (up to date) BSD commands work. They are just a different unix lineage than Linux.
The GNU tools were intentionally written to be more user-friendly than traditional UNIX™ tools, which is why the command line options are generally nicer. GNU/Linux systems come with GNU tools of course. macOS never did because it is derived from BSD and comes with BSD tools (with Apple enhancements, like "cp -c").
You get the same on most other unix environments that are not GNU/Linux. People install the GNU tools on top, if they want the GNU command line experience instead of the default. Sometimes with the "g" prefix (like "gls", "gtouch" etc.).
These days, even if Apple decided it's worth the technical fallout of switching from BSD command line tools to GNU, they wouldn't do it for the same legal reason as what keeps Bash at 3.2: The current GNU tools are licensed as GPLv3.
Apple could choose to be GPLv3 compliant tomorrow, if they wanted to.
What up-to-date BSD are you referring to? The commands on different forks of BSD like FreeBSD vs OpenBSD are not the same. And quickly looking at the man pages of latest FreeBSD vs MacOS versions of ls, for example - they are not the same.
> These days, even if Apple decided it's worth the technical fallout of switching from BSD command line tools to GNU, they wouldn't do it for the same legal reason as what keeps Bash at 3.2: The current GNU tools are licensed as GPLv3.
What actually prevents them from including GPLv3 software?
macOS is UNIX certified and POSIX compliant. You're probably expecting GNU commands, but macOS is based off of FreeBSD (and is not related Linux).
CLI tools/shell is attempting to follow more-or-less standardish
unix/linux setup but fails pretty hard, with many of the same commands existing but behaving
just differently enough to be annoying.
They wasn't following unix/Linux standards they are following unix/bsd standards. Standards that predate Linux and for some of us are very familiar indeed.Everyone knows that macos (and windows) took a lot from unix/bsd. But that does not mean they are actively following any kind of reasonable modern standard. And saying they might be following some 30 year old supposed bsd standard is pretty hilarious for an OS that portends to be cutting-edge, intuitive and well-integrated.
Just a couple concrete examples, if you open an app in a workspace, then switch screens to a different workspace, then click the app in the dock, nothing happens. I would expect to be taken to the screen and have the app made visible, but instead, nothing. I kept thinking that the app must be frozen or something until I switched screens and found it.
Another example, I was carrying my laptop to and from work. I put it in my backpack with padding that protects the laptop. I didn’t jostle it around, I literally just carried it to and from work. I get home and the screen is in some sort of weird flickering bugged out state. I had to forcefully restart it just to get it working again.
With all that said, the trackpads and gestures on Macs are amazing. The displays are also very visually appealing. The performance is good.
I find that more often than not I can't make it through the Windows setup without worse janky stuff happening. Pretty often when toggling off all the bullshit privacy settings that shouldn't be opt-out to begin with, I'll get a visual indication of the switch starting to move after my click, then turning around and going back to the default—so my click was definitely received, but rejected somehow. That seems worse to me than a correct response delayed.
> if you open an app in a workspace, then switch screens to a different workspace, then click the app in the dock, nothing happens. I would expect to be taken to the screen and have the app made visible, but instead, nothing.
There is a visual indication in that the contents of the menu bar change to reflect the newly active app; unlike on Windows a Mac app can be active without having an active or foreground window. There's a system setting to control whether to switch spaces in this scenario, but I don't recall whether the behavior you describe is the default or something you accidentally configured to annoy you.
My Mac and Linux shortcuts align more than my Windows and Linux/Mac ones. For the most used ones it’s CMD + whatever the standard key is for that shortcut, instead of Control. Overal I prefer that the Super key is more useful than what has been the default for many years with Windows.
I also use the CLI for virtually everything on Mac and Linux, MacOS isn’t all that different and feels more like another Linux flavour than it’s own beast.
The only UI gripes I can think off immediately is no window snapping and closing the window doesn’t mean you’ve exited the application. The first requires a third-party tool (I recommend Rectangle), the latter is a change in behaviour.
Frankly I’m not really all that interested in defending MacOS, but I hope you realise that saying “very buggy and inconsistent” without naming anything specific isn’t any less vague and ambiguous than “usability and comfort”.
Your reaction comes off as “I’m used to this, therefore the other thing is bad and unintuitive.” I’m sure this isn’t your intention, so specifics would be illuminating.
I posted a list of recent issues I've run into elsewhere in the thread, but there are many bugs and inconsistencies in macos:
- Doc breaking/becoming inaccessible.
- Running app windows disappearing/becoming inaccessible.
- Cursor/caret disappearing when editing text.
- Can't move windows between workspaces.
- Constant issues with external monitors.
- Switching between windows via command-tab regularly breaks.
These are all well-known issues that have existed for years. If you google them you will find threads and workaround from 5+ years ago.> My Mac and Linux shortcuts align more than my Windows and Linux/Mac ones
Because.. you changed your linux shortcuts to match macos? The most obvious example is that ctrl+c/s/v etc are instead command+c/s/v on macos.
> I hope you realise that saying “very buggy and inconsistent” without naming anything specific isn’t any less vague and ambiguous than “usability and comfort”.
There are literally dozens of examples of issues listed in this thread. I hope you realize that saying 'give me examples' when there are many many examples all around the post your replying too is a bit disingenuous. I can't keep repeat ing what I've already posted in the thread in every single comment.
I am not pretending MacOS is bug free, again I was just asking for your issues with the OS. But from what I've seen in your replies it seems you post-hoc justified your opinion by googling for known issues.
Unless you're claiming you have all of these issues, constantly and consistently?
Even a Mac does well with the occasional reboot, I have never had a system that was completely issue free. Be it Windows, Mac or Linux.
>> My Mac and Linux shortcuts align more than my Windows and Linux/Mac ones
>Because.. you changed your linux shortcuts to match macos? The most obvious example is that ctrl+c/s/v etc are instead command+c/s/v on macos.
I literally said in my post that the most common ones have CMD instead of CTRL, this is more than "a bit disingenuous".
The reason I prefer the Super + key, is so it doesn't mess with using CTRL+key in the terminal. As that behaviour is running contrary to expectations set by every other OS. CTRL+C doesn't mean copy in the terminal, it means terminate the currently running program. CTRL+A doesn't mean "select all" it means, jump to the start of the line.
Programs shouldn't be overwriting OS level shortcuts, though I completely understand how it came to be. It is really counter-intuitive for new users. Super + key makes more sense for OS level shortcuts, as it's literally the Windows symbol on most keyboards.
>> I hope you realise that saying “very buggy and inconsistent” without naming anything specific isn’t any less vague and ambiguous than “usability and comfort”.
>There are literally dozens of examples of issues listed in this thread. I hope you realize that saying 'give me examples' when there are many many examples all around the post your replying too is a bit disingenuous. I can't keep repeat ing what I've already posted in the thread in every single comment.
I don't know how you read, but I read from comment to comment, top to bottom. I'm in the top thread where you made the claims without any examples, I don't know why you expect me to look elsewhere for the examples that you might have posted or not. Nor why you think I would look for other people's issues.
If you think that's disingenuous that's your prerogative, I think that's how most people read these thread's including you. You don't need to keep repeating the same thing, you can literally just link your comment with the specifics.
Really? I 'post-justified' my opinion by posting the same set of issues in another comment hours before you replied to me? Why are you even trying to psycho-analyze my comments and come up with your own imagined motivations for them?
> Unless you're claiming you have all of these issues, constantly and consistently?
I've experienced every single issue I've mentioned. Now you're trying to quantify how 'constantly and consistently' issues appear? You're already going in circles - either they are so constant and consistent that I 'post-justified' my entire criticism based on the popularity of these issues, or they are so rare and inconsistent that they should be ignored?
> I have never had a system that was completely issue free. Be it Windows, Mac or Linux.
What is this statement supposed to represent other than blanket blessing of macos bugs? If windows has a bug - macos bugs are okay?
> as it's literally the Windows symbol on most keyboards.
That's not really a good reason.
> I don't know how you read, but I read from comment to comment, top to bottom. I'm in the top thread where you made the claims without any examples, I don't know why you expect me to look elsewhere for the examples that you might have posted or not. Nor why you think I would look for other people's issues.
I don't care how you read and I don't expect anything from you. If you're in a thread where many macos issues are mentioned, you can attempt to read the other comments in the thread, read the other replies to the same comment you're about to reply to, look at my other recent comments, etc. Instead of pretending that macos issues don't exist, then claiming that my criticism is 'post-justified' after I give you examples, and finally waving the issues off because 'linux and windows also have bugs'.
Mac OS predates both.
Also, this is personal preference, but I find engaging Command with my thumb far more comfortable than Control with my pinky.
8gb wasn't even enough in 2015!
Apple competes and demolishes anything from PC in battery and build quality. Certainly not in usability and subjectively comfort.
Also, low tier PCs support multiple monitors. Try getting that on the macbook Air.
QED seemingly works out well for Apple though.. :P
I’m still hoping for some ex Apple folks to create some new version of NeXT computers. I would switch immediately to someone’s alternative offering trying to actually play at Apple’s level of quality.
This is a bad reason to upgrade. If you were supposed to know about it, it'd be in the specs.
It's not there to improve performance or be more forward compatible, it's because the camera upgrades need it.
In defense of the poorly made apps, it just is a reflection of the general market. Mid-range Android phone have double the amount of RAM of entry level iPhone at half the price. The pressure to optimize is not very strong and I can't blame them. It's not worth spending hours of expensive engineering time on optimisation. It would still have limitations and at some point when you need more RAM to fit more data, you just need more RAM, you cannot "optimise" the problem away. All of this would be solved by more/bigger RAM chips that cost a dollar at worst. If Apple wasn't so greedy it would be a non-issue. So I think those developer have the right mindset, fuck Apple and if you are an Apple user either you spend more for the real deal or go look somewhere else for a more sensibly priced device.
Sorry ranting, not aimed at your comment at all just as I came back to this context: So I'm definitely a long standing and good customer (often and over many years an "evangelist" for free FWIW). IMO they have been milking us on the memory side of things for a while now though.
Even if I can gladly afford maxed out options I now increasingly do so because I feel "coerced" not because I just want the best. It's not great and gives a sour feeling for no good reason, I used to just love what they have on offer for the money spent. At this point they should just eat into their own margins and bump up to 50% more RAM across the board for most of the devices they are selling. That will not only make entry point customers more happy but also the ones buying their highest margin products. Why does the iPhone 15PM only have 8GB of RAM? I know that in no time my apps as a normal (?) multi tasker will get OOM killed again. The top of the line model just doesn't buy me much longevity in that department. The "toy" that is the Nintendo Switch had 4GB of RAM and came out the same year as my "premium" iPhone X at 3GB. Same kind of memory also IIRC. The next "toy" Switch 2 will apparently have 12GB when it arrives next year, I'm somewhat positive that Apple is already planning for their next PRO to have 10GB RAM max, maybe it will even stay at 8GB... the memory situation has really been ridiculous with them for a while.
Rant over, enjoy the sun :D probably / hopefully wrote this into /dev/null haha.
But yeah 16gb is so cheap Apple stop it
(Much like how the iPhone Pro has faster USB-C data transfer speeds vs base iPhone)
or
Give me an "air" with two external monitors and 64GB ram.
The pros are clunky and heavy. I'm on an air, and will stay there for a long time because if this
It uses the 6950 DisplayLink chip, which can do 4K@60Hz.
It's 90 dollars and drives 2 screens.
Software is less good. I had to enable Rosetta2 to get the pkg to install. Then you have to boot to recovery mode to allow signed 3rd party drivers. And you get a creepy notice that someone is watching your screen, which is how the display driver works.
Performance is pretty good, just a bit laggy on mouse movement.
Unfortunately I don't think the M1 Air supports TB daisy chaining unless you're ok with mirrored displays. I still can't decide if I want to ask my job for a new computer, a new dock, or new displays lol.
The way I have it set up: the i-tec dock is connected to a regular USB-C hub (from Ugreen). The USB-C hub is also connected to a 4k monitor. This way I connect 1 cable to my Mac and get everything: power delivery, Ethernet, peripherals, 4k monitor running natively and 2 2K monitors running on displaylink. It is… perfect. I havent touched my desktop computer for about a year.
Basically it is better to use the Displaylink monitors for static content - running 4K video on a 4K monitor on Displaylink would probably take about 40% CPU on my M1 chip. So everything dynamic goes onto my native 4k monitor, whereas the Displaylink monitors have easier content - browsers, vscode, notes etc.
But like, I regularly also play video on my 2K displaylink monitors and honestly I never ran into issues, or noticed a difference. Just dont do this on 4k monitors I guess.
Sorry for the delay, still havent figured out a way to get notified about replies on HN.
Since I also don't get notified of replies I've been checking back on this comment in hopes that someone had a clever solution like yours. Thanks!
At least, not the last time I tried.
It supports a 6K screen in addition to the built-in screen. It's reasonable to say that if you need 3 screens to get your job done, then that is not representative of the market for apple's lowest-end laptop.
RAM and fan has nothing to do with it, the cheapest low-end Windows laptops can do this with ease, it doesn't stress the RAM, CPU or GPU at all.
- M-series uses unified memory, the ram does in fact matter.
- Heat also matters, because throttling. The Air uses a fanless, heatsink system.
- Whatever cheapest low-end PC you’re imagining is not fanless and not running an external 6k monitor at 60Hz.
- None of those systems are optimised to maintain performance while possessing an 18 hour battery life. None of those even have an 18 hour battery life.
The Air serves a clear market segment. It’s their entry level laptop, the problem isn’t the laptop.
This is arbitrary market segmentation. I need two external monitors mostly because I share the same single cable to my dock with work and because macOS is so stupid about monitors it randomly connects to one or the other, not both. So I have to manually power off the wrong monitor each time and turn it on for work. Really annoying.
Btw a quick check on Elitebooks start at $1,760 and support at most a single 5k screen.
It may also be they have chips that have bad display controllers and they are using this as one way of offloading those chips with the bad controllers lasered off.
- Monitor randomly resets/readjusts for no apparent reason. Like multiple times every hour.
- Windows disappear, become inaccessible after moving between monitors, even though it still open and active according to doc/task list.
- Why can't I move a window to a monitor/workspace that has a maximized window? Like, you can do it by un-maximizing the window in question, moving the other window over and then re-maximizing the window again. But why is this nonsense needed? What problem could this restriction possibly be solving?
- Lots of other monitor/workspace related problems (quick google will show dozens related problems without any obvious solutions or explanations for the completely nonsensical behaviour).
I really don't understand how people can say macos has good and consist overall UI? I mean, yeah - it's consistently buggy and un-intuitive:
- Doc constantly breaks/becomes inaccessible. This is a known problem for at least 5+ years - the solution is to manually kill and restart the process???
- Text cursor/caret randomly disappears when editing text, so you can't see where the cursor is, and you can't fix this unless you restart the app (happens to pretty much all apps).
- Was working with unicode characters recently, now whenever I press command+s to save something, it gives me a visual unicode character selector popup, with no apparent way to stop/cancel this behaviour from the popup itself.
- Bad defaults in terms of keypress repeat times and rate. No apparent way to change this from settings - need to run commands and re-login to test new behaviour.
Just an overall crap OS and UI imo.
> Why can't I move a window to a monitor/workspace that has a maximized window?
Because it’s fullscreened, not maximized. macOS doesn’t really have window maximization in the traditional sense out of the box, you need a utility like Magnet or Moom for that.
That fullscreen mode was introduced in 10.7 Lion and a lot of long time mac users have found it silly from day one. Personally I never use it.
> Text cursor/caret randomly disappears when editing text, so you can't see where the cursor is, and you can't fix this unless you restart the app (happens to pretty much all apps).
I’ve seen this, but only in Chromium browsers and Electron apps. Seems like it might be a Blink bug.
Regarding other OSes, multimonitor on Linux is mostly fine (so long as you’re using Wayland; X11 is another matter especially if you’re doing something slightly uncommon like using two GPUs, in which case xorg.conf mucking will likely be necessary).
By far the most frustration I’ve had with multimonitor is in Windows, which is generally weak there. IIRC it only recently gained the ability to set per-display wallpaper; before you had to glue wallpapers together into a single image that spanned across them, which is silly.
Agreed, however it's arguably for a different mental model. If people think of it as "focus mode" or "workspace mode" it makes more sense. Four finger swipe to slide between the workspaces or focuses.
More importantly, you don't need MOOM.
- - -
To maximize a window to the dimension of the screen without entering full screen mode, either:
1) hold shift option ⌥ and click the green maximize button on the top left of the window
- or -
2) hold the Option key and double click a corner of a window to maximize without full screen focus, and doing that again will size it back to where it was
This is a handy trick to know, but has caveats. Option-green-functionality is actually defined by apps, not the OS, and so in some cases it will for example act as a “fit window to content” button.
Option-double-clicking a corner appears to be consistent across windows however.
I use it to compartmentalize stuff I'm working on, and 4 finger swipe between them.
I have a couple instances of VSCode, some app/debugging browser windows, some chrome profile windows etc... all running full screen and I spend my day brush swiping between them.
It may be different for me because I work on a 14" macbook pro, mostly at coffee shops or unusual work locations, so I don't have a large monitor setup. I don't think I'd use it much if I had more of a traditional desk/multimonitor config.
Generally I’m working at my desk with at least 2x 27” displays. If I’m out somewhere it’s instead 16” MBP + 12.9” iPad with Sidecar.
I use workspaces on my linux laptops all the time - this 'feature' has existed for ~20 years, and is not hard to implement. The difference being that macos seems to force the restriction of having only 1 window per workspace and not being able to drag a window from one workspace to another. If that's the behaviour you want (one window per workspace), you can easily operate in this way without having the forced restriction.
I don't really buy this explanation. I'm talking about using a single external monitor here, a monitor which I regularly also use with linux (intel/amd) laptops without a single issue.
> Because it’s fullscreened, not maximized. macOS doesn’t really have window maximization in the traditional sense out of the box, you need a utility like Magnet or Moom for that.
That's not really a good reason though. It still doesn't explain why the restriction exists. Why can't a non-maximized/fullscreen window be displayed on top of a fullscreen/maximized window? What problem does that solve?
> That fullscreen mode was introduced in 10.7 Lion and a lot of long time mac users have found it silly from day one. Personally I never use it.
It's default though.
Might be model-specific then. It’s not something I’ve seen with displays from Asus, Alienware, and Apple. I briefly owned a Dell monitor that would periodically flicker but it got returned.
> That's not really a good reason though. It still doesn't explain why the restriction exists. Why can't a non-maximized/fullscreen window be displayed on top of a fullscreen/maximized window? What problem does that solve?
Probably because it’d be easy for windows to get “lost” if the fullscreen window were focused and non-fullscreened windows fell behind it, with there being no obvious indicator that those windows exist.
I would not buy any new monitor for MacOS that does not explicitely advertize MacOS support.
I was pleasantly surprised when I plugged the AW2721D that’s part of my gaming setup into my daily driver Mac. Everything worked great, including 240hz and variable refresh.
Obviously you have some kind of problem with your system.
- Windows disappear, become inaccessible after moving between monitors, even though it still open and active according to doc/task list.
This indeed happens relatively often if you have multiple monitors and switch between them for any reason. e.g. in my case I have two machines and two monitors, sometimes I switch the primary monitor to a specific machine and this almost always fucks up macOS. Solution is to disconnect and reconnect the monitor.
- Why can't I move a window to a monitor/workspace that has a maximized window? Like, you can do it by un-maximizing the window in question, moving the other window over and then re-maximizing the window again. But why is this nonsense needed? What problem could this restriction possibly be solving?
A lot of people who use macOS agree that the fullscreen window thing is needless and makes for quirky behaviour.
- Dock constantly breaks/becomes inaccessible. This is a known problem for at least 5+ years - the solution is to manually kill and restart the process???
- Text cursor/caret randomly disappears when editing text, so you can't see where the cursor is, and you can't fix this unless you restart the app (happens to pretty much all apps).
Yep, happens quite frequently to multiple people I know and in multiple apps.
- Bad defaults in terms of keypress repeat times and rate. No apparent way to change this from settings - need to run commands and re-login to test new behaviour.
Indeed this is very painful for people who are non-developers and are used to be able to have higher repeat rates.
I've seen all of those things listed.
It would be one thing if OSX/Linux/Windows UIs would just stay at their basic usability from around 2010. They haven't. They just get steadily worse.
OSX has been the most stable of them, quirks and all, even with a goddamn architecture change, but its closed hardware, a forced upgrade cycle, and bad backwards compatibility.
Linux once would just rewrite window managers every 5 years as soon as they got stable, now Linux is rewriting with Wayland and Vulkan, and ... about 5 years in they'll probably start rewriting those once they get a little stable.
Windows? Committed UI suicide with the tiles and two desktops thing in Windows 8. Now there's ARM in the future and a break with the only thing it has going for it: backwards compatibility.
But yes, everything the author complains about happens in OSX with laptop + monitor / dual monitors, and even without with disappearing mouse cursors.
(And I for one hasn't bought a Macbook since 2020 because I am not going to spend at least $1,999 just to get dual monitor support. A $500 asus laptop can do dual monitor without any problem, and it turns out that machine is good enough for my productivity needs. That money is better spent elsewhere)
They make a small MacBook Pro that is suited for that task.
It is Apple’s best selling computer by quite a bit. They sell metric assloads of the $999 base model each fall when school starts.
IMO the $999 one (or $899 with education discount) is literally the best price:perf ratio of any computer available today or at any time in my recent memory. It’s astounding how good it is for that price.
> IMO the $999 one (or $899 with education discount) is literally the best price:perf ratio of any computer available today or at any time in my recent memory. It’s astounding how good it is for that price.
It is possible for your comment to be correct while the poster above is also correct. The M chips are amazing, but let's not pretend that Apple doesn't knowingly gimp the hardware to upsell the more expensive versions.
"But that would make it more expensive."
Yes it would... by pennies. It is a bit ridiculous to sell a phone as expensive as the current iphones and limit them to USB 2.
If you are thinking in any way whatsoever about the non-wireless data transfer speeds on your phone, you are not the market or user it was designed for. Same goes for external monitors on an MBA.
I'm skeptical. A ton of money is dumped into optimizing everything and then they just throw it down the drain? That would drive more people to the competition than to higher-priced Macs.
- the 14" M3 is $1600, but limited to a single external display, and actually only has two TB ports, it's just sad
- the M3 Pro is limited to two external displays, despite an entry price of $2000
$3199 is the baseline to be able to use 3 external displays (although at that price you can plug up to 4).
They're selling a $1600 machine which can't drive two external displays, it's sad. Intel's HD Graphics have been doing better since 2012 and they're trash.
And that's why everyone loves node shrinks. You can stuff more transistors for the same cost.
That doesn't make it less frustrating.
> If they thought it would sell more Macs, they would do it.
It's short term thinking, it generates bad feeling of nickel and diming and unnecessary upsells: on M3 you need to pay $2000 to be able to use two external displays, and $3200 for 3, even if you have no need for the rest of the processing power.
Not only that but they managed to create more range confusion with the expensive but gimped entry-level 14".
Or more than 1 external display. The vast majority own none or a single. Few people have multiples, and those people are generally enthusiasts who will also tend to pay more.
I'd love to see some modern stats that take into account these nuances.
Apple sure could design a chip that drives more monitors, but maybe they decided that making the chip x% more performance/efficient, or having y feature was more important.
Or, maybe this really truly is trivial and they decided to segment their chips by not including this feature. There is absolutely nothing wrong with that.
My job provided me with a Dell laptop with an i7 and it can keep my coffee warm just idling. Sometimes, when it’s decided it doesn’t want to sleep, I can hear the fans from the next room. While the screen is off, not being touched.
I could go on at length about just how shitty the Dell is compared to my MacBook Air (despite costing more and performing worse!), but Apple Silicon Macs are just so much nicer when it comes to the practicalities of using a portal computer.
It's almost like we should focus on what Apple does best and ignore what Apple does worse.
I have.
Engineering tradeoffs indeed.
For all its flaws, Apple focuses on making sure there is a good experience overall. In general, they'd rather have a more limited hardware ecosystem that works better than a broad ecosystem that's flaky.
There are tradeoffs to both approaches. I go back and forth between windows and mac, and have for decades.
I was a surfacebook/win10/WSL guy for a few years, and liked it a lot. Win 11? Not so much.
Currently the M series chips blows any PC laptop away for the combination of portability/performance/battery.
The Snapdragon X might change that in the next couple years, and I'll take a look at switching back then, and see what win 12 offers. If MS decides to take a step back from being an ad-serving platform and goes back to focusing on productivity, I may switch back.
For now though, I'm planning on accepting the gut punch to my wallet and picking up a 14" M3 Max in a few weeks.
Yes, I regularly drive my monitors with 1 intel laptop and/or 1 amd laptop (modern ones, linux). Not a single issue ever. I plug in my work m2 pro mac to these same monitors - constant issues.
> For all its flaws, Apple focuses on making sure there is a good experience overall.
MacOS has had dozens of well-know, well-documented bugs for years that haven't been addressed, many of them mentioned in this thread. I don't see any focus from Apple on these whatsoever - their main focus seems to be advertising and visual design.
The standard setup at my company is a ThinkPad connected to dual 27" monitor. My company has thousand of employees. (Mac setup is also available for those who requests.) Many many companies offer a similar setup for employees.
Maybe you need a reality check first.
Thanks for the kindness, I had my first laptop (PC) in the mid 80s, and have been writing software on various hardware configurations for 30 years, so maybe I just need a bit more reality I guess?
> The standard setup at my company is a ThinkPad connected to dual 27" monitors
No one claimed that dual monitors isn't possible.
Running two 4k large, high quality monitors off a low-end Intel integrated video controller at 120hz is going to be harder.
Apple is focused on higher-end experience, always has been. They're not a great choice if you're looking for standard enterprise arrangements.
You can go into pretty much any bank or office and see the kinds of setups that you're talking about.
You can also see the flicker and wince at the eye-strain.
This is a silly discussion.
Yes, sounds like you've been drinking apple koolaid and fanboying over bullshit for 40 years.
> This is a silly discussion.
What's silly is reading through comments of multiple people discussing actual issues they face with macs, completely ignoring what's said, and then claiming 'apple is focused on higher-end experience' based on nothing but your own anecdotal experience and imagination.
I mentioned that I switch back and forth between PC and Mac, depending on what's better at the time - so you're pretty far off the mark.
Regardless, why are you responding with such anger and venom?
> What's silly is ...
I'd like to suggest that you take a moment to reflect on how you treat others. Even a stranger online.
I notice that your account is 59 days old, so maybe you're new to the HN community.
This community frowns on personal attacks, we try to focus on comments that are informative and add to the discussion.
I recommend reviewing the comment guidelines [1]
Any 'anger and venom' is completely imagined by you.
> This community frowns on personal attacks,
Really? What personal attacks? Please point out exactly where I've personally attacked you.
> we try to focus on comments that are informative and add to the discussion.
You mean like your comments in this chain? Where you dismiss the entire conversation as 'silly', based on nothing but your own personal, anecdotal experience? If it's silly, no need to participate. Your comments are rude, condescending and add nothing of substance to the discussion.
Save this petty nonsense for reddit.
It would be annoying if you had to get a 16” laptop to be able to hook up to multiple external displays. I love my 16” MBP but my Air is the one that goes everywhere in my handbag.
[1] https://www.apple.com/macbook-pro/specs/ (scroll down to “Display Support”)
Also, the base MBP 14" doesn't support more than 1 display either.