Blurry rendering of games on Mac(colincornaby.me)
colincornaby.me
Blurry rendering of games on Mac
https://www.colincornaby.me/2025/08/your-mac-game-is-probably-rendering-blurry/
327 comments
> Are they supposed to leave a menu bar on macOS?
Depends also how the specific game is implemented, but often that area is just black and inaccessible, as in you cannot even move the cursor there. It is as if the screen does not include the area above the notch anymore, ie how the screen would be if there was no notch, like the m1 air.
Depends also how the specific game is implemented, but often that area is just black and inaccessible, as in you cannot even move the cursor there. It is as if the screen does not include the area above the notch anymore, ie how the screen would be if there was no notch, like the m1 air.
Thanks for explaining! I see this is common then. If I'm understanding correctly the docs of NSPrefersDisplaySafeAreaCompatibilityMode[1], this is supposed to be a compatibility mode that apps can opt-out of to behave like I expected, and can be force-disabled from Finder.
So I guess rendering around the notch is the intended experience, but devs don't seem to know or care enough to opt-out, and the bug here is that enumerating display resolutions doesn't take this compatibility mode into account.
[1]: https://developer.apple.com/documentation/bundleresources/in...
So I guess rendering around the notch is the intended experience, but devs don't seem to know or care enough to opt-out, and the bug here is that enumerating display resolutions doesn't take this compatibility mode into account.
[1]: https://developer.apple.com/documentation/bundleresources/in...
Hah I was not aware that a user can actually select that in finder. Really useful to know. Thanks for sharing!
Am I the only one who finds screens with rounded corners and notches really stupid? We had to struggle for decades with CRTs and their funky geometry, and when we finally get displays with perfect geometry, we botch them again to make them look... cooler?
Don't think of notches as something stupid that takes away from screen area.
Think of them as something that allows the overall screen area to increase, as bevels shrink.
And then when the corners of the screen are so close to the corner of the laptop, and the corner of the laptop is rounded, it looks weird if the corner of the screen isn't rounded. Like a square peg in a round hole.
Fortunately, it's all context-dependent. So when you watch a video that is inherently rectangular on a Mac, that takes precedence. It's only shown below the notch, and the rounded corners on the bottom disappear.
So it's kind of the best of all worlds. Bigger screen with round corners for actual work (the notch is not particularly objectionable in the menu bar), slightly smaller screen with rectangular corners for video (and games too I assume?).
Think of them as something that allows the overall screen area to increase, as bevels shrink.
And then when the corners of the screen are so close to the corner of the laptop, and the corner of the laptop is rounded, it looks weird if the corner of the screen isn't rounded. Like a square peg in a round hole.
Fortunately, it's all context-dependent. So when you watch a video that is inherently rectangular on a Mac, that takes precedence. It's only shown below the notch, and the rounded corners on the bottom disappear.
So it's kind of the best of all worlds. Bigger screen with round corners for actual work (the notch is not particularly objectionable in the menu bar), slightly smaller screen with rectangular corners for video (and games too I assume?).
Is bevel size really so important when it's already measured in mm? Personally I like a bit of bevel because I don't want the screen going to the edge of the device. The edge of the device is for holding, not interaction.
No, screen size is important. For the same size laptop, less bevel means more screen.
And I don't about you but I don't hold the screen half of my laptop. Not unless the laptop is closed. So I don't see how that's a concern.
And I don't about you but I don't hold the screen half of my laptop. Not unless the laptop is closed. So I don't see how that's a concern.
My point was at some point maximising screen size is less important than other usability factors. For phone definitely I do not want screen near the edge because fingers are there. For laptop, true, it's less of an issue. Although while opening my macbook my finger is about 1mm from touching the screen.
And the other comment about wasting screen space is funny. Yeah we need 1mm of extra phone screen space when 60% of most webpages are covered with ads (separate problem but still amusing in combination).
And the other comment about wasting screen space is funny. Yeah we need 1mm of extra phone screen space when 60% of most webpages are covered with ads (separate problem but still amusing in combination).
For the love of $DEITY, it’s bezel! :-)
https://www.howtogeek.com/762611/what-is-a-bezel/
https://www.howtogeek.com/762611/what-is-a-bezel/
I've often wondered about that, because I often see them used interchangeably (and not just here). But you're absolutely right. Here's a random site I found that explains it: https://www.difference.wiki/bevel-vs-bezel/
Is the similarity of the word the only reason they often get mixed up? I think another factor is that flat surfaces surrounded by an angled bevel are fairly common. For example. I just noticed that the bezel of one of my monitors is also beveled.
Is the similarity of the word the only reason they often get mixed up? I think another factor is that flat surfaces surrounded by an angled bevel are fairly common. For example. I just noticed that the bezel of one of my monitors is also beveled.
The bezel on my monitor has a bevel.
TIL. Thank you! Suddenly realizing I've had the words confused my whole life :S
But a cell phone, maybe. For a laptop, we are talking about a couple of millimetres on each side max, it is not a big deal.
...and then the same "more space!!!111" people run apps which fill their screen with useless whitespace.
I mean… I would be very happy to whip designers in public but I think that's illegal.
Hi, laptop repair tech here.
You want more bezel. Screens with less bezel have less overall edge protection and will break easier due to opening or closing forces or impacts.
Bezel-less screens are fragile pieces of junk.
You want more bezel. Screens with less bezel have less overall edge protection and will break easier due to opening or closing forces or impacts.
Bezel-less screens are fragile pieces of junk.
Tell me about it. I've replaced 2 screens on a MBP. One was from cleaning the edge of the screen. I applied just a little too much pressure and it destroyed the whole screen.
Another was when my kitten bit the edge of the screen. It didn't even leave a mark but it was just enough concentrated pressure at the edge of the screen that it killed it.
Now I'm a lot more careful, but thank goodness for Applecare.
Another was when my kitten bit the edge of the screen. It didn't even leave a mark but it was just enough concentrated pressure at the edge of the screen that it killed it.
Now I'm a lot more careful, but thank goodness for Applecare.
[deleted]
> then when the corners of the screen are so close to the corner of the laptop, and the corner of the laptop is rounded, it looks weird if the corner of the screen isn't rounded.
The rounded laptop corners is a similar design decision. And also it doesn't look weird to me at all compared to rounded corners for windows, especially when they introduce visible desktop garbage in those now-not-perfectly-covering-rectangles corner areas
The rounded laptop corners is a similar design decision. And also it doesn't look weird to me at all compared to rounded corners for windows, especially when they introduce visible desktop garbage in those now-not-perfectly-covering-rectangles corner areas
Rounded corners are not simply an aesthetic design choice, they make the device more durable as there's less of a pinch point when you drop, snag or mishandle the device.
First of all, you can not argue anyone out of thinking it looks stupid or ugly. That is a visceral subjective experience and the extra space or whatever does nothing to make up for it.
Now for the bezels, mind that an equidistant circle (or squircle) radius converges to zero. So to avoid having a large inner radius, avoid a large outer radius. The Macbook is not a tablet, you do not hold its corners in your hand.
However, at some point Apple must have decided that the squircle is its entire visual identity and that hard corners on the XY plane are bad. That creates design problems it would not otherwise have.
The fact that developers are led into the trap of not pixel matching to the display however just shows a lack of attention to detail.
Now for the bezels, mind that an equidistant circle (or squircle) radius converges to zero. So to avoid having a large inner radius, avoid a large outer radius. The Macbook is not a tablet, you do not hold its corners in your hand.
However, at some point Apple must have decided that the squircle is its entire visual identity and that hard corners on the XY plane are bad. That creates design problems it would not otherwise have.
The fact that developers are led into the trap of not pixel matching to the display however just shows a lack of attention to detail.
The bottom corners of a MacBook screen are not rounded. The top corners are because the corners of the case are rounded. The corners of the case are rounded because you need to be able to do things like slide it into a laptop bag.
> The bottom corners of a MacBook screen are not rounded.
They are on my M4 MBA. They're software-rounded rather than in the hardware. You can move the pointer over the lower rounded corners; you can't over the upper ones.
They are on my M4 MBA. They're software-rounded rather than in the hardware. You can move the pointer over the lower rounded corners; you can't over the upper ones.
> Fortunately, it's all context-dependent. So when you watch a video that is inherently rectangular on a Mac, that takes precedence. It's only shown below the notch, and the rounded corners on the bottom disappear.
Also, it's worth noting that notches are a hardware-specific. I haven't tried any of the MBAs with notches, but the MBPs have good-enough black levels that the notch just kind of vanishes into the black background when using full-screen apps.
Also, it's worth noting that notches are a hardware-specific. I haven't tried any of the MBAs with notches, but the MBPs have good-enough black levels that the notch just kind of vanishes into the black background when using full-screen apps.
The notch reduces the space available in the top menu bar. And since Apple is still incapable of creating a built-in Bartender-like functionality you end up with less space on screen.
It's an actual objective fact of life.
You don't get a larger 15"/16"/17" inch screen. You get a screen that size minus the notch because of a psychotic obsession with thinness. And then they struggle to compensate for that with barely working workarounds in software that don't cover even half of cases.
It's an actual objective fact of life.
You don't get a larger 15"/16"/17" inch screen. You get a screen that size minus the notch because of a psychotic obsession with thinness. And then they struggle to compensate for that with barely working workarounds in software that don't cover even half of cases.
The screen size advertised by Apple measures the "full screen" area, the undisturbed 16:10 rectangle of pixels. I just took measures on both a 14 and a 16 inch Macbook Pro. The screen we get is indeed slighly larger.
If you want to avoid the extra space, it's as easy as using a 16:10 resolution size. The menubar will drop down to the 16:10 space.
If you want to avoid the extra space, it's as easy as using a 16:10 resolution size. The menubar will drop down to the 16:10 space.
I just tried to do this and Apple has obfuscated that there’s even a 16:10 option. You have to click deep into the Displays customization presets menu. They don’t even label the presets with a display ratio and have them labeled with some obscure Apple design lingo (Apple XDR (P3-1600 nits)).
To change it you have to first display the hidden list by enabling a “display resolutions list” toggle.
That is not something a “I love Apple because it just works” person can figure out.
To change it you have to first display the hidden list by enabling a “display resolutions list” toggle.
That is not something a “I love Apple because it just works” person can figure out.
If the notch was replaced with a 1cm bezel, then the entire top menu bar would move down by roughly 1cm, and I'd have less screen space for actual content. In some ways, a bezel could be considered to be a "notch" that takes the entire width of the screen.
Personally, I've never run out of space in my menu bar, So the notch gives me 1cm of extra screen space.
It's nothing to do with thinness. It's about packing the largest possible display into the laptop's width/height. Sure, you could argue to just make the laptop 1cm higher for that bezel, but then why not add a notch and get 2cm of extra screen height?
Personally, I've never run out of space in my menu bar, So the notch gives me 1cm of extra screen space.
It's nothing to do with thinness. It's about packing the largest possible display into the laptop's width/height. Sure, you could argue to just make the laptop 1cm higher for that bezel, but then why not add a notch and get 2cm of extra screen height?
> If the notch was replaced with a 1cm bezel, then the entire top menu bar would move down by roughly 1cm, and I'd have less screen space for actual content.
That perceived 1cm is largely meaningless for content. And you get less space in the top menu bar.
> Personally, I've never run out of space in my menu bar
I have 27 icons in my menu bar. Not because I collect them, but because quite a few apps add their icons there and I use a few of them.
On the laptop screen it manages to show 10.
IntelliJ idea has 12 top-level menus (I swear they had more). On a laptop the top menu bar manages to show 10 items on the left of the notch, and has to move two more to the right. This both splits the menu for no reason, and reduces the space for icons even further.
The notch has been around for 4 years now, and Apple still hasn't provided a solution for the problem they introduced.
And, of course, when you want to truly take advantage of "more content" you can't because the "safe screen space" without the notch is still squarely below the notch, and apps have to to be very careful to actually use that, or the notch will get in the way.
> It's nothing to do with thinness.
Yes, it does. In this case with thinness of bezels.
> Sure, you could argue to just make the laptop 1cm higher for that bezel
Yes, you could do that if you didn't have an institutional psychosis about thinness everywhere.
That perceived 1cm is largely meaningless for content. And you get less space in the top menu bar.
> Personally, I've never run out of space in my menu bar
I have 27 icons in my menu bar. Not because I collect them, but because quite a few apps add their icons there and I use a few of them.
On the laptop screen it manages to show 10.
IntelliJ idea has 12 top-level menus (I swear they had more). On a laptop the top menu bar manages to show 10 items on the left of the notch, and has to move two more to the right. This both splits the menu for no reason, and reduces the space for icons even further.
The notch has been around for 4 years now, and Apple still hasn't provided a solution for the problem they introduced.
And, of course, when you want to truly take advantage of "more content" you can't because the "safe screen space" without the notch is still squarely below the notch, and apps have to to be very careful to actually use that, or the notch will get in the way.
> It's nothing to do with thinness.
Yes, it does. In this case with thinness of bezels.
> Sure, you could argue to just make the laptop 1cm higher for that bezel
Yes, you could do that if you didn't have an institutional psychosis about thinness everywhere.
> The notch has been around for 4 years now, and Apple still hasn't provided a solution for the problem they introduced.
As a lot of people told you, you can just disable it. I've been doing that for 4 years, just set your resolution to a 16:10 ratio and you're good to go. The resolution is exactly the same as it was before they introduced the notch
Personally I like the fact that Apple gives us the choice. I dislike the notch and prefer my menu bar below because I use apps like intellij. My wife likes the notch and keeps it. So, both of us can have what we want.
Maybe Apple could have made it slightly easier to disable it by having an option instead of choosing a 16:10 resolution but, to be honest, most of the people who dislike it tend to be power users who can figure it out.
As a lot of people told you, you can just disable it. I've been doing that for 4 years, just set your resolution to a 16:10 ratio and you're good to go. The resolution is exactly the same as it was before they introduced the notch
Personally I like the fact that Apple gives us the choice. I dislike the notch and prefer my menu bar below because I use apps like intellij. My wife likes the notch and keeps it. So, both of us can have what we want.
Maybe Apple could have made it slightly easier to disable it by having an option instead of choosing a 16:10 resolution but, to be honest, most of the people who dislike it tend to be power users who can figure it out.
What I'm learning from this entire line of discussion is that there is a subset of personalities who will find any reason to hate $COMPANY, in this case Apple. No amount of logical explanation will change their mind, there just isn't anything that $COMPANY can do right, no design decision sensible enough.
If the notch bothers you so much, then why not disable it?
It's actually optional, the functionality is built into Mac OS (just check "show all resolutions" in display setting and pick the notchless resolution). You get that bezel you want, along with the full menu bar.
> Yes, it does. In this case with thinness of bezels.
Device thickness is not the same thing as bezel thinness. If you make a phone/laptop thinner, all you get is less battery life. If you make bezels thiner, you get more display area.
It's actually optional, the functionality is built into Mac OS (just check "show all resolutions" in display setting and pick the notchless resolution). You get that bezel you want, along with the full menu bar.
> Yes, it does. In this case with thinness of bezels.
Device thickness is not the same thing as bezel thinness. If you make a phone/laptop thinner, all you get is less battery life. If you make bezels thiner, you get more display area.
To be honest, I wouldn't be surprised if it is requested and/or greenlit by Apple managers who only use their Macs for Safari or Mail. There can't be another way, because the menu splitting and icon disappearance is pretty infuriating.
Luckily I have mostly used Macs on external screens the last few years. But it ticks me off every time I actually use a MacBook as a laptop.
Luckily I have mostly used Macs on external screens the last few years. But it ticks me off every time I actually use a MacBook as a laptop.
I don't understand your logic unless you're implicitly saying the camera needs to go away, but then you should say so (so that I can properly disagree with you).
The notch makes for a smaller menu bar but without the notch there would be no menu bar there, it would take the space underneath instead.
The notch makes for a smaller menu bar but without the notch there would be no menu bar there, it would take the space underneath instead.
[deleted]
> I don't understand your logic unless you're implicitly saying the camera needs to go away
Yup. We never had camera before the notch.
> The notch makes for a smaller menu bar but without the notch there would be no menu bar there
Yup. Before the notch we neither had a menu bar that could comfortably fit most menu items even in professional apps, nor did we have a camera.
BTW, you literally are saying "The notch makes for a smaller menu bar". Imagine if I wrote that as the first sentence in my comment, then there would be no misunderstanding
Yup. We never had camera before the notch.
> The notch makes for a smaller menu bar but without the notch there would be no menu bar there
Yup. Before the notch we neither had a menu bar that could comfortably fit most menu items even in professional apps, nor did we have a camera.
BTW, you literally are saying "The notch makes for a smaller menu bar". Imagine if I wrote that as the first sentence in my comment, then there would be no misunderstanding
The screen is a 16:10 screen with some extra pixels added next to the notch.
By default, the system uses a resolution of 1512x982 (14"), which you can change to 1512x945 (16:10) to move the menu bar below the notch and end up with black pixels next to the notch.
"If you go make weird contortions and workarounds you might just find a semi-working non-solution to a problem that didn't exist until Apple introduced it".
Also my response here: https://news.ycombinator.com/item?id=44909996
Also my response here: https://news.ycombinator.com/item?id=44909996
What MacBook doesn't have a camera?
They are being sarcastic because the parent post put forward a false dichotomy between a notch and a camera or no notch but no camera.
I didn't think this would be so hard to understand. It's not a false dichotomy, without the notch the screen would have to be smaller to have the camera there. You didn't lose any pixels.
[deleted]
my menu icons are hiding behind the notch lol
I've got a MacBook with a notch and I literally never notice it. That's a common sentiment among MacBook users, btw -- I very rarely seeing people complain about the notch. I'm sure there are some, but seems to be a minority.
I frequently notice when my menubar items overflow and get truncated behind the notch with no built-in way to actually see them!
You have to hoop jump with janky tools[1] that actually let you see and access the icons silently hidden because they overshot the notch.
[1] https://macmenubar.com/menu-bar-managers/
You have to hoop jump with janky tools[1] that actually let you see and access the icons silently hidden because they overshot the notch.
[1] https://macmenubar.com/menu-bar-managers/
I think nothing shows more that Apple has lost it’s eye for detail and good designs than the icons disappearing behind the notch.
This has to be a vast gulf in terms of usage patterns for different users - I’ve managed at times to get up to six icons in my menu bar; what are you doing that fills up half the screen?
You didn’t lose pixels to the notch, you gained pixels beside it!
Look, given current technology there are exactly three options:
1. Don't have a front-facing camera on your laptop. Your actual laptop screen can be as close to the edge of the laptop case as technology will allow, with no bevel.
2. Have a front-facing camera on your laptop, with no bevel. Your actual laptop screen is now square, but has to be 5mm shorter now. There's a 5mm strip at the top of your laptop that can't be used for anything.
3. Have a front-facing camera on your laptop, with a bevel. Now the actual laptop screen has a "dead space" in middle at the top, but can again be as close to the edge of the laptop case as technology will allow. There's a narrow strip at the top that can't be used for anything, but the area to the left and right of the bevel can.
(A number 4 would be to somehow have a front-facing camera that operates without needing to displace screen area. Not clear how this would work without some complicated mechanism to extend the camera out the top of the screen, which would come with its own problems.)
Now, the vast majority of the time, you're going to be using your Mac in a windowed environment, with menus on the left, indicators on the right, and absolutely nothing in the middle.
In the case of #2, this menu bar has to take real estate from the top of your shorter screen, meaning that your windows are all 5mm shorter. #3 allows the menu bar and indicators to take up that space which on #2 is completely dead, freeing up extra space for your actual applications.
And the key thing is this: For modern full-screen games, in #3, you (apparently) can't use the areas to the side of the bezel; but this is the same situation you're in in #2.
IOW, as another commenter has said: The bevel design doesn't take away screen in the middle; it adds screen space on the side of the bevel.
That said, the API here seems obviously mad: What's the point of giving you a resolution if it's going to silently resize it behind your back? It should either give you the resolution which it won't resize, or throw an error when you try to make one higher.
1. Don't have a front-facing camera on your laptop. Your actual laptop screen can be as close to the edge of the laptop case as technology will allow, with no bevel.
2. Have a front-facing camera on your laptop, with no bevel. Your actual laptop screen is now square, but has to be 5mm shorter now. There's a 5mm strip at the top of your laptop that can't be used for anything.
3. Have a front-facing camera on your laptop, with a bevel. Now the actual laptop screen has a "dead space" in middle at the top, but can again be as close to the edge of the laptop case as technology will allow. There's a narrow strip at the top that can't be used for anything, but the area to the left and right of the bevel can.
(A number 4 would be to somehow have a front-facing camera that operates without needing to displace screen area. Not clear how this would work without some complicated mechanism to extend the camera out the top of the screen, which would come with its own problems.)
Now, the vast majority of the time, you're going to be using your Mac in a windowed environment, with menus on the left, indicators on the right, and absolutely nothing in the middle.
In the case of #2, this menu bar has to take real estate from the top of your shorter screen, meaning that your windows are all 5mm shorter. #3 allows the menu bar and indicators to take up that space which on #2 is completely dead, freeing up extra space for your actual applications.
And the key thing is this: For modern full-screen games, in #3, you (apparently) can't use the areas to the side of the bezel; but this is the same situation you're in in #2.
IOW, as another commenter has said: The bevel design doesn't take away screen in the middle; it adds screen space on the side of the bevel.
That said, the API here seems obviously mad: What's the point of giving you a resolution if it's going to silently resize it behind your back? It should either give you the resolution which it won't resize, or throw an error when you try to make one higher.
[deleted]
Option 4 was redesigning a camera unit to be narrow along the whole width of the screen instead of dropping in an oem component that demands the notch.
When you look at the remaining bezel along with the camera unit, the lens is the same size. They really could have built a bezelless mac more or less if they only stretched out the components in that camera unit.
When you look at the remaining bezel along with the camera unit, the lens is the same size. They really could have built a bezelless mac more or less if they only stretched out the components in that camera unit.
See Lenovo's design here https://p4-ofp.static.pub/ShareResource/na/products/thinkpad...
I like it - do you know if the space added for the camera extends past the bottom half of the laptop when it's closed? If yes, it feels like it would make it easier to open the laptop by grabbing it.
While I agree in general with your comment, a small nitpick on this:
> There's a 5mm strip at the top of your laptop that can't be used for anything.
Well, it can - on mine I have a physical switch that allows me to block the lens, and it saved me a few times. (I just wish I had a similar one for the microphone.)
> There's a 5mm strip at the top of your laptop that can't be used for anything.
Well, it can - on mine I have a physical switch that allows me to block the lens, and it saved me a few times. (I just wish I had a similar one for the microphone.)
i'll pick option 1 every time. you can't make me but a computer with a camera in it
> (A number 4 would be to somehow have a front-facing camera that operates without needing to displace screen area. Not clear how this would work without some complicated mechanism to extend the camera out the top of the screen, which would come with its own problems.)
I don't know, Lenovo figured it out, and it's no more ridiculous than Apple's solution. Their notch just goes the other way. It's actually a little bit better, because it gives me a space to put my thumb when I'm opening the laptop to, you know, use it.
Sometimes it seems to me like Apple engineers do not use Apple products, because if they did, there's no way we'd have problems like disappearing icons without a way to get them back (Hell, Windows has had this ability for DECADES, why can't Apple "invent" this technology?). We wouldn't have edge-to-edge glass screens which seem to exist solely to get fingerprints on the screen. We wouldn't have closed lids touching the keyboard, leaving weird patterns on the smudgy glass.
The only other option is that design at Apple is not driven by designers or engineers, but by executives who have no clue. And that's worse.
I don't know, Lenovo figured it out, and it's no more ridiculous than Apple's solution. Their notch just goes the other way. It's actually a little bit better, because it gives me a space to put my thumb when I'm opening the laptop to, you know, use it.
Sometimes it seems to me like Apple engineers do not use Apple products, because if they did, there's no way we'd have problems like disappearing icons without a way to get them back (Hell, Windows has had this ability for DECADES, why can't Apple "invent" this technology?). We wouldn't have edge-to-edge glass screens which seem to exist solely to get fingerprints on the screen. We wouldn't have closed lids touching the keyboard, leaving weird patterns on the smudgy glass.
The only other option is that design at Apple is not driven by designers or engineers, but by executives who have no clue. And that's worse.
For what it's worth, Macintosh had rounded corners since its inception in 1984. They were just bitmaps in the screen corners and still addressable by software (and even by the mouse cursor in any context) but this demonstrates an aesthetic heritage.
These software rounded corners disappeared in software when CRTs gave way to flat panels, but they are indisputably part of the Apple design aesthetic.
These software rounded corners disappeared in software when CRTs gave way to flat panels, but they are indisputably part of the Apple design aesthetic.
Are the screens OLED? The phones are...
IMO the notch is pointless, but they need space for the front camera. With OLED they can just turn the pixels off when it suits the application and it becomes like a big bevel, which was the alternative anyway.
IMO the notch is pointless, but they need space for the front camera. With OLED they can just turn the pixels off when it suits the application and it becomes like a big bevel, which was the alternative anyway.
Expected in the next year or two on the pros, but not yet.
My M1 MacBook Pro turns off the display & backlight that would show the notch as needed, for example right now in full screen Safari you could not tell there is a notch/menu bar area at all. It's actually just as good as it can be already. Free extra space!
Bezel not bevel FYI.
Bezel not bevel FYI.
The funny thing is, I had bezel initially, but saw so many instances of bevel here that I started to second-guess myself, haha.
I've always preferred the look of non-antialiased fonts on an LCD for this reason - you can finally actually see the sharp square corners of a pixel, yet somehow many like the blurry smoothness of antialiasing to make the screen more like a CRT.
I prefer text to be hinted and antialiased even in low resolutions on a CRT. The first time I saw this on BeOS in the 90s I thought it was a big step up.
You get corners snapped to pixels without jagged lines in-between. However, hinting makes text wider or narrower depending on font size and resolution.
Apple chose not to have hinting so as to make the text more dimensionally accurate. That did look blurry ... so Apple then doubled the screen resolution.
Apple chose not to have hinting so as to make the text more dimensionally accurate. That did look blurry ... so Apple then doubled the screen resolution.
A lot of games don’t even support the notched resolution so you get business as usual. The ones that do let you chose this resolution as well.
I don't have a notched laptop screen, but I do like rounded corners, makes screens feel just a little bit more natural. My MacBook is older and doesn't have rounded corners, but I got used to them so much that I ended up simulating them in software.
More natural why? Paper doesn't (usually) have rounded corners and it looks pretty natural to me.
It goes deep.
obligatory: https://www.folklore.org/Round_Rects_Are_Everywhere.html
obligatory: https://www.folklore.org/Round_Rects_Are_Everywhere.html
Menu bar is on top on mac. I see it as the top bevel becoming a screen, not taking away from any screen real estate, actually FREEING up space for apps. I never see the notch anyway because my wallpaper is black.
Until you want to do something full screen, then it might be a glaring black rectangle on top of the screen. The way to do it properly is to hide the camera in the thin bezels or somewhere else (inside the LCD, are we there yet?). This is just a lazy solution that designers probably even thought seems iconic.
Full screen stuff isn't supposed to go behind the notch, unless they opt in to supporting it. By default, fullscreen stuff just gets the notchless 16:10 area under the menubar, and the menubar area goes black, so the notch becomes invisible and nothing is "glaring", it just looks like the top bezel of the screen is larger.
I get what you mean, but to me it just looks like before there was a notch, like there's no screen there. I can't really tell where the bezel ends and the screen starts if it's all black. Just looks like a large bezel.
Guess it's just a matter of taste. I'm never bothered by it.
Guess it's just a matter of taste. I'm never bothered by it.
But if you hide it in a small bezel or behind the LCD you will get significantly worse camera quality.
The quality is already insane if you think about how thin it has to be, with "glass" in front of it and the alu behind it. Pinch it with your fingers, imagine a CAMERA being thinner than that...
I feel like the only one that's still amazed by tech sometimes. I still look at planes and feel amazed we puny humans did that. It's never good enough.
I feel like the only one that's still amazed by tech sometimes. I still look at planes and feel amazed we puny humans did that. It's never good enough.
Suppose it comes down to psychology. I recall reading long time ago that rounded corners signal safety since they can't cut you so easily so we gravitate towards those shapes.
Nope. I’m right there with you. I can’t even use my laptop undocked because half my applications use the toolbar to store their icon. So I have to plug my laptop into my monitor just to see what is in my screen space.
I have no idea why people praise these laptops, for a cpu I guess. Their design is a joke and feels like a Playskool laptop toy.
At least when the old Apple forced “phablets” as the standard phone size they included a software work around for reaching the top of the screen.
Not adding a dropdown menu for the toolbar is brain dead.
I have no idea why people praise these laptops, for a cpu I guess. Their design is a joke and feels like a Playskool laptop toy.
At least when the old Apple forced “phablets” as the standard phone size they included a software work around for reaching the top of the screen.
Not adding a dropdown menu for the toolbar is brain dead.
Yeah, it's annoying. Try:
https://github.com/jordanbaird/Ice
https://github.com/FelixKratz/SketchyBar
https://www.macbartender.com
I think there's a native solution (finally) coming in the next MacOS.
https://github.com/jordanbaird/Ice
https://github.com/FelixKratz/SketchyBar
https://www.macbartender.com
I think there's a native solution (finally) coming in the next MacOS.
I’m not trying anything because it should have been implemented before launch natively. Not years after as part of some Product manager promotion cycle. Not installing a fix is how Apple wants me to use my machine by default in a broken state.
In the time it took you to write your comments on this issue, you could have just fixed the problem.
It's a valid complaint, don't get me wrong... but insisting on not fixing it as some sort of moral stance is only hurting yourself.
People are weird, man.
It's a valid complaint, don't get me wrong... but insisting on not fixing it as some sort of moral stance is only hurting yourself.
People are weird, man.
I mostly work attached to a monitor. I will continue to work how I like, I don’t own a Macbook outside of work. I will continue not installing custom untrusted software just because a bunch of “fans” online told me to do it. I will continue complaining about it. All of that BECAUSE I enjoy the entropy it causes more than actually using the piece of garbage laptop.
I can do a lot of things instead of write that comment. And installing work arounds for a trillion dollar company with an attitude problem is not one of them. Give attitude, get attitude.
What’s weird is being a complacent drone even though you understand the issue.
I can do a lot of things instead of write that comment. And installing work arounds for a trillion dollar company with an attitude problem is not one of them. Give attitude, get attitude.
What’s weird is being a complacent drone even though you understand the issue.
No, you are not the only one
Nope. I think they're incredibly stupid as well.
You realise you can use the largest rectangular section of the screen as a rectangular screen right? Play a video and you’ll see. It’s the best of both worlds
Oh it’s not just Apple…
This was an issue I also discovered on Xbox 360 in 2008. TV’s have overscan and depending on that setting, your resolutions will be off.
However, at the time, we couldn’t create render targets that matched the overscan safe area. XNA added a Screen SafeArea rect to help guide people but it was still an issue that you had to consciously develop for.
Now, we can create any back buffer size we want. It’s best to create one 1:1 or use DLSS with a target of 1:1 to the safe area for best results. I’m glad the author went and reported it but ultimately it’s up to developers to know Screen Resolution != Render Resolution.
Anyone using wgpu/vulkan/AppKit/SDL/glfw/etc need to know this.
This was an issue I also discovered on Xbox 360 in 2008. TV’s have overscan and depending on that setting, your resolutions will be off.
However, at the time, we couldn’t create render targets that matched the overscan safe area. XNA added a Screen SafeArea rect to help guide people but it was still an issue that you had to consciously develop for.
Now, we can create any back buffer size we want. It’s best to create one 1:1 or use DLSS with a target of 1:1 to the safe area for best results. I’m glad the author went and reported it but ultimately it’s up to developers to know Screen Resolution != Render Resolution.
Anyone using wgpu/vulkan/AppKit/SDL/glfw/etc need to know this.
If I understood you correctly... you wanted to be able to render to a slightly smaller surface to avoid wasting graphics compute time, but that's still going to be upscaled to 1080 for the HDMI scanout, and then mangled again by TVs' overscan - which to me feels like introducing more problems more severe than whatever problem you were trying to solve in the first place.
(Besides, TV overscan is a solved problem: instead of specifically rendering a smaller frame games should let users set a custom FoV and custom HUD/GUI size - thus solving 3 problems at once without having to compromise anything).
(Besides, TV overscan is a solved problem: instead of specifically rendering a smaller frame games should let users set a custom FoV and custom HUD/GUI size - thus solving 3 problems at once without having to compromise anything).
No, Your TV says it’s 1080 but it’s not, it’s 1074… This is a solved issue now but it wasn’t when HDMI was first introduced. The Xbox 360 suffered from red rings of death. Microsoft hated Linux. And C# was cool.
Basically, if you rendered an avatar image in the top left of the screen, perfectly placed on your monitor, on the TV its head would be cut off. So you change to safe area resolution and it’s perfect again (but on your monitor safe area and screen resolution are the same, except Apple apparently). Make sense?
You can see how if your screen says it’s 4k, but really it’s short 40 pixels, you render at 4k - the screen will shrink it by 40 pixels and introduce nasty pixel artifacts. TV overscan goes the other way. Interesting find by the author about the notch.
Basically, if you rendered an avatar image in the top left of the screen, perfectly placed on your monitor, on the TV its head would be cut off. So you change to safe area resolution and it’s perfect again (but on your monitor safe area and screen resolution are the same, except Apple apparently). Make sense?
You can see how if your screen says it’s 4k, but really it’s short 40 pixels, you render at 4k - the screen will shrink it by 40 pixels and introduce nasty pixel artifacts. TV overscan goes the other way. Interesting find by the author about the notch.
Read up on g buffer and deferred rendering. Usually one doesnt do everything at full resolution until the final output and even then it is often better these days to have fancy upscaling.
Many games do let users set the things you mention but it is not always so simple. For example, handling rounded edges and notches is a huge pain.
Many games do let users set the things you mention but it is not always so simple. For example, handling rounded edges and notches is a huge pain.
I'm surprised this article focused solely on blurry rendering when mouse pointer location in "fullscreen" Mac games is also commonly affected by this bug or whatever we are calling it. You have to dive into an OS menu for each game to tell it to render fullscreen below the notch to fix it. It should be a global accessibility setting but isn't for some reason.
Yes!
I remember first implementing this in Planimeter Game Engine 2D, we got a massive resolution list from SDL (through LÖVE, which is what we're built on).
If I remember correctly, we filtered the list ourselves by allowing users to explicitly select supported display ratios first, then showing the narrowed list from there. Not great. Technically there's a 683:384 ratio in there.[1]
But it did enough of the job that users who knew what resolution they wanted to pick in the first place didn't have to scroll a gargantuan list!
[1]: https://github.com/Planimeter/game-engine-2d/blob/v9.0.1/eng...
I remember first implementing this in Planimeter Game Engine 2D, we got a massive resolution list from SDL (through LÖVE, which is what we're built on).
If I remember correctly, we filtered the list ourselves by allowing users to explicitly select supported display ratios first, then showing the narrowed list from there. Not great. Technically there's a 683:384 ratio in there.[1]
But it did enough of the job that users who knew what resolution they wanted to pick in the first place didn't have to scroll a gargantuan list!
[1]: https://github.com/Planimeter/game-engine-2d/blob/v9.0.1/eng...
Which says more about the volume of the market of gaming on Mac. It's small and unfortunate.
It's actually really small, according to Steam Hardware Survey, Macs are only 1.88% of Steam users, which is less than that of Linux, which is probably why most developers don't care.
Between the deprecation and stagnation of OpenGL on the platform, the removal of 32 bit support completely, the refusal to natively support Vulkan in favor of Metal, and the switch to ARM based systems... I can't believe it's still that "high".
Don't worry, they plan to gut Rosetta 2 so it will only support Mac games from the Intel era, that should help shrink that number!
> Rosetta was designed to make the transition to Apple silicon easier, and we plan to make it available for the next two major macOS releases – through macOS 27 – as a general-purpose tool for Intel apps to help developers complete the migration of their apps. Beyond this timeframe, we will keep a subset of Rosetta functionality aimed at supporting older unmaintained gaming titles, that rely on Intel-based frameworks.
https://developer.apple.com/documentation/apple-silicon/abou...
> Rosetta was designed to make the transition to Apple silicon easier, and we plan to make it available for the next two major macOS releases – through macOS 27 – as a general-purpose tool for Intel apps to help developers complete the migration of their apps. Beyond this timeframe, we will keep a subset of Rosetta functionality aimed at supporting older unmaintained gaming titles, that rely on Intel-based frameworks.
https://developer.apple.com/documentation/apple-silicon/abou...
Their compatibility layers being intended as exclusively transitional can be frustrating, but on the other hand it’s also why near every Mac app now has a proper aarch64 build. If it were known that Rosetta were going to remain part of the OS forever, many apps would’ve never been ported and would’ve been at an effectively permanent 30-60% performance penalty and disproportionate drags on battery life.
On the other side of the fence in Windows land, adoption of features much more trivial than an architecture change are absolutely glacial because devs know they can lean on back compatibility in perpetuity.
Apple’s approach is perhaps too aggressive but Microsoft’s is far too lax. I don’t think it’s realistic to dump a binary and expect it to work forever with no maintenance.
On the other side of the fence in Windows land, adoption of features much more trivial than an architecture change are absolutely glacial because devs know they can lean on back compatibility in perpetuity.
Apple’s approach is perhaps too aggressive but Microsoft’s is far too lax. I don’t think it’s realistic to dump a binary and expect it to work forever with no maintenance.
Even if Windows wanted to push hard to get off x86 they still lack ARM hardware worth moving to in the first place. I wouldn't be surprised if the 13" M1 MacBook alone shipped more units than all Windows 8/8.1/10/11 ARM devices combined. The 32 bit -> 64 bit app migration for x86 was also much slower on Windows but, again, there wasn't any real performance gain to be had until your app needed more than 4 GB of RAM in a single process, so no real pressure there either.
The moment Windows actually has non-x86 hardware which people actually want to buy I bet native app support comes pretty quick.
The moment Windows actually has non-x86 hardware which people actually want to buy I bet native app support comes pretty quick.
> The moment Windows actually has non-x86 hardware which people actually want to buy I bet native app support comes pretty quick.
Snapdragon X laptops are here already, and reviews are generally positive (of course, use and workload dependent, nobody should get one to game, but for web browsing and long battery life it's perfect).
Snapdragon X laptops are here already, and reviews are generally positive (of course, use and workload dependent, nobody should get one to game, but for web browsing and long battery life it's perfect).
Qualcomm's exclusivity deal with Microsoft started 9 years ago, but if you've got the numbers to say people are actually buying the latest Snapdragon option more often for web browsing than x86 laptops I'd be willing to believe something has finally changed. Otherwise there is always some special stat advertised about how "this time it really is better", yet it's never what people actually want.
Looking at the M1, there was no "if", "but", "for certain", etc wording. It was just better all around, even comparing gaming performance vs older MacBooks. Even running Windows ARM in a VM was better than buying a Windows laptop (x86 or ARM) in terms of both performance and battery. Based on your description, I don't think the Snapdragon X laptops are the same story?
Looking at the M1, there was no "if", "but", "for certain", etc wording. It was just better all around, even comparing gaming performance vs older MacBooks. Even running Windows ARM in a VM was better than buying a Windows laptop (x86 or ARM) in terms of both performance and battery. Based on your description, I don't think the Snapdragon X laptops are the same story?
I don't follow how Rosetta 2 supporting Mac games from the x86 era is going to "shrink" that number.
macOS x86 games + macOS arm64 games == same number of games. Whats the loss angle here?
macOS x86 games + macOS arm64 games == same number of games. Whats the loss angle here?
If amateurs can use game porting and achieve decent results then I think the actual devs can achieve excellent results.
My guess is that Mac users simply don’t buy games for their macs
My guess is that Mac users simply don’t buy games for their macs
> the refusal to natively support Vulkan in favor of Metal
1. Metal precedes Vulkan
2. Hardly anyone supports Vulkan https://www.carette.xyz/posts/state_of_vulkan_2024/
1. Metal precedes Vulkan
2. Hardly anyone supports Vulkan https://www.carette.xyz/posts/state_of_vulkan_2024/
1. You've named the release order, but not your argument behind why that should be limit what's currently supported today. E.g. if someone "OpenGL precedes Metal" wouldn't be an argument why Apple should not have added Metal support either.
2. I can easily list 5x as many AAA games, engines, or libraries supporting a Vulkan backend vs a Metal backend, does that mean Apple shouldn't support Metal? I'd say no, but maybe you're seeing this kind of logic differently. I'd be fully in support of macOS/iOS/iPadOS/visionOS adding native DirectX support, if that's what you mean. It just seems less likely than Vulkan (for several reasons).
2. I can easily list 5x as many AAA games, engines, or libraries supporting a Vulkan backend vs a Metal backend, does that mean Apple shouldn't support Metal? I'd say no, but maybe you're seeing this kind of logic differently. I'd be fully in support of macOS/iOS/iPadOS/visionOS adding native DirectX support, if that's what you mean. It just seems less likely than Vulkan (for several reasons).
This is of course horseshit. Vulkan was being developed before Metal and Apple was even part of that development - they only dropped out once they decided to do their own thing instead.
Vulkan is the primary rendering API on Android and Linux these days and also well supported on Windows by GPU vendors. Applications that don't use it yet generally don't because they don't need it and still OpenGL (ES) (or for Windows applications, use D3D instead).
Vulkan is the primary rendering API on Android and Linux these days and also well supported on Windows by GPU vendors. Applications that don't use it yet generally don't because they don't need it and still OpenGL (ES) (or for Windows applications, use D3D instead).
> This is of course horseshit. Vulkan was being developed before Metal and Apple was even part of that development
It's fascinating that history is changing so fast now that even events of 10 years ago can be claimed to be something they weren't.
- 2013: AMD starts developing Mantle, and it is only available as part of AMD Catalyst, and only on Windows.
- 2013 (at least): Apple starts working on their own graphics API.
- June 2014: Metal 1.0 on iPhones is announced by Apple (it means it had already been in development much earlier, that's why I wrote "2013 at least" above)
- July 2014: Khronos starts work on Vulkan
- August 2014: The announcement of the Vulkan project and the call for participation.
- June 2015: Apple announced Metal on Macs.
- Sometime in 2015: AMD discontinues Mantle and donates it to Khronos.
- December 2015: Vulkan 1.0 specification announced by Khronos group
- February 2016: The full spec and SDK for Vulkan 1.0 released
So, reality: Metal had been released two years before Vulkan even had a specification.
> also well supported on Windows by GPU vendors.
Keyword: GPU vendors. Not by Microsoft.
> Vulkan is the primary rendering API on Android and Linux these days
But not on Macs, iPhones, Windows, XBox, and Playstation.
And yet, "omg why doesn't Apple support this late-to-the scene quite shitty API that it must support because we say it must".
It's fascinating that history is changing so fast now that even events of 10 years ago can be claimed to be something they weren't.
- 2013: AMD starts developing Mantle, and it is only available as part of AMD Catalyst, and only on Windows.
- 2013 (at least): Apple starts working on their own graphics API.
- June 2014: Metal 1.0 on iPhones is announced by Apple (it means it had already been in development much earlier, that's why I wrote "2013 at least" above)
- July 2014: Khronos starts work on Vulkan
- August 2014: The announcement of the Vulkan project and the call for participation.
- June 2015: Apple announced Metal on Macs.
- Sometime in 2015: AMD discontinues Mantle and donates it to Khronos.
- December 2015: Vulkan 1.0 specification announced by Khronos group
- February 2016: The full spec and SDK for Vulkan 1.0 released
So, reality: Metal had been released two years before Vulkan even had a specification.
> also well supported on Windows by GPU vendors.
Keyword: GPU vendors. Not by Microsoft.
> Vulkan is the primary rendering API on Android and Linux these days
But not on Macs, iPhones, Windows, XBox, and Playstation.
And yet, "omg why doesn't Apple support this late-to-the scene quite shitty API that it must support because we say it must".
History aside, what are the technical merits of Vulkan vs Metal vs D3D?
Wouldn't it make sense to simply implement the technically best solution everywhere?
Wouldn't it make sense to simply implement the technically best solution everywhere?
Aside of the technical merits there are also the questions of open vs proprietary, platform availability etc.
Also the question of "technically best solution" is also fraught with subjective definitions of "better". You also want competition in approaches. E.g. Vulkan might not have happened (an we would be stuck wit OpenGL) without the newer more modern GPU APIs from Metal and DX12.
Also the question of "technically best solution" is also fraught with subjective definitions of "better". You also want competition in approaches. E.g. Vulkan might not have happened (an we would be stuck wit OpenGL) without the newer more modern GPU APIs from Metal and DX12.
It would be smaller than that overall because Steam stats are incomplete, they don't count all the Game Pass users. I haven't opened Steam in the six or so years I've been taking advantage of Microsoft providing a few hundred games for $10/month.
It's worth noting that the percentage of Steam users that are Mac users is not going to be equal to the percentage of gamers who play games on Macs, because not only is Steam not the only distribution channel for games on Mac, it's always been a fairly poor UX there, so bad I don't usually even bother installing it on my Macs anymore. Steam sees me as a Linux user as I have a Steam Deck, but I spend more time playing non-Steam games on my Mac than I do using that.
Actually, I think the last time I installed Steam on a Mac I did so in a CrossOver Games bottle, so even there Steam would have seen that install as a non-Mac user.
EDIT: Also just because I think it's interesting to note this, Steam Deck accounts for most of Linux's headroom there, if you subtract the SteamOS numbers from the rest of Linux it's at 2.07% instead, which is much closer to Mac.
Actually, I think the last time I installed Steam on a Mac I did so in a CrossOver Games bottle, so even there Steam would have seen that install as a non-Mac user.
EDIT: Also just because I think it's interesting to note this, Steam Deck accounts for most of Linux's headroom there, if you subtract the SteamOS numbers from the rest of Linux it's at 2.07% instead, which is much closer to Mac.
> It's worth noting that the percentage of Steam users that are Mac users is not going to be equal to the percentage of gamers who play games on Macs
Exactly this. As a piece of anecdata, I play World of Warcraft every day on my Mac, but I don't have steam installed.
Exactly this. As a piece of anecdata, I play World of Warcraft every day on my Mac, but I don't have steam installed.
Mac users might prefer to get their games through the default Mac App Store than Steam for distribution which plausibly could unrealistically distort the numbers.
I do my work on a Mac. I game on a game machine. Which right now is a Steam Deck. In the past it's been PS4, 360, Gamecube, PS2, etc.
I think the only game I've put serious time into on my Mac was Hades 1, which I pretty much finished before the console ports happened.
I think the only game I've put serious time into on my Mac was Hades 1, which I pretty much finished before the console ports happened.
I went the other direction: moved away from mac, windows, and game consoles into a monster PC running Manjaro. Now I can invest all my money into one machine and see benefits in all aspects of my life: work, personal projects, gaming, video editing, photo editing. I just stream from it to other devices if I'm mobile.
This just shows how little Apple cares about gaming on Mac. It's so sad that I spent thousands on multiple Mac devices (MBP, M Studio, etc.) only to be bottlenecked not by hardware, but by Apple's shitty approach to gaming software.
I know why they do it though. Apple can't take their undeserved 30% cut of Mac games the same way they take their iOS cuts.
We had a teacher years ago who said something that remains true until today: "everything is about money, especially the ones that appear to have non-monetary reasons."
I know why they do it though. Apple can't take their undeserved 30% cut of Mac games the same way they take their iOS cuts.
We had a teacher years ago who said something that remains true until today: "everything is about money, especially the ones that appear to have non-monetary reasons."
I think their bigger problem is there's shit for documentation. You get a big list of function signatures and if you actually want to know how you're supposed to use anything you find the WWDC session from 4 years ago and hope it's still accurate.
A WWDC session, I might add, with a mildly relevant title and rarely a hyperlink from the relevant documentation, let alone a timestamp.
What's even worse is they used to have great documentation, then for some nonsense reason archived it and replaced it with this wannabe JavaDocs crap with vague function explanations that leave more questions open than they resolve.
They now tell people to watch WWDC videos as if those relatively short videos contained the same amount of information a proper API documentation does.
They now tell people to watch WWDC videos as if those relatively short videos contained the same amount of information a proper API documentation does.
honestly i don't see this as Apple-specific but more of a sign of the times. i've seen a few libraries and vendor platforms we use at work with the same style of documentation (really lack thereof).
Microsoft's documentation quality very noticeably fell of a cliff about a decade ago. Now most of their public APIs and SDKs have hundreds of thousands of "documentation" pages that are just the name of the function with spaces added between the words. There might also be a listing of the parameters, which helpfully tells you that "string param1" is called "param1" and takes a string as the data type.
Yeah, the extreme basics seems to be the trend. We've actually had a lot of trouble due to this exact problem with one particular vendor now. Even repeated requests to improve their documentation are completely ignored or laughed off. it's too bad I don't have the purchasing power otherwise I'd suggest we should find a different vendor.
But if you find anything with the dark-blue "documentation archive" header, then you know it's some good stuff. Though sometimes outdated.
We've come from the monstrous Inside Macintosh tomes, to that early OS X documentation (that's now in the documentation archive), to this seemingly programmatically generated from doc comments thing.
Next they'll start generating documentation from code using LLMs...
That's an odd way to spell "AI hallucination"
Somebody told me that the quality of a company is directly proportional to the quality of its documentation...
Boeing's documentation is probably excellent.
In general it is assumed that documentation is the boring part and paying attention to it is a sign of quality. But where do you put people who prefer writing and/or teaching to thinking long and deep about product issues ?
In general it is assumed that documentation is the boring part and paying attention to it is a sign of quality. But where do you put people who prefer writing and/or teaching to thinking long and deep about product issues ?
Perhaps the biggest issue with the 737 MAX was lack of documentation. Boeing consciously chose to completely omit several new features (most notoriously MCAS) from the pilot manuals in order to make it seems like nothing important was changed that would require retraining 737 NG pilots on a simulator.
In a sense, this is far worse than what most tech companies do since it is a life-and-death issue and Boeing has made a very conscious effort to hide details here, rather than just being lazy.
In a sense, this is far worse than what most tech companies do since it is a life-and-death issue and Boeing has made a very conscious effort to hide details here, rather than just being lazy.
One could say that "the point" of MCAS was to be an implementation detail, something that you would often deliberately hide from software documentation so that users don't design around internal details.
There's something of a history of aerospace vendors omitting "implementation details" that end up contributing to serious accidents (e.g. if you get an Airbus far enough out of the normal envelope protections, you lose stall warning), and an equally sordid history of flight and maintenance crews improvising procedures to the observed (rather than designed/specified) behavior of aircraft systems.
Arguably, the single biggest systematic risk in the current pilot training system is that crews overlearn to the implementation details of their training, rather than the actual principles and flight manuals (e.g. training inadvertently training for quick engine shutdowns, when the consequences of shutting down the wrong engine in reality are much more serious).
There's something of a history of aerospace vendors omitting "implementation details" that end up contributing to serious accidents (e.g. if you get an Airbus far enough out of the normal envelope protections, you lose stall warning), and an equally sordid history of flight and maintenance crews improvising procedures to the observed (rather than designed/specified) behavior of aircraft systems.
Arguably, the single biggest systematic risk in the current pilot training system is that crews overlearn to the implementation details of their training, rather than the actual principles and flight manuals (e.g. training inadvertently training for quick engine shutdowns, when the consequences of shutting down the wrong engine in reality are much more serious).
> There's something of a history of aerospace vendors omitting "implementation details" that end up contributing to serious accidents (e.g. if you get an Airbus far enough out of the normal envelope protections, you lose stall warning),
And Airbus control laws and protections are well defined and studied by pilots training for them.
And Airbus control laws and protections are well defined and studied by pilots training for them.
They are now, just as MCAS behavior is well-defined and covered in conversion training now. They were not covered as well prior to AF447.
You encourage them to blog about it and you aggregate the posts into documentation - somehow. (I'm sure there's people for that, or an AI, or something). They had to explain it when they implemented it - explain it on a post. Confluence. Somewhere.
You're right though.
You're right though.
>Boeing's documentation is probably excellent.
it isn't, it's just ISO/NADCAP conforming.
it isn't, it's just ISO/NADCAP conforming.
Tech writer. Google famously employs quite a few of them for internal documentation.
I've read one of the manuals for the 787 management software stack, and it was... beautiful. It read like a novel. I read it twice on the train for the simple pleasure of it.
I guess mathworks is one of the best companies ever.
Microsoft has excellent documentation. So that's one counterexample. :)
It was excellent. It's a mess last time I looked.
Their documentation for the very newest stuff contains very obviously AI-generated inaccurate and misleading crap.
Don't believe me? Go look at it yourself. They've even "edited" the old docs with AI slop.
https://learn.microsoft.com/en-us/windows-hardware/drivers/u...
"The characteristics of the endpoint determine the size of each packet is fixed and determined by the characteristics of the endpoint."
https://learn.microsoft.com/en-us/windows-hardware/drivers/u...
"The characteristics of the endpoint determine the size of each packet is fixed and determined by the characteristics of the endpoint."
That sentence was already there _at least_ since Dec 2022, stop seeing AI everywhere.
https://web.archive.org/web/20221214171028/https://learn.mic...
https://web.archive.org/web/20221214171028/https://learn.mic...
They were using an automated editing tool before that.
Moving goalpost + evidence needed
If they used AI the sentence would be coherent
No they don't. Just last week I was looking for something, found a Google result from Microsoft's docs, but opening it resulted in a page saying they're moving docs around, this one isn't being moved, fuck off. No content, no link to the content.
Most of the time I just get function signatures that are already exposed via intellisense.
Sometimes they actually have examples of how to use it, but most are just Javadoc level, and of minimal use.
Sometimes they actually have examples of how to use it, but most are just Javadoc level, and of minimal use.
I can attest to that. I used to freelance doing porting about 10 years ago, and the main way of having a stable event loop for a game on macOS is not really anywhere clear in the documentation, at least not anywhere I could find.
Libraries and SDL, GLFW and Sokol handle this for you, and I had to poke inside them to actually figure out how to get the same performance of other games.
In a nutshell, the trick is simple, you call [NSApplication finishLaunching] and do a while-loop yourself instead of calling [NSApplication run].
Libraries and SDL, GLFW and Sokol handle this for you, and I had to poke inside them to actually figure out how to get the same performance of other games.
In a nutshell, the trick is simple, you call [NSApplication finishLaunching] and do a while-loop yourself instead of calling [NSApplication run].
Most of this stuff uses APIs greater than four years old, so you're probably not getting those videos unless you look at third party rehosts.
They sure don't care about games on Mac, but I think this specific issue is more due to trying to do "magic" for better or worse.
Introducing the notch creates this "here but not really usable" area that is specific to some displays, and Apple touts it as something that will just work thanks to their software layer.
Yet every app has to deal with it one way or another and most apps that care about screen estate or resolution will need hacks.
It will be the same for every feature that pushes the boundaries and offers an abstraction layer as an answer to how the issues will be solved.
Introducing the notch creates this "here but not really usable" area that is specific to some displays, and Apple touts it as something that will just work thanks to their software layer.
Yet every app has to deal with it one way or another and most apps that care about screen estate or resolution will need hacks.
It will be the same for every feature that pushes the boundaries and offers an abstraction layer as an answer to how the issues will be solved.
No, every app does not need to deal with it, at least in principle. Apple could literally have provided a resolution list which only covers the 16:10 resolutions which aren't covered by the notch, and then games literally wouldn't have known that they were running on a machine with a notch.
The problem here is 100% that Apple, for some reason, provides both 16:10 "safe" resolutions and the actual whole screen resolutions. All those non-16:10 resolutions are a trap, because they cause the compositor to downscale the window to fit below the notch anyway -- they serve literally no point. There is no situation where a user would want a window that's 16:10.39 or whatever and then downscaled to fit within the bounds of the 16:10 safe area, so there is no reason to provide those 16:10.39 resolutions in the list of display modes.
Apple botched the implementation, but the hardware would've been perfectly reasonable and caused no issues or complexities for either users or developers if Apple hadn't botched the software.
The problem here is 100% that Apple, for some reason, provides both 16:10 "safe" resolutions and the actual whole screen resolutions. All those non-16:10 resolutions are a trap, because they cause the compositor to downscale the window to fit below the notch anyway -- they serve literally no point. There is no situation where a user would want a window that's 16:10.39 or whatever and then downscaled to fit within the bounds of the 16:10 safe area, so there is no reason to provide those 16:10.39 resolutions in the list of display modes.
Apple botched the implementation, but the hardware would've been perfectly reasonable and caused no issues or complexities for either users or developers if Apple hadn't botched the software.
There are ways for an application to actually use 100% of the screen and draw over the notch[0], and apps taking screen captures or need to know the screen area but not for drawing will also need the full actual screen resolution.
https://www.reddit.com/r/MacOS/comments/qveb0u/force_true_fu...
https://www.reddit.com/r/MacOS/comments/qveb0u/force_true_fu...
Yeah, and there should be a special "get the actual full resolution of the screen" for those apps which use the special "draw to the actual full resolution of the screen" APIs. But the normal case should be for the OS to upheld the illusion that the screen has a 16:10 aspect ratio which excludes the part with the notch.
Or a (user-configurable) setting per app, and if the user configures the app to run below the notch, the OS should return the 16:10 resolutions and make the app draw below the notch; and if the user configures the app to take up the whole screen, the OS should return the full resolutions and make the app draw to the whole screen.
There should be no case where the app gets told about the 16:10.34 resolutions through normal display mode query APIs, but then gets scaled by the OS to fit in the 16:10 area below the notch.
Or a (user-configurable) setting per app, and if the user configures the app to run below the notch, the OS should return the 16:10 resolutions and make the app draw below the notch; and if the user configures the app to take up the whole screen, the OS should return the full resolutions and make the app draw to the whole screen.
There should be no case where the app gets told about the 16:10.34 resolutions through normal display mode query APIs, but then gets scaled by the OS to fit in the 16:10 area below the notch.
Im on an M3 Ultra Mac Studio. A $4K computer. And I'm not sure why but if I try to stream anything on StreamLabs (even with no game open), the recording is laggy and choppy. I just don't understand how that's possible.
> I know why they do it though. Apple can't take their undeserved 30% cut of Mac games the same way they take their iOS cuts.
Why would Apple be deliberately sabotaging the experience? They would gain nothing from it. That argument makes even less sense when you consider most of the games mentioned in the article are on the Mac App Store, Apple can take their cut.
https://apps.apple.com/us/app/control-ultimate-edition/id650...
https://apps.apple.com/us/app/shadow-of-the-tomb-raider/id14...
https://apps.apple.com/us/app/riven/id1437437535
https://apps.apple.com/us/app/cyberpunk-2077-ultimate/id6633...
https://apps.apple.com/us/app/stray/id6451498949
This is an obvious case of Hanlon’s Razor. Anyone who develops for Apple platforms and has had to file Feedbacks is aware of Apple’s incompetence and lack of care.
Why would Apple be deliberately sabotaging the experience? They would gain nothing from it. That argument makes even less sense when you consider most of the games mentioned in the article are on the Mac App Store, Apple can take their cut.
https://apps.apple.com/us/app/control-ultimate-edition/id650...
https://apps.apple.com/us/app/shadow-of-the-tomb-raider/id14...
https://apps.apple.com/us/app/riven/id1437437535
https://apps.apple.com/us/app/cyberpunk-2077-ultimate/id6633...
https://apps.apple.com/us/app/stray/id6451498949
This is an obvious case of Hanlon’s Razor. Anyone who develops for Apple platforms and has had to file Feedbacks is aware of Apple’s incompetence and lack of care.
Except for the handful of Mac ports exclusive to the Mac App Store, who with a lick of sense would choose to buy from there? Steam, GoG and Epic are all more feature rich, have more often sales/3rd party resellers and throw in the PC version too.
On iOS there is no choice.
On iOS there is no choice.
When No Man’s Sky first announced a Mac port, they promised to release on Steam and App Store. I waited a year after the Steam release for the App Store release which never came.
I am a very casual gamer and sometimes weeks go by without playing. My first experience with Steam was with Civ VI. Long flight, no internet, great I’ll play some Civ! But instead of opening up Civ, I was forced to open Steam which would then not allow me to play my own game because I hadn’t authenticated recently enough for them. Or I would try to play and Steam would say, oh first you need to download some huge update before you’re allowed to play your single player entirely offline game.
I know theoretically GoG is supposed to solve this issue but no Mac game I wanted was available there. Finally Cyperpunk 2077 launched on multiple stores and I bought on GoG. Even then, the default option became to use the GoG launcher. If I wanted DRM free download, there was some immediately complicated off putting set of instructions, downloading something like 20+ files, etc.
App Store experience, I click download, it downloads. I open it, it opens the app and not some launcher. Everything just works.
I am a very casual gamer and sometimes weeks go by without playing. My first experience with Steam was with Civ VI. Long flight, no internet, great I’ll play some Civ! But instead of opening up Civ, I was forced to open Steam which would then not allow me to play my own game because I hadn’t authenticated recently enough for them. Or I would try to play and Steam would say, oh first you need to download some huge update before you’re allowed to play your single player entirely offline game.
I know theoretically GoG is supposed to solve this issue but no Mac game I wanted was available there. Finally Cyperpunk 2077 launched on multiple stores and I bought on GoG. Even then, the default option became to use the GoG launcher. If I wanted DRM free download, there was some immediately complicated off putting set of instructions, downloading something like 20+ files, etc.
App Store experience, I click download, it downloads. I open it, it opens the app and not some launcher. Everything just works.
I’ve been a long time iOS user.
A fair amount of my purchased software won’t run anymore as it wasn’t updated from 32->63 bit change. I had some Mac software in the same boat. App Stores have some ease of use advantages, but it “just works” till at some point it doesn’t.
I’ll angree it’s annoying to have be internet connected to use the software. FWIW the steam deck seems to work with games offline, so maybe they fixed some of those issues?
I guess that's true, though I don't think you have to launch games through the steam app, but they try to make it convenient to do so.
You can also right-click the game and 'Browse local files' and the game's regular executable is usually right there.
I'm currently playing the Oblivion remake, and launch that through a mod manager rather than Steam (though on Windows), even though the game was installed via Steam.
You can also right-click the game and 'Browse local files' and the game's regular executable is usually right there.
I'm currently playing the Oblivion remake, and launch that through a mod manager rather than Steam (though on Windows), even though the game was installed via Steam.
> though I don't think you have to launch games through the steam app, but they try to make it convenient to do so.
It depends on the game, they do offer some kind of DRM, which requires Steam to be open when launching the game, but it's optional for the developer to use it or not. See https://www.pcgamingwiki.com/wiki/Digital_rights_management_...
PCGamingWiki also usually has information on whether the game is DRM-free or not, e.g.: https://www.pcgamingwiki.com/wiki/Hades#Availability
It depends on the game, they do offer some kind of DRM, which requires Steam to be open when launching the game, but it's optional for the developer to use it or not. See https://www.pcgamingwiki.com/wiki/Digital_rights_management_...
PCGamingWiki also usually has information on whether the game is DRM-free or not, e.g.: https://www.pcgamingwiki.com/wiki/Hades#Availability
Surely this isn't your policy for all software. I've known many people that defend the App Store on iOS this way, but nobody that uses a Mac exclusively for App Store software.
That doesn’t matter. We’re not discussing “all software”, we’re discussing games. You can simultaneously dislike the Mac App Store and still prefer it over Steam. Those ideas aren’t contradicting.
> On iOS there is no choice.
Two things people think can't be done, but are:
https://setapp.com/
https://www.xbox.com/en-us/play
Save the Xbox one to home screen for full screen experience, turning your iPhone or even iPad 13" into a Logitech gCloud if you add https://www.amazon.com/dp/B0D7CHHB42
Two things people think can't be done, but are:
https://setapp.com/
https://www.xbox.com/en-us/play
Save the Xbox one to home screen for full screen experience, turning your iPhone or even iPad 13" into a Logitech gCloud if you add https://www.amazon.com/dp/B0D7CHHB42
That is not only completely irrelevant to the point, it’s also wrong and inconsiderate of the preferences of others. I agree with the other commenter that the Mac App Store has advantages in terms of experience, especially if you’re not constantly gaming.
* Steam is constantly updating, every time you open it, and until recently videos would almost always fail to play on my Mac.
* The Epic Games launcher is so atrocious that calling it “feature-rich” feels like a bad joke. I find it so bad that I don’t even open it to get the free games, opting instead for the website, and even then I am super selective about any game I get (fewer than 10%) because I always think I’ll have to deal with that app. In its current state, there is zero chance I’ll ever by a game on there, all because of the app. My “favourite feature” is how if you queue a bunch of games to install and then set a few others to uninstall, those are added to the same queue and you have to wait for the installs to finish before the uninstalls get a chance. So if you are low on disk space, now you have to, one by one, cancel each of the installs and tell them to start again, so they are added to the bottom of the queue.
* GOG Galaxy was the biggest disappointment. I was expecting to like it but it only lasted an hour on my machine before I trashed it. It felt old and incomplete.
* Steam is constantly updating, every time you open it, and until recently videos would almost always fail to play on my Mac.
* The Epic Games launcher is so atrocious that calling it “feature-rich” feels like a bad joke. I find it so bad that I don’t even open it to get the free games, opting instead for the website, and even then I am super selective about any game I get (fewer than 10%) because I always think I’ll have to deal with that app. In its current state, there is zero chance I’ll ever by a game on there, all because of the app. My “favourite feature” is how if you queue a bunch of games to install and then set a few others to uninstall, those are added to the same queue and you have to wait for the installs to finish before the uninstalls get a chance. So if you are low on disk space, now you have to, one by one, cancel each of the installs and tell them to start again, so they are added to the bottom of the queue.
* GOG Galaxy was the biggest disappointment. I was expecting to like it but it only lasted an hour on my machine before I trashed it. It felt old and incomplete.
It's not irrelevant. How much is Apple really making off Mac game sales from the MAS?
Compared to the MAS, Epic is a good launcher for games. Take a look at CP2077. On the MAS you can't just download the language you need, you have to get all of them. This increases the download by 60GB. No other platform has this issue. So it ends up being 160GB which is nuts and more than half the storage on a base model M4 Mac. It's insanely barebones and half assed for gaming.
Compared to the MAS, Epic is a good launcher for games. Take a look at CP2077. On the MAS you can't just download the language you need, you have to get all of them. This increases the download by 60GB. No other platform has this issue. So it ends up being 160GB which is nuts and more than half the storage on a base model M4 Mac. It's insanely barebones and half assed for gaming.
BG3 on Gog wanted Steam for various capabilities like online multiplayer, which in turn wanted Rosetta. The game itself supported ARM without Rosetta.
It's a shame because a Mac Mini is a solid gaming computer.
I just replaced a nuc 9 ghost canyon with a Mac mini.
The difference in power consumption is insane. Nuc was 67 watts. The mini is 4-10. I don’t have enough data for a long term average on the mini yet, but it’s ludicrously efficient.
The difference in power consumption is insane. Nuc was 67 watts. The mini is 4-10. I don’t have enough data for a long term average on the mini yet, but it’s ludicrously efficient.
Is it me or is a 6 year old product on 14nm against whatever isn't exactly the most level of comparisons?
Its been across the board for me. Have ryzen 6xxx-8xxx mini PCs that are 45-60W and my 5 year old M1 Mini is comparable at a fraction of power draw
I would think a low TDP Ryzen chip shouldn't be that much different. Were those the 15W TDP Ryzens?
30W and 54Ws. iGPU performance is also better on the Mac compared to the non-65W Ryzens.
The good thing is that the Ryzen boards can be upgraded on RAM and Storage but that seems to be changing with soldered DDR5 on many mini PCs now.
The good thing is that the Ryzen boards can be upgraded on RAM and Storage but that seems to be changing with soldered DDR5 on many mini PCs now.
The comparison wasn’t meant to be fair - power usage is why I upgraded.
Both are on 10gbe, and I suspect the card in the Nuc was a bit of a power draw.
Both are on 10gbe, and I suspect the card in the Nuc was a bit of a power draw.
Mac Mini is i believe the most efficient consumer computer made ever. It uses the same energy most computers Ethernet ports use.
> Mac Mini is i believe the most efficient consumer computer made ever
My raspberry pi is sitting at 3 watts, and runs linux software just fine.
A Mac Mini uses multiple times that, and can barely run any software I care about (i.e. linux).
They're both consumer computers, and yes there's a massive difference in their capabilities, but "most efficient ever" is a really strong claim.
My raspberry pi is sitting at 3 watts, and runs linux software just fine.
A Mac Mini uses multiple times that, and can barely run any software I care about (i.e. linux).
They're both consumer computers, and yes there's a massive difference in their capabilities, but "most efficient ever" is a really strong claim.
The raspberry pi is great. Absolutely love them. Been running them as dev boards (robotics) and servers (at home) for 10+ years. Last time I truly, genuinely, felt excited about Christmas was when my SO gave one to me back in 2014 or so.
But I wouldn't compare the experience to a Mac Mini, and I wouldn't call a raspberry pi a "consumer computer". It solidly falls into the amateur dev board category. Heck, it doesn't even have a power button.
But I wouldn't compare the experience to a Mac Mini, and I wouldn't call a raspberry pi a "consumer computer". It solidly falls into the amateur dev board category. Heck, it doesn't even have a power button.
The claim was about efficiency, not just power draw.
In your comparison you talk about software compatibility, but the Mac can run Linux and many open source tools & apps found on it. So the Pi is only ahead if you arbitrarily limit the comparison to a specific distro that's not Asahi or an application like sxiv, and in addition are the kind of user who wants that software and doesn't care about Mac exclusive programs. Which is valid, but has nothing to do with a metric like power efficiency.
In your comparison you talk about software compatibility, but the Mac can run Linux and many open source tools & apps found on it. So the Pi is only ahead if you arbitrarily limit the comparison to a specific distro that's not Asahi or an application like sxiv, and in addition are the kind of user who wants that software and doesn't care about Mac exclusive programs. Which is valid, but has nothing to do with a metric like power efficiency.
I’m running Ubuntu on the Mac, in UTM.
It works well. Quite why networking from VM is more reliable than networking from the host is a question I’d like to ask Apple. SMB does not reliably start at boot.
Imagine if you could turn on a Mac mini, have docker containers start and then have them access network shares reliably.
The Ubuntu VM on the same host can. That’s ridiculous.
It works well. Quite why networking from VM is more reliable than networking from the host is a question I’d like to ask Apple. SMB does not reliably start at boot.
Imagine if you could turn on a Mac mini, have docker containers start and then have them access network shares reliably.
The Ubuntu VM on the same host can. That’s ridiculous.
The mini does 6.74 Gflops/W. At the default clock rate of 1200 MHz the Pi 3 can achieve 6.2 Gflops. However, without a heatsink the CPU will instantly throttle to half speed and average about 3.1 Gflops. So the mini is 3 to 6 times as efficient.
> A Mac Mini uses multiple times that, and can barely run any software I care about (i.e. linux).
You’re both right, and wrong.
The Mac uses 3-4W most the time. The reason mine is using more is that it has an Ubuntu VM running Pihole (so it is running Linux). This doubles/triples the power usage.
If I wasn’t such a chicken, I’d run it on the host in docker, but I’ve learned the pain of having Pihole on the same host as other services. Dead dns is not not good.
I really wish I could run Ubuntu on the metal. Something as simple as having docker containers run on boot is unreliable, and the god awful hack I have made to get it to work is so disgusting it’s shameful.
You’re both right, and wrong.
The Mac uses 3-4W most the time. The reason mine is using more is that it has an Ubuntu VM running Pihole (so it is running Linux). This doubles/triples the power usage.
If I wasn’t such a chicken, I’d run it on the host in docker, but I’ve learned the pain of having Pihole on the same host as other services. Dead dns is not not good.
I really wish I could run Ubuntu on the metal. Something as simple as having docker containers run on boot is unreliable, and the god awful hack I have made to get it to work is so disgusting it’s shameful.
I genuinely curious, how are you noticing? Do you have a power plug that reports that data to you or is the room with it noticibly hotter, or?
I have one of those Kasa H110 smart plugs that reports power usage.
I have a few bits of hardware on them so that I can force a hard reboot remotely if needed. Crude, but effective.
https://www.tp-link.com/us/home-networking/smart-plug/hs110/
I have a few bits of hardware on them so that I can force a hard reboot remotely if needed. Crude, but effective.
https://www.tp-link.com/us/home-networking/smart-plug/hs110/
> It's a shame because a Mac Mini is a solid gaming computer
Well, Apple doesn't sell 'em with RGB LEDs built-in, so I dunno.
...more seriously though: I don't know how you can say that with a straight-face. On paper, the Apple Silicon M3 and M4 seem comparable to NVIDIA's mid-tier offerings from 3-4 years ago... when rendering to a 1080p-sized display; assuming you'd like to render your games at native Retina or even 5K resolution (given that Apple would really rather you used their display hardware for the best experience, right?) then you'll have to limit yourself to games from the last decade (assuming they've even been ported to macOS in the first place) or convince yourself that this year's AAA titles are fully playable as a slideshow.
...and that's assuming your Mac doesn't start thermal-throttling itself too.
Also, you'll also need a very non-Apple mouse: I'm flabbergasted by how even still in 2025 you cannot independently left-click and right-click on Apple's Magic Mouse[1]; while, ergonomically a multitouch mouse is great for many things, but navigating a wheel-driven UI (e.g. weapon-wheels) is not one of them.
[1] https://superuser.com/questions/188431/apples-magic-mouse-an...
Well, Apple doesn't sell 'em with RGB LEDs built-in, so I dunno.
...more seriously though: I don't know how you can say that with a straight-face. On paper, the Apple Silicon M3 and M4 seem comparable to NVIDIA's mid-tier offerings from 3-4 years ago... when rendering to a 1080p-sized display; assuming you'd like to render your games at native Retina or even 5K resolution (given that Apple would really rather you used their display hardware for the best experience, right?) then you'll have to limit yourself to games from the last decade (assuming they've even been ported to macOS in the first place) or convince yourself that this year's AAA titles are fully playable as a slideshow.
...and that's assuming your Mac doesn't start thermal-throttling itself too.
Also, you'll also need a very non-Apple mouse: I'm flabbergasted by how even still in 2025 you cannot independently left-click and right-click on Apple's Magic Mouse[1]; while, ergonomically a multitouch mouse is great for many things, but navigating a wheel-driven UI (e.g. weapon-wheels) is not one of them.
[1] https://superuser.com/questions/188431/apples-magic-mouse-an...
> Well, Apple doesn't sell 'em with RGB LEDs built-in, so I dunno.
now i have a sudden urge to buy a mac mini and install a tiny case window with LEDs and an itty-bitty LCD display for power/thermal monitoring.
now i have a sudden urge to buy a mac mini and install a tiny case window with LEDs and an itty-bitty LCD display for power/thermal monitoring.
I said solid not state of the art :)
if all I can't play is 2025 AAA games..I'm not missing out on much. It ran BG3 solidly anyways! Obviously not maxed out but it was playable and enjoyable.
if all I can't play is 2025 AAA games..I'm not missing out on much. It ran BG3 solidly anyways! Obviously not maxed out but it was playable and enjoyable.
Apple is institutionally incapable of understanding games. It started with Jobs who didn't like and didn't understand video games. and continues with the top brass [1]
Games with app purchases are just a lucky turn of events for Apple because they still don't understand what games are. Hence the "oh, we now have desktop-level graphics on iPhone" or some other drivel they pronounce from time to time at WWDC.
From time to time someone in the company manages to push something forward (see Game Porting Toolkit), but those remain very few and far in between.
[1] To be honest, I doubt any of the top brass even uses computers these days looking at the decisions they make wrt Mac OS.
Games with app purchases are just a lucky turn of events for Apple because they still don't understand what games are. Hence the "oh, we now have desktop-level graphics on iPhone" or some other drivel they pronounce from time to time at WWDC.
From time to time someone in the company manages to push something forward (see Game Porting Toolkit), but those remain very few and far in between.
[1] To be honest, I doubt any of the top brass even uses computers these days looking at the decisions they make wrt Mac OS.
> I doubt any of the top brass even uses computers these days looking at the decisions they make wrt Mac OS.
I had a similar thought about the Microsoft manager who just claimed that in 2030 no one will use a mouse and keyboard anymore and people won't want to be "mousing around". If he actually believes that it says a lot about the way he interacts with computers. And how rarely he uses it outside of a quiet office.
I had a similar thought about the Microsoft manager who just claimed that in 2030 no one will use a mouse and keyboard anymore and people won't want to be "mousing around". If he actually believes that it says a lot about the way he interacts with computers. And how rarely he uses it outside of a quiet office.
> I had a similar thought about the Microsoft manager who just claimed that in 2030 no one will use a mouse and keyboard anymore
That's nothing new: Microsoft still has an institutional obsession with pen-computing (going right back to 1992's "Windows for Pen Computing"); it re-emerges every few years: sometimes it's a major imitative like Windows XP TabletPCs[1], or re-launching OneNote as a "free" Windows feature; or adding "inking" support anywhere it doesn't belong (so if there's one good thing about the invasive MS Copilot awareness campaign: it made me forget about how useless "inking" is and shareholder value pissed away on it.
-----
[1] Speaking from personal experience: I had a Tecra M4 myself, but despite everything: a very high-resolution display, Wacom digitizer and stylus, NVIDIA's best laptop GPU, and the best OS and Office integration yet (the 2005 version of the TabletPC Input Panel in Windows XP is a work of art, honestly) and the launch of a brand new product-line: Office OneNote - but the whole experience was really just still... a noticeable downgrade compared to using a good pen on good lined paper; but especially a significant downgrade from using a mouse and keyboard.
The main reason it was such a disappointment comes down to a small number of intractable problems that probably won't be solved on Windows for a long while still:
1. The time-latency between moving the stylus and the on-screen (hardware scanout sprite!) moving with it.
2. The time-latency between writing with the stylus and the on-screen ink being drawn (which is done in software, through multiple layers of buffers, making it easily 3-5x more laggy than the bufferless hardware cursor sprite.
3. Insufficient display resolution: even with a 125dpi display (compared to the 96dpi most laptops had at the time) of 1400x1050 @ 14 inches, natural handwriting with a pen on paper really needs to be rendered at 300dpi or maybe 600dpi.
4. That awkward gap between the actual LCD display screen and the plastic-y stylus-safe screen covering - this was long before iPad-style laminated displays existed too; which means there's parallax error - making it impossible to take the stylus off the screen and reposition it exactly where you expect: it would always land off-target by 3-5px if you're lucky. This alone kills cursive handwriting because you won't be able to accurately dot-your-Is-and-cross-your-Ts even if you have the best fine motor-control possible.
...and there were other issues too: handwriting recognition remains an evergreen joke going back decades[2]; while my Tecra was better at it than my PocketPC, it was still far short of the MS PDC demos showing a full Letter-sized paper of handwriting transforming into rich-formatted text with zero spelling mistakes. There were plenty of glitches in Windows GDI when you used the screen-rotation feature too (e.g. it disabled double-buffering for most Win32 controls; and everything would awkwardly lock-up for a few seconds after the rotation; iPad OS this surely was not).
(I'm sorry for writing obsessively about this; it's one of my... uh... autistic hangups)
[2] https://www.youtube.com/watch?v=FiorZ4yrbtk
-----
Apple gets a lot of things wrong; but when Apple get something right, the world knows. And what Apple got right was their understanding that pen-computing for text input is just plain unworkable; even on the iPad with Apple Pencil, it's clear they only intend it to be used for tasks like art/drawing or for simple shape-like annotations - neither of which require fine application of the stylus point on-screen. Whereas Microsoft just won't let the dream die; and I've no idea why.
That's nothing new: Microsoft still has an institutional obsession with pen-computing (going right back to 1992's "Windows for Pen Computing"); it re-emerges every few years: sometimes it's a major imitative like Windows XP TabletPCs[1], or re-launching OneNote as a "free" Windows feature; or adding "inking" support anywhere it doesn't belong (so if there's one good thing about the invasive MS Copilot awareness campaign: it made me forget about how useless "inking" is and shareholder value pissed away on it.
-----
[1] Speaking from personal experience: I had a Tecra M4 myself, but despite everything: a very high-resolution display, Wacom digitizer and stylus, NVIDIA's best laptop GPU, and the best OS and Office integration yet (the 2005 version of the TabletPC Input Panel in Windows XP is a work of art, honestly) and the launch of a brand new product-line: Office OneNote - but the whole experience was really just still... a noticeable downgrade compared to using a good pen on good lined paper; but especially a significant downgrade from using a mouse and keyboard.
The main reason it was such a disappointment comes down to a small number of intractable problems that probably won't be solved on Windows for a long while still:
1. The time-latency between moving the stylus and the on-screen (hardware scanout sprite!) moving with it.
2. The time-latency between writing with the stylus and the on-screen ink being drawn (which is done in software, through multiple layers of buffers, making it easily 3-5x more laggy than the bufferless hardware cursor sprite.
3. Insufficient display resolution: even with a 125dpi display (compared to the 96dpi most laptops had at the time) of 1400x1050 @ 14 inches, natural handwriting with a pen on paper really needs to be rendered at 300dpi or maybe 600dpi.
4. That awkward gap between the actual LCD display screen and the plastic-y stylus-safe screen covering - this was long before iPad-style laminated displays existed too; which means there's parallax error - making it impossible to take the stylus off the screen and reposition it exactly where you expect: it would always land off-target by 3-5px if you're lucky. This alone kills cursive handwriting because you won't be able to accurately dot-your-Is-and-cross-your-Ts even if you have the best fine motor-control possible.
...and there were other issues too: handwriting recognition remains an evergreen joke going back decades[2]; while my Tecra was better at it than my PocketPC, it was still far short of the MS PDC demos showing a full Letter-sized paper of handwriting transforming into rich-formatted text with zero spelling mistakes. There were plenty of glitches in Windows GDI when you used the screen-rotation feature too (e.g. it disabled double-buffering for most Win32 controls; and everything would awkwardly lock-up for a few seconds after the rotation; iPad OS this surely was not).
(I'm sorry for writing obsessively about this; it's one of my... uh... autistic hangups)
[2] https://www.youtube.com/watch?v=FiorZ4yrbtk
-----
Apple gets a lot of things wrong; but when Apple get something right, the world knows. And what Apple got right was their understanding that pen-computing for text input is just plain unworkable; even on the iPad with Apple Pencil, it's clear they only intend it to be used for tasks like art/drawing or for simple shape-like annotations - neither of which require fine application of the stylus point on-screen. Whereas Microsoft just won't let the dream die; and I've no idea why.
> "And what Apple got right was their understanding that pen-computing for text input is just plain unworkable; [...]"
Ah, the usual "inking is useless" hyperbolic drivel. Pens worked fine (enough) for me as longtime Wacom EMR user, including for handwriting, e. g. classroom notes, sketching, and the like, especially via dedicated third-party solutions. And, obviously, there's always room for improvement. Just as it's obvious that for that to happen you have to "keep the dream alive".
And Steve "Who needs a stylus" Jobs is, as overrated as he was, a dead businessman, while the stylus is, as underrated a tool, still kicking. Even in the castrated and enshittified pen-computing product line of the company he helped to build.
I do pen computing since it began. Indispensable tool in my fields of work. The most problematic thing? Ultramobile and modular general-purpose computing is an underserved market; penabled UMGPC (or UMPCs) are practically nonexistant. Sad.
Ah, the usual "inking is useless" hyperbolic drivel. Pens worked fine (enough) for me as longtime Wacom EMR user, including for handwriting, e. g. classroom notes, sketching, and the like, especially via dedicated third-party solutions. And, obviously, there's always room for improvement. Just as it's obvious that for that to happen you have to "keep the dream alive".
And Steve "Who needs a stylus" Jobs is, as overrated as he was, a dead businessman, while the stylus is, as underrated a tool, still kicking. Even in the castrated and enshittified pen-computing product line of the company he helped to build.
I do pen computing since it began. Indispensable tool in my fields of work. The most problematic thing? Ultramobile and modular general-purpose computing is an underserved market; penabled UMGPC (or UMPCs) are practically nonexistant. Sad.
I've always thought that the reason they don't care about gaming is because gaming has always been a race-to-the-bottom in margins business. Gamers care a lot about hardware in ways that make selling gaming PCs always very low margin (compared to enterprise or creative) (very few other customers know about RAM or SSD prices, famously Apple's bread-and-butter margin increaser).
Macs were bad for gaming long before the software Apple Store existed.
Steve Jobs was dismissive about gaming, even when PC gaming was on the rise, that's the reason.
Steve Jobs was dismissive about gaming, even when PC gaming was on the rise, that's the reason.
I don’t try to game on my laptop, and I have always thought “gaming laptops” are somewhat akin to “racing-spec BarcaLoungers”. That’s why I’ve never understood why so many people bitch about not being able to game on Macs. If you want to play video games, you should probably buy a console or a desktop PC.
White-hot take: you’re allowed to own a PC and a Mac. They aren’t like matter and antimatter, you won’t collapse the galaxy or anything.
White-hot take: you’re allowed to own a PC and a Mac. They aren’t like matter and antimatter, you won’t collapse the galaxy or anything.
People are complaining because the hardware is capable but there are other reasons may make gaming on a mac an annoyance. Not because macbooks are not powerful enough to run games. And to be fair, macbooks can perfectly run games, and indeed a lot of titles perform great, even if most have to use some sort of compatibility layer (roseta 2, vulkan to metal etc). Why should I get a PC just for gaming if my machine can handle that? Especially something like a big form factor gaming PC that takes quite a bit of space in a room.
And this is not a matter of laptop vs desktop because most of these issues (not the notch) will be present for a mac studio.
In fact apple itself has started advertising gaming in macs in WWDCs last years. So it is only fair that people will complain about it.
But in general gaming in macs is perfectly feasible (maybe not the latest most demanding graphics game at max settings, but most of the stuff). You may miss certain graphics features that may not be available for macs, but otherwise performance is not bad. Even playing windows versions of games through whisky or CrossOver is perfectly feasible.
And this is not a matter of laptop vs desktop because most of these issues (not the notch) will be present for a mac studio.
In fact apple itself has started advertising gaming in macs in WWDCs last years. So it is only fair that people will complain about it.
But in general gaming in macs is perfectly feasible (maybe not the latest most demanding graphics game at max settings, but most of the stuff). You may miss certain graphics features that may not be available for macs, but otherwise performance is not bad. Even playing windows versions of games through whisky or CrossOver is perfectly feasible.
>That’s why I’ve never understood why so many people bitch about not being able to game on Macs.
Well that's where you're wrong then. It's perfectly possible to game on a laptop. Over the last decade with the development of the lightning ecosystem and docks it's become a very low friction endeavor as well.
There are a myriad of quality "gaming" laptops out there, but obviously that's not for everybody, and that's one of many reasons why workstation laptops exist (basically the same thing - ability to run at high loads for extended periods of time - without the gamer aesthetic).
There are many casual gamers out there who don't want to shell out for a dedicated gaming device, nor should they win a laptop is a perfectly adequate device to game on. It's not that hard to comprehend.
Well that's where you're wrong then. It's perfectly possible to game on a laptop. Over the last decade with the development of the lightning ecosystem and docks it's become a very low friction endeavor as well.
There are a myriad of quality "gaming" laptops out there, but obviously that's not for everybody, and that's one of many reasons why workstation laptops exist (basically the same thing - ability to run at high loads for extended periods of time - without the gamer aesthetic).
There are many casual gamers out there who don't want to shell out for a dedicated gaming device, nor should they win a laptop is a perfectly adequate device to game on. It's not that hard to comprehend.
I mostly agree.
> There are a myriad of quality "gaming" laptops out there, but obviously that's not for everybody, and that's one of many reasons why workstation laptops exist (basically the same thing - ability to run at high loads for extended periods of time - without the gamer aesthetic).
For the last few years, I thought 'gaming' was more GPU heavy and 'workstations' were heavier on the CPU and RAM?
Though I wonder how much that has changed recently or will change soon: after all with the rise of (local) AI, perhaps more work will move to the GPU?
> There are a myriad of quality "gaming" laptops out there, but obviously that's not for everybody, and that's one of many reasons why workstation laptops exist (basically the same thing - ability to run at high loads for extended periods of time - without the gamer aesthetic).
For the last few years, I thought 'gaming' was more GPU heavy and 'workstations' were heavier on the CPU and RAM?
Though I wonder how much that has changed recently or will change soon: after all with the rise of (local) AI, perhaps more work will move to the GPU?
> For the last few years, I thought 'gaming' was more GPU heavy and 'workstations' were heavier on the CPU and RAM?
On workstations you can get both. The Dell Precision 7XXX, HP Zbook Fury, and Lenovo P5x/P7x series are the primary high-end notebook workstations, and they are all nearly infinitely configurable with a myriad of CPU, GPU, memory, storage, display, and connectivity options.
I myself have a Precision 7560 from 2021 that has a Xeon W 11955M, and an RTX 3080 Laptop GPU that's roughly between a desktop 3060 and 3070 in performance due to the power limit of 90 W.
Before that I had a Precision 7530 from 2018 that had a Xeon E 2176M.
Both Precisions have 4 DDR4 slots for up to 128 GB, 3 M.2 slots (and an additional one for the WiFi module), and full repair/service manuals online.
On workstations you can get both. The Dell Precision 7XXX, HP Zbook Fury, and Lenovo P5x/P7x series are the primary high-end notebook workstations, and they are all nearly infinitely configurable with a myriad of CPU, GPU, memory, storage, display, and connectivity options.
I myself have a Precision 7560 from 2021 that has a Xeon W 11955M, and an RTX 3080 Laptop GPU that's roughly between a desktop 3060 and 3070 in performance due to the power limit of 90 W.
Before that I had a Precision 7530 from 2018 that had a Xeon E 2176M.
Both Precisions have 4 DDR4 slots for up to 128 GB, 3 M.2 slots (and an additional one for the WiFi module), and full repair/service manuals online.
I think you are correct, although some work stations are possible to be specced with the "big" GPUs found in the gaming laptops. On the "gaming" side, the hulking neon plastic gamer aesthetic somewhat gave way to a new popular class of gaming-laptop that is more sleek, and those machines often have the mid-range GPUs that you'd find in a workstation. It's all fairly blurred now.
> There are a myriad of quality "gaming" laptops out there, but obviously that's not for everybody
If you're talking x86, only if you're okay with hearing loss :)
Or really have no choice. Student who has space/funds for one device and it has to be portable, for example.
If you're talking x86, only if you're okay with hearing loss :)
Or really have no choice. Student who has space/funds for one device and it has to be portable, for example.
Modern Ryzen APUs have completely fixed this. Anything that can run on a steam deck can run just fine on your budget laptop. You can play AAA games at HD resolution and 60fps on sub $1000 laptops. It will even beat an older gaming laptop's battery life while doing it.
> If you want to play video games, you should probably buy a console or a desktop PC.
Push this logic one or two notches further and people should write and build code on desktop only with an e-ink portrait monitor.
Specialization has its place but asking a generic computing device to gracefully handle most applications isn't a big ask IMHO.
They're not running the latest top notch games or anything exotic, it should be fine with no tinkering.
Push this logic one or two notches further and people should write and build code on desktop only with an e-ink portrait monitor.
Specialization has its place but asking a generic computing device to gracefully handle most applications isn't a big ask IMHO.
They're not running the latest top notch games or anything exotic, it should be fine with no tinkering.
Different people have different trade-offs. Some people like the laptop form factor and want to game on it.
Just like people like the hand held form factor of the Nintendo Switch, but it's still entirely fine for them to complain about the system's low specs. Especially when the Steam Deck and the Rog Ally show that you can do better.
Just like people like the hand held form factor of the Nintendo Switch, but it's still entirely fine for them to complain about the system's low specs. Especially when the Steam Deck and the Rog Ally show that you can do better.
Valid and correct take, but I don’t want to own a Mac and a PC. I’d like to be able to run casual games on my MacBook. I don’t game often or heavily enough to warrant purchasing a rig for it.
Not everyone has the extra money or space to spend on another device just to play games from time to time. I don’t even own a TV, I’m not going to get one, plus a console, plus rearrange my living room and get new furniture to house them, to play games occasionally. Nor will I buy an extra expensive, bulky, and noisy desktop machine and monitor, plus (again) rearrange my furniture.
Additionally, laptops are more than capable of playing demanding games these days.
Additionally, laptops are more than capable of playing demanding games these days.
White-hot take: you are allowed to own an outhouse and a urine only toilet. They aren't like matter and antimatter, and so on.
I so glad someone else was saying what I was thinking.
> If you want to play video games, you should probably buy a console or a desktop PC.
> White-hot take: you’re allowed to own a PC and a Mac.
I do own a console, a pc and two macs. But for what I've paid for the macs Apple should make it easy for me to play games on their hardware if i so choose.
There is some hope: Lies of P is actually very playable on the minimum requirements M2/16G ram. And you get the Mac version on Steam with the Windows version so you're not limited to a single platform.
> White-hot take: you’re allowed to own a PC and a Mac.
I do own a console, a pc and two macs. But for what I've paid for the macs Apple should make it easy for me to play games on their hardware if i so choose.
There is some hope: Lies of P is actually very playable on the minimum requirements M2/16G ram. And you get the Mac version on Steam with the Windows version so you're not limited to a single platform.
[deleted]
What? This seems like just games not defaulting to the correct resolution for the display they're on. The first thing I do in every game I play (on any platform) is go through the settings, and make sure the resolution matches the screen's physical resolution. If the game is dumb about it, I choose a smaller multiple or run in windowed mode or on an external display.
> We had a teacher years ago who said something that remains true until today: "everything is about money, especially the ones that appear to have non-monetary reasons."
That's more of an aspiration than a statement of fact.
Eg I'd happily have organised a crowdfunding to give Vladimir Putin a few dozen billion dollars to bribe him away from starting a war. And if you look at Russia's finances that's effectively what happened: he (and even more his oligarchs) predictably lost untold billions in revenue and profit for this war.
Also, migration from poor to rich countries increases workers' pay so much, that you could charge them a hefty sum for the privilege and they would still benefit from coming. However voters by and large don't like it, even if you were to distribute the proceeds amongst them (as a "citizen's dividend" or whatever).
They have non-monetary reasons.
See https://citeseerx.ist.psu.edu/document?repid=rep1&type=pdf&d... for an interesting collection of historical cases drawn from such diverse sources as Apartheid and Post-Apartheid South Africa, Malaysia, Nazi Germany.
That's more of an aspiration than a statement of fact.
Eg I'd happily have organised a crowdfunding to give Vladimir Putin a few dozen billion dollars to bribe him away from starting a war. And if you look at Russia's finances that's effectively what happened: he (and even more his oligarchs) predictably lost untold billions in revenue and profit for this war.
Also, migration from poor to rich countries increases workers' pay so much, that you could charge them a hefty sum for the privilege and they would still benefit from coming. However voters by and large don't like it, even if you were to distribute the proceeds amongst them (as a "citizen's dividend" or whatever).
They have non-monetary reasons.
See https://citeseerx.ist.psu.edu/document?repid=rep1&type=pdf&d... for an interesting collection of historical cases drawn from such diverse sources as Apartheid and Post-Apartheid South Africa, Malaysia, Nazi Germany.
jama211(1)
to be fair there is only so much you can do inside the power envelope of 100W or so
The Xbox Series S only uses about 80w under full load, and that's built on TSMCs old 7nm process. Apple's bleeding edge 3nm silicon should be able to do even more with a similar power envelope.
100W TDP ought to be enough for anyone.
[deleted]
Not really. If you compare it to gaming rigs, they bear radically different architectures, so you can't really compare them by TDP or power requirements. They don't emit the same hear or require the same amount of power per TFLOP. And I wouldn't be surprised if tflops also wouldn't translate to actual compute room for shaders.
Even if they did, 100w should be room enough to play relatively recent titles, specially indie ones. Nothing really excuses Apple from this contempt it has for the gaming market.
Even if they did, 100w should be room enough to play relatively recent titles, specially indie ones. Nothing really excuses Apple from this contempt it has for the gaming market.
> Even if they did, 100w should be room enough to play relatively recent titles
Steamdeck runs on 45W, and that's plenty enough power to have fun.
Steamdeck runs on 45W, and that's plenty enough power to have fun.
I briefly owned a Steam Deck (before returning it), and it seems like most users tone down their expectations a lot compared to PC gaming. 30fps at the Deck’s low resolution seems to be the norm for recent games. Enough power to have fun, sure, but I think people would rightfully pan it if it weren’t Valve.
Expectations are lowered appropriately, I think. There are a number of other handhelds on the market. Of the high end PC handhelds that came out reasonably close to the Steam Deck, they have to trade away a lot of battery life to perform better than the Steam Deck. Valve was clearly optimizing for battery life and I don't think it was a bad choice. The Switch 2 isn't even held back by x86 and it's battery life is still quite painful.
Now, handhelds with newer hardware are definitely going to trounce the steam deck without having to trade away battery life, but I think they did the best they could at the price point and time.
Now, handhelds with newer hardware are definitely going to trounce the steam deck without having to trade away battery life, but I think they did the best they could at the price point and time.
The battery life is nice, but the Steam Deck is huge - big enough that I'd feel incredibly silly pulling one out of my bag on the train - so it's the least I'd expect.
absolutely agreed.
you swallow the taste of the terrible hardware of a steam deck for the support of valve/proton/devs and the ecosystem.
you swallow the taste of the terrible hardware of a steam deck for the support of valve/proton/devs and the ecosystem.
The included charger is 45W but the chip consumes less.
Steam Deck's APU is power limited to 15W
> Nothing really excuses Apple from this contempt it has for the gaming market.
Considering how the typical self-identifying "gamer" conducts themselves online, I think Apple might be on to something...
Considering how the typical self-identifying "gamer" conducts themselves online, I think Apple might be on to something...
What, you mean you aren't champing at the bit to get death threats over a bug in a piece of software for which 70 dollars was paid three years ago?
I have no idea how they behave online. I know however that in 2022 the market size of the gaming industry was over 200 billion in value.
While the differences between ARM and x86 CPUs are quite substantial, Apple's iGPUs follow the same architecture as all the brands
> "everything is about money, especially the ones that appear to have non-monetary reasons."
There are countless other incentives as tangible as money including meaning, status, security, fame, etc.
If you spend time around people with money you will find they will happily trade it to achieve these.
What this belief signals most strongly to me is your class.
There are countless other incentives as tangible as money including meaning, status, security, fame, etc.
If you spend time around people with money you will find they will happily trade it to achieve these.
What this belief signals most strongly to me is your class.
> What this belief signals most strongly to me is your class.
What this "classism" mentality signals is your sense of superiority due to the amount of $ you have in a bank.
What this "classism" mentality signals is your sense of superiority due to the amount of $ you have in a bank.
Class is not money - and you're making non-personal comment a personal one.
> non-personal comment
You literally said "What this belief signals most strongly to me is your class.". So that wasn't personal?
You literally said "What this belief signals most strongly to me is your class.". So that wasn't personal?
No - this is a general statement. People who are saying that everything is about money are revealing they don’t appreciate other motivations.
But how do that relate to their class? The working class desire money just as much as the owning class.
Depending on culture it very much is. Money is a direct signal of status in a way most other things are not as it is correlates to resources which nature selects for.
In the us of a, money is the ultimate status and often used as the measuring stick to the value of ones ideas, personhood, and everything in between.
I cannot stand it but it is what it is.
In the us of a, money is the ultimate status and often used as the measuring stick to the value of ones ideas, personhood, and everything in between.
I cannot stand it but it is what it is.
No, its the way you talk, interests, activities, goals, etc.
Do you remember the TV show duck dynasty where a rural family form the south became millionaries selling sporting goods?
How would you compare their socials status to a Berkeley undergrad with parents who work in the bay?
Do you remember the TV show duck dynasty where a rural family form the south became millionaries selling sporting goods?
How would you compare their socials status to a Berkeley undergrad with parents who work in the bay?
Not mentioned about WoW in here is that they considered the notch enough to also have an option to have the UI avoid the notch. It calls a function in C_UI to get the safe region, and then resizes UIParent to fit within that region while still rendering the game up to the true top of the display.
WoW has always been exceptionally good at treating macOS like a first-class citizen. It's a shame Blizzard has stopped supporting macOS for their newer games.
Back in the day they even implemented near-zero-performance-impact video recording that leveraged AVKit/Quicktime as a Mac-exclusive feature, which was pretty neat. It let me get silky recordings where Windows user guildmates’ videos skipped and stuttered from having to run both WoW and much heavier third party recording software.
Always loved Blizzard games back in the day because I could play with my Mac-owning friends.
Bullshit like this is probably why they sent their developers to farm greener pastures.
If anything it's an example that games can be amazing on macOS, if developers take the time to learn and use the system. WoW on macOS is a far superior experience to WoW on Windows.
By what standard is it superior to WoW on Windows? Starting from the available hardware, the Windows world is far superior for WoW resulting in better visuals and more consistent fps which is a good start of having enjoyable experience.
Also I really can't think of the way Mac's mouse settings in WoW work better than the Windows ones. Scrolling, mouse movement are all having more settings under Windows to customize them compared to the experience on Mac (even with all the tools such as Mos to help with the bad external mouse handling in Mac).
So what exactly is so superior? I play WoW on both platforms and when I have a choice (that is, when playing at my home desktop - on my summer cabin I only have the Mac option) it's always the Windows one I select. It's nice that it works in Mac so I can play everywhere as I only have Mac laptop, but the sometimes weird graphics bugs, worse performance and odd issues with rendering displacing my WAs and other stuff just doesn't inspire confidence in Mac gaming compared to using Windows. And the mouse movement.. ugh.
Also I really can't think of the way Mac's mouse settings in WoW work better than the Windows ones. Scrolling, mouse movement are all having more settings under Windows to customize them compared to the experience on Mac (even with all the tools such as Mos to help with the bad external mouse handling in Mac).
So what exactly is so superior? I play WoW on both platforms and when I have a choice (that is, when playing at my home desktop - on my summer cabin I only have the Mac option) it's always the Windows one I select. It's nice that it works in Mac so I can play everywhere as I only have Mac laptop, but the sometimes weird graphics bugs, worse performance and odd issues with rendering displacing my WAs and other stuff just doesn't inspire confidence in Mac gaming compared to using Windows. And the mouse movement.. ugh.
Heh, I play mmos in a window if i play them.
WoW on Linux with wine used to be a superior experience to WoW on Windows. Because the system didn't lock up for half a minute when I alt-tabbed.
[Haven't played WoW in a long time though, maybe in Windows 10 and up you have an easier time alt-tabbing between heavy 3d apps.]
WoW on Linux with wine used to be a superior experience to WoW on Windows. Because the system didn't lock up for half a minute when I alt-tabbed.
[Haven't played WoW in a long time though, maybe in Windows 10 and up you have an easier time alt-tabbing between heavy 3d apps.]
Borderless window (fullscreen) is now the norm for over a decade, alt-tab is instant in this mode. You’re stuck at whatever resolution you have your desktop but most games now have a render scale option.
How can this be fixed without breaking existing software? Re-ordering the list?
They could do what Windows has done, and build OS code that checks if the running application is a known-legacy game, and lie to the game about various capabilities so that the game runs well and looks good.
Not sure how much of that is still around but it was rampant for many years and likely a key to Windows success in gaming.
Not sure how much of that is still around but it was rampant for many years and likely a key to Windows success in gaming.
> They could do what Windows has done, and build OS code that checks if the running application is a known-legacy game, and lie to the game about various capabilities so that the game runs well and looks good.
Or, even simpler (and AFAIK modern Windows does that too): if the running application doesn't say in its application manifest "I'm a modern application which understands the new things from operating system versions A, B, C and features X, Y, Z", you know it's a legacy application and you can activate the relevant compatibility shims.
Or, even simpler (and AFAIK modern Windows does that too): if the running application doesn't say in its application manifest "I'm a modern application which understands the new things from operating system versions A, B, C and features X, Y, Z", you know it's a legacy application and you can activate the relevant compatibility shims.
They already do that, linked from another comment here: https://developer.apple.com/documentation/bundleresources/in...
They just need to adapt the API to also filter the list of resolutions when the compatibility mode is on.
They just need to adapt the API to also filter the list of resolutions when the compatibility mode is on.
[deleted]
The suggested filtering is just creating a new problem of assuming a 16:10 safe area exists (and external displays or other shapes don't).
Group all resolutions returned that are the same +-5% together and choose the lowest one in the desired bucket.
Group all resolutions returned that are the same +-5% together and choose the lowest one in the desired bucket.
League of Legends in borderless mode renders at the resolution that's set in BetterDisplay instead of the real one which makes it very blurry. In fullscreen it does it correctly so I'm forced to use fullscreen.
Also consider setting NSPrefersDisplaySafeAreaCompatibilityMode and just leave self letterboxing control to a toggle in the settings (with whatever default you prefer).
Meta: the name on HN was "Blurry game rendering on Mac" or something. Now we have the same title as in the article - clickbait-sounding. Why?
Interesting article, but I think the demonstration image isn’t doing its job. Neither side really looks good to me. They both look roughly the same.
Right? If it's vertically squashed, then at least draw the dividing line vertically so we can see a better difference! But yeah, both images seem like a janky rendering of an antialiased circle.
The bottom left side is showing the circle with the artist-created rough texture that it's supposed to have. The top right shows that that edgy-but-sharp texture has been softened by anti-aliased.
Yeah but the difference isn't as stark as one would expect really.
Part of my decided to get the M3 MacBook Pro because I wouldn't be able to game on it so much - I needed something reliable for a Cybersecurity Masters and I knew if I got a powerful windows laptop I would be tempted to play games .
My is a lovely machine for the most part but overheats a lot when gaming, so much so that it worries me. So I don't bother.
My is a lovely machine for the most part but overheats a lot when gaming, so much so that it worries me. So I don't bother.
interesting -- I ran into this recently playing baldur gate 3 and was curious the technical details why. my fix was that I had an external monitor and I just reset the resolution to the external monitor. (by default, though, the monitor was showing up blurry though; with the wrong aspect ratio.)
Baldur's gate 3 groups the resolutions by aspect ratio. I assume it probably queries the resolutions, computes the aspect ratios and then displays them grouped them by it. This results in some weirdness with some weird ratios with huge coprime numerators/denominators but, as long as the right resolution is detected somewhere, you only basically need to do is select the right aspect ration for your screen.
> through NSScreen’s safeAreaInsets
How is vague "safety" is better than a simple descriptive rect_below_notch?
How is vague "safety" is better than a simple descriptive rect_below_notch?
"Safe area" is terminology that has a history of being used with displays: defining the portion of a TV screen where viewers could be reliably expected to be able to see content and on-screen graphics without them getting clipped off by the overscan.
I assume they also wanted to choose something that would still be named appropriately if they had other kinds of notches or things in the future (and that even now it already accounts for, say, the curved corners where things also can't display).
I assume they also wanted to choose something that would still be named appropriately if they had other kinds of notches or things in the future (and that even now it already accounts for, say, the curved corners where things also can't display).
Since "no-one" knows the history, the design go back to prioritizing the basics of comprehension
Loads of people know it as “safe area”, just because you hadn’t heard it before doesn’t mean it’s not an incredibly common term… I was shocked you hadn’t heard of it. It’s consistent across the industry.
I've heard of that term before, just because you don't have an actual argument there is no need to make up ignorance in others and feign your shock.
Also you're also mistaking two different types of knowledge: what the term means and its "TV screen" history. I was explicitly referencing the latter
Are you ok? You’re not making sense my friend.
Safe area can account for things that are not just a notch. It's used across Apple platforms to indicate anything that might need to occupy a dedicated region on the screen: notch on iPhones, home indicator, iPadOS traffic light buttons, menu bar, curved edges of displays, and so on
Your container views can extend the safe areas for their children as well. In our apps, which allow users to run their own custom projects, we increase the safe area for our UI so that users can avoid it in their own rendering
Safe area is a fairly neat and functional API. The unfortunate thing is the older `CGDisplayCopyAllDisplayModes` API is just lumping all resolutions together
Your container views can extend the safe areas for their children as well. In our apps, which allow users to run their own custom projects, we increase the safe area for our UI so that users can avoid it in their own rendering
Safe area is a fairly neat and functional API. The unfortunate thing is the older `CGDisplayCopyAllDisplayModes` API is just lumping all resolutions together
Even then, you can still have something descriptive like unobstructed_area for more general cases. "Safety" is too generic
But also you don't need to degrade Mac dev experience for games to tackle ipads the games will not be developed on, aliases exist
But also you don't need to degrade Mac dev experience for games to tackle ipads the games will not be developed on, aliases exist
How is unobstructed area, a term you just made up, better than safe area, a term that has been standard for decades?
That's obvious: the descriptive term is obvious in what it represents on your screen, so has a low cognitive overload for all the new generations of people learning these APIs.
Encoding bad practices for decades, on the other hand, just reflects the pains of the old generations.
Safe area is an industry wide term for the “safe area to display in”. It means that it’s a high probability of being safe to have important content there, not that it is a safe guarantee.
Your suggestion here and in the responses would be bucking industry standard terminology for content creation.
Your suggestion for unobstructed area is also incorrect because you cannot guarantee it’s unobstructed depending on the display it’s on. Different displays and configurations might have differing levels of overscan causing content to be clipped.
Your suggestion here and in the responses would be bucking industry standard terminology for content creation.
Your suggestion for unobstructed area is also incorrect because you cannot guarantee it’s unobstructed depending on the display it’s on. Different displays and configurations might have differing levels of overscan causing content to be clipped.
Of course it's correct, even Apple says so only using a different synonym unobscured
https://developer.apple.com/documentation/appkit/nsscreen/sa...
> The distances from the screen’s edges at which content isn’t obscured.
> because you cannot guarantee
That's a condition you've added without justification. Nothing in the term requires it. The term's core benefit is that it's more clarity. Nothing more (in terms of extra guarantees), but nothing less.
But also, you can guarantee, read the API docs again:
> Content in the safe area is guaranteed to be unobscured
Like,
> “safe area to display in”.
So it's not a "safe area", it's a "potentially a safe area"
> bucking industry standard terminology
yes, bad standards should be bucked, preferably before they become standards, but the next best time is immediately after that or any time later.
> The distances from the screen’s edges at which content isn’t obscured.
> because you cannot guarantee
That's a condition you've added without justification. Nothing in the term requires it. The term's core benefit is that it's more clarity. Nothing more (in terms of extra guarantees), but nothing less.
But also, you can guarantee, read the API docs again:
> Content in the safe area is guaranteed to be unobscured
Like,
> “safe area to display in”.
So it's not a "safe area", it's a "potentially a safe area"
> bucking industry standard terminology
yes, bad standards should be bucked, preferably before they become standards, but the next best time is immediately after that or any time later.
It’s not a bad standard just because you personally struggle to understand it. Lots of things have historical names, especially in computer graphics, that are now standard.
What is an absolute safe area or an unobstructed area in video then to you? How do you guarantee such a thing?
Please define one as such that accounts for all display types with appropriate verbiage. I’ll personally advocate for it in the film industry if you can come up with a term that is better than what the entirety of cinematic history has been able to think of.
Apple only claim that it’s unobstructed by their specific display edges and overlays but it doesn’t account for other display concerns. Hence safe area is still the most intuitive name.
Would you also like to go and argue with people about alpha channels?
What is an absolute safe area or an unobstructed area in video then to you? How do you guarantee such a thing?
Please define one as such that accounts for all display types with appropriate verbiage. I’ll personally advocate for it in the film industry if you can come up with a term that is better than what the entirety of cinematic history has been able to think of.
Apple only claim that it’s unobstructed by their specific display edges and overlays but it doesn’t account for other display concerns. Hence safe area is still the most intuitive name.
Would you also like to go and argue with people about alpha channels?
> It’s not a bad standard just because you personally struggle to understand it.
I'm not as bad at this as you are, I've explained why it's bad several times without a reference to my understanding, but you fail to understand that primitive explanation, so now think others also can't.
> Lots of things have historical names, especially in computer graphics, that are now standard.
So? Lots of things also change. You forgot to finish your thought.
> How do you guarantee such a thing?
I don't, I use an API that does
> Please define one as such that accounts for all display types with appropriate verbiage.
Your favorite term doesn't do that.
> I’ll personally advocate for it in the film industry if you can come up with a term that is better than what the entirety of cinematic history has been able to think of.
Oh no, that's a recipe for disaster, please stick to worshipping historic standards, don't ruin a tiny chance of progress!
> Apple only claim that it’s unobstructed by their specific display edges and overlays but it doesn’t account for other display concerns. Hence safe area is still the most intuitive name.
Apple only claim that unobstructed API is unobstructed by their specific display edges and overlays but it doesn’t account for other display concerns. Hence unobstructed area is still the most intuitive name because it still is the closest to the reality, and because "safe" is still not safe, so offers no benefit.
> Would you also like to go and argue with people about alpha channels?
What, are they sacred?
I'm not as bad at this as you are, I've explained why it's bad several times without a reference to my understanding, but you fail to understand that primitive explanation, so now think others also can't.
> Lots of things have historical names, especially in computer graphics, that are now standard.
So? Lots of things also change. You forgot to finish your thought.
> How do you guarantee such a thing?
I don't, I use an API that does
> Please define one as such that accounts for all display types with appropriate verbiage.
Your favorite term doesn't do that.
> I’ll personally advocate for it in the film industry if you can come up with a term that is better than what the entirety of cinematic history has been able to think of.
Oh no, that's a recipe for disaster, please stick to worshipping historic standards, don't ruin a tiny chance of progress!
> Apple only claim that it’s unobstructed by their specific display edges and overlays but it doesn’t account for other display concerns. Hence safe area is still the most intuitive name.
Apple only claim that unobstructed API is unobstructed by their specific display edges and overlays but it doesn’t account for other display concerns. Hence unobstructed area is still the most intuitive name because it still is the closest to the reality, and because "safe" is still not safe, so offers no benefit.
> Would you also like to go and argue with people about alpha channels?
What, are they sacred?
They’re not sacred but changing them gives a much lower payoff than the pain of changing.
None of your suggestions actually improve the situation. They’d just not scale the way you think they would to other display types when you query the safe area.
For example, Apple specifically calls out why they use the safe area term to correspond to different display types
> In tvOS, the safe area also includes the screen’s overscan insets, which represent the area covered by the screen’s bezel.
Unobstructed is longer, and provides no extra information of value. Go work in a visual industry and see how long before you get tired of saying title unobstructed and action unobstructed.
Again, you’re coming at this form the perspective of a lay person in the realm of displays and getting angered that the term isn’t immediately intuitive to you personally, rather than the entire industry that has a standard term that they use and have for many decades.
None of your suggestions actually improve the situation. They’d just not scale the way you think they would to other display types when you query the safe area.
For example, Apple specifically calls out why they use the safe area term to correspond to different display types
> In tvOS, the safe area also includes the screen’s overscan insets, which represent the area covered by the screen’s bezel.
Unobstructed is longer, and provides no extra information of value. Go work in a visual industry and see how long before you get tired of saying title unobstructed and action unobstructed.
Again, you’re coming at this form the perspective of a lay person in the realm of displays and getting angered that the term isn’t immediately intuitive to you personally, rather than the entire industry that has a standard term that they use and have for many decades.
I’m disappointed none of the proposed fixes are for CGDisplayCopyAllDisplayModes to have the “first” option on the list be the BEST option, taking into account the notch. The author hinted that many games pick the first option, so rather than demanding all those publishers add new code, Apple could make the easy path the happy path.
In typical Apple fashion, they have ignored the feedback for several years. Nice work, Apple!
> The problem with Apple laptops is they have a notch at the top of the display
Well, yes.
Well, yes.
When I was into pixel art games and 8 bit emulation, this caused me to stick with the MacBook Air instead of the Pro, because it had the traditional 1440x900 screen without funky scaling.
[deleted]
Most of the complains in TFA and the bandwagon here just seem to be lazy/stubborn developers not bothering to understand the platform they're porting to.
There's a kind of entitlement among developers coming from PC/Windows expecting Apple to give them everything on a silver plate, yet they gladly bend over when porting to consoles without a peep.
I mean yeah Apple documentation sucks ass sometimes but sheesh you know the notch is fucking there, you have to account for it. You gotta do some specific shit for PS/XBox/Switch too, can't always just expect a one-click port (yet). Hell, there isn't even any public/3rd-party documentation or articles or YouTube tutorials for consoles but you don't see anyone bitching about that.
There's a kind of entitlement among developers coming from PC/Windows expecting Apple to give them everything on a silver plate, yet they gladly bend over when porting to consoles without a peep.
I mean yeah Apple documentation sucks ass sometimes but sheesh you know the notch is fucking there, you have to account for it. You gotta do some specific shit for PS/XBox/Switch too, can't always just expect a one-click port (yet). Hell, there isn't even any public/3rd-party documentation or articles or YouTube tutorials for consoles but you don't see anyone bitching about that.
It’s a good thing that most people don’t buy Macs for gaming, as they suck compared to any other platform. Anyone who expects a good experience is fooling themselves as they won’t get it! If you want to experience games as the developer intends, don’t play ports that use compatibility layers, just buy a console and play natively!
> If you want to experience games as the developer intends, don’t play ports that use compatibility layers
A few months ago I would have assumed you're correct.
But recently I've played some games on my laptop with Lutris on Ubuntu which uses Wine or Proton under the hood.
The performance and stability is excellent. Although I haven't done any testing, subjectively it feels superior or at least equal to Windows. I've played several intense titles which are pushing my laptop's GPU (Nvidia 3070m) to it's limit, most recently the new Indiana Jones game (which is excellent FYI).
A few months ago I would have assumed you're correct.
But recently I've played some games on my laptop with Lutris on Ubuntu which uses Wine or Proton under the hood.
The performance and stability is excellent. Although I haven't done any testing, subjectively it feels superior or at least equal to Windows. I've played several intense titles which are pushing my laptop's GPU (Nvidia 3070m) to it's limit, most recently the new Indiana Jones game (which is excellent FYI).
It depends on the game, the distro, the version of the game, the kernel and the windowing system as to how well it performs. I am using Debian and while a lot of games work well, some games are an absolute PITA to setup properly.
It is easier for me to reboot into Windows.
It is easier for me to reboot into Windows.
The Steam Deck runs games on a compatibility layer (Wine) and it’s an excellent console.
I’m pretty sure that if a developer releases their game on macOS, it plays, by definition, as the developer intended.
I have both a powerful gaming PC with Windows and all that, and a PS5, but some games I just like on my MacBook.
I have both a powerful gaming PC with Windows and all that, and a PS5, but some games I just like on my MacBook.
A lot of games are ported to Mac / Linux by a third party. The quality of that port is dependant on the company and the budget for porting it. If I was a game developers I would never do a Mac port.
Hmm I just realized something. The article author seems to be unaware that Apple makes desktops too, and laptops can be connected to external monitors, and thus not every game will be played on something with a notch.
Notches are dumb as shit. Eg. when making a cross platform mobile app, you just have to leave a portion of the screen at the top completely empty. Cus various different phones could have a notch or a front facing camera in any position up there.
On mobile where screen real estate is tight we just have to give up a really important fraction of the screen because of this madness of non rectalinear screens.
It's kinda funny that an article complaining about blurry rendering, is written using one of the most illegible fonts I've ever seen.
The notch is such a wildly stupid idea I can't even begin with it. I actually kinda liked the direction they were going with the keyboard Touch Bar... but they killed that.
What's the alternative? A camera on top of the screen? Fragile, unless you could fold it away. Which would be another point of failure.
Might be unthinkable to some, but an alternative could also be to have NO camera. People already have a phone with one if they really need it.
The alternative is what literally every other laptop does and just has a rectangular screen. Put the camera outside please and thank you.
iPhones have the same problem. Ever played a fullscreen game and had part of the UI cut off into the notch or island. Yep, it's a problem.
iPhones have the same problem. Ever played a fullscreen game and had part of the UI cut off into the notch or island. Yep, it's a problem.
The idea is that you should consider the area around the notch to be extra, and not part of the normal screen. Show your game on the rectangular part of the screen, and use the extras for stuff that doesn't need the whole screen, like time, date, notification count, menu, whatever.
Having just the rectangular screen means not having the option of making those things visible, or having a smaller screen.
Having just the rectangular screen means not having the option of making those things visible, or having a smaller screen.
A bezel would be far preferable to a notch.
Why? Unless I am running a full screen app the notch gives me more screen space. Remember that the mac have the menu bar on top of the screen at all times so the space is not available for normal windowed apps.
I hide my menubar by default. I like using my space for stuff I'm actively looking at.
I was watching someone code in vim on a new mac the other day and the notch covered part of the first like of their editor! Like how does this not completely break you as a human. Maybe I'm a little OCD idk.
Isn't there just like an option to change the resolution and fix this? Apple should really have a "disable notch" mode.
I was watching someone code in vim on a new mac the other day and the notch covered part of the first like of their editor! Like how does this not completely break you as a human. Maybe I'm a little OCD idk.
Isn't there just like an option to change the resolution and fix this? Apple should really have a "disable notch" mode.
No it wouldn’t be
The notch grants more usable vertical physical pixels than you'd have otherwise, with the only "downside" being a small unusable area in the center where the camera/mic/other sensors are placed.
I put "downside" in quotes because the alternative is just not having those vertical pixels at all, and having the screen end below the sensors.
I put "downside" in quotes because the alternative is just not having those vertical pixels at all, and having the screen end below the sensors.
The problem is, by granting more vertical space in such a way that requires additional application logic to avoid overlaps, you've taken a sacred abstraction (the rectangular screen) and shattered it.
Most applications do not handle this well, and I'm willing to bet that will continue to be the case for the foreseeable future.
I can see the allure. If you're a default macOS user with the menu bar not set to slide up when not in use, that space nicely fits. Problem still remains for fullscreen apps though.
And it's not even really a hardware problem. Apple could fix this in software. Just make using the unsafe region an opt-in for developers instead of the default. You want to paint in the unsafe region, call NSAllowUnsafeRegionResolution(). Boom done. By default, when the menu bar isn't shown, expose a rectangle to the viewport.
Most applications do not handle this well, and I'm willing to bet that will continue to be the case for the foreseeable future.
I can see the allure. If you're a default macOS user with the menu bar not set to slide up when not in use, that space nicely fits. Problem still remains for fullscreen apps though.
And it's not even really a hardware problem. Apple could fix this in software. Just make using the unsafe region an opt-in for developers instead of the default. You want to paint in the unsafe region, call NSAllowUnsafeRegionResolution(). Boom done. By default, when the menu bar isn't shown, expose a rectangle to the viewport.
> with the only "downside" being a small unusable area in the center where the camera/mic/other sensors are placed.
The notch is wider than need be. As far as I can tell the main reason is aesthetics. But I agree, it is better than nothing
Notch: Camera, ambient light sensor, and a camera status LED
Dynamic island: camera, infrared camera and flood illuminator, proximity sensor, and an ambient light sensor... also half the width and height
The notch is wider than need be. As far as I can tell the main reason is aesthetics. But I agree, it is better than nothing
Notch: Camera, ambient light sensor, and a camera status LED
Dynamic island: camera, infrared camera and flood illuminator, proximity sensor, and an ambient light sensor... also half the width and height
No it's not
Not knowing much about Macs, I would have thought games were supposed to render full screen around the notch for immersion but respect the safe area for UI and gameplay. Are they supposed to leave a menu bar on macOS?
> Control gets around the issue by just making up its own resolutions.
That's hilarious, I wonder if they had trouble enumerating resolutions and gave up or if they simply couldn't bother.