6 ms·

The interesting part, for anyone who actually reads the article - the change was fixed in an RC and then reverted in the final release. Which implies there was

The interesting part, for anyone who actually reads the article - the change was fixed in an RC and then reverted in the final release. Which implies there was some regression, some issue, some incorrect behavior or negative impact. One has to wonder… what could it have been? What could the issue with having a more accurate clickbox for the corner of the window possibly be?

anematode 7mo ago
Maybe it was just an oversight in the merge process? e.g. the diff was applied only to the RC and not to the release branch? idk
cardanome 7mo ago
The AI reverted the change and no one does proper code reviews anymore so it went into prod.
- adithyassekhar 7mo ago
  Nah then it won't show up in the known issues section. I hope.
GuB-42 7mo ago
It can be some technical detail. For example: imagine you have 2 windows, the lower right corner of one window almost touching the upper right corner of the other, so that the bounding rectangles overlap but the graphics don't. With the inaccurate "false square" corners, you just had to check the bounding rectangles, to know which window to resize, now you have to check the actual graphics (or more likely, a mask). I am not saying it is the problem, but that's the kind of thing that can happen. Or it may be a simple bug, like a crash, memory corruption, an unhandled exception, the usual stuff, but they couldn't fix it in time and it is better to revert instead of leaving the buggy code or pushing an untested fix.
- blindriver 7mo ago
  Just revert the code back to pre-26! This is ridiculous, it can't possibly be this hard and if it is, it just points to the degradation in the quality of Apple software! This is maddening!
  - igregoryca 7mo ago
    This is already the pre-26 bounding box, isn't it? It's the new graphics that don't line up. (Not a great excuse, but the graphics are here to stay at least for a little while.)
    - reddalo 7mo ago
      > the graphics are here to stay at least for a little while And that's the reason why I won't buy a new Mac. Tahoe and Liquid Glass are so horrible that they're going to lose customers because of those. They should realize what they did and just backtrack: it wouldn't be the first time they admit they made a mistake [1]. [1] https://www.theverge.com/2020/5/4/21246223/macbook-keyboard-butterfly-magic-pro-apple-design https://www.theverge.com/2020/5/4/21246223/macbook-keyboard-...
      - rezonant 7mo ago
        Still waiting on admission that the magic mouse was a mistake though
        GuB-42 7mo ago
        The magic mouse have been there, almost unchanged, since 2009. That is a lot for a tech product, and retiring a product after 16 years is not admitting to a mistake. For example, the Logitech G5 mouse and its direct evolutions were among the most successful Logitech products, and it didn't last that long. No, it is not just refusing to admit that the magic mouse was a mistake, it is considering that it is the best ever. That USB port on the underside is still one of the great mysteries though, maybe it is some quirk of evolution, because it is certainly not intelligent design.
jlaternman 7mo ago
macOS does have weirdness with windows that span multiple screens. I bet some of that kicked in to an unacceptable level. It can create incoherent moving/snapping, for example. Has been kind of crazy-making for a while, for my set-up where screens are not joined but adjacent in a triangular configuration.
- iainmerrick 7mo ago
  Yeah, that's something that was unambiguously better back in the "Classic MacOS" days (probably starting with the Mac II). Windows could overlap multiple screens and they were always drawn correctly. At some point in OS X in the switch to hardware acceleration, they started rendering windows on one screen only. I get that you hardly ever really want a window spanning two screens, but when you accidentally misplace a window it would be handy to be able to see it on each overlapping screen so you can track it down. Right now you can put a few pixels of the title bar on the wrong screen, and the rest of the window just vanishes. These regressions are weird given that modern hardware is vastly more powerful than a Mac II.
  - timw4mail 7mo ago
    I'm pretty sure screen-spanning was better before "fullscreen"...In Lion, I think?
radley 7mo ago
Most likely (and natural): they tested it publically and the response wasn't positive, so they held it back until they could do it better.
msephton 7mo ago
I think it shows how difficult it is to ship a seemingly easy thing inside the Apple machine. I'm more interested in how or why this bug was approved up be worked on so quickly after it was surfaced, rather than other longstanding and arguably more impactful bugs.
- StilesCrisis 7mo ago
  It's because the bug got publicity. Apple marketing prioritizes what does and doesn't get built. Someone saw bad publicity on the front page of HN and requested a fix.
  - 1over137 7mo ago
    Exactly. It got a lot of publicity, even inside Apple.
- nozzlegear 7mo ago
  The answer is probably a ho-hum combination of different teams work on different issues, and this one having annoyed one of the devs who could work on it.
deleted 7mo ago
[deleted]
lobochrome 7mo ago
Or it was just a botched git op
galad87 7mo ago
It broke some NSWindow styles: https://developer.apple.com/forums/thread/814798 https://developer.apple.com/forums/thread/814798
- hbn 7mo ago
  The sad part is we all know the real solution is to just UNDO THE DAMN FISHER PRICE ROUNDING NO ONE CARED THAT THE WINDOW CORNER RADIUS DIDN'T MATCH AN IPAD, IT DOESN'T NEED TO
  - 1over137 7mo ago
    It's because touch screens are coming to MacBooks.
pdhborges 7mo ago
Maybe they reverted it because they are already planning to get rid of the super rounded corners!

anematode 7mo ago

Maybe it was just an oversight in the merge process? e.g. the diff was applied only to the RC and not to the release branch? idk

cardanome 7mo ago

The AI reverted the change and no one does proper code reviews anymore so it went into prod.

adithyassekhar 7mo ago
Nah then it won't show up in the known issues section. I hope.

GuB-42 7mo ago

It can be some technical detail. For example: imagine you have 2 windows, the lower right corner of one window almost touching the upper right corner of the other, so that the bounding rectangles overlap but the graphics don't. With the inaccurate "false square" corners, you just had to check the bounding rectangles, to know which window to resize, now you have to check the actual graphics (or more likely, a mask). I am not saying it is the problem, but that's the kind of thing that can happen. Or it may be a simple bug, like a crash, memory corruption, an unhandled exception, the usual stuff, but they couldn't fix it in time and it is better to revert instead of leaving the buggy code or pushing an untested fix.

blindriver 7mo ago
Just revert the code back to pre-26! This is ridiculous, it can't possibly be this hard and if it is, it just points to the degradation in the quality of Apple software! This is maddening!
- igregoryca 7mo ago
  This is already the pre-26 bounding box, isn't it? It's the new graphics that don't line up. (Not a great excuse, but the graphics are here to stay at least for a little while.)
  - reddalo 7mo ago
    > the graphics are here to stay at least for a little while And that's the reason why I won't buy a new Mac. Tahoe and Liquid Glass are so horrible that they're going to lose customers because of those. They should realize what they did and just backtrack: it wouldn't be the first time they admit they made a mistake [1]. [1] https://www.theverge.com/2020/5/4/21246223/macbook-keyboard-butterfly-magic-pro-apple-design https://www.theverge.com/2020/5/4/21246223/macbook-keyboard-...
    - rezonant 7mo ago
      Still waiting on admission that the magic mouse was a mistake though
      - GuB-42 7mo ago
        The magic mouse have been there, almost unchanged, since 2009. That is a lot for a tech product, and retiring a product after 16 years is not admitting to a mistake. For example, the Logitech G5 mouse and its direct evolutions were among the most successful Logitech products, and it didn't last that long. No, it is not just refusing to admit that the magic mouse was a mistake, it is considering that it is the best ever. That USB port on the underside is still one of the great mysteries though, maybe it is some quirk of evolution, because it is certainly not intelligent design.

jlaternman 7mo ago

macOS does have weirdness with windows that span multiple screens. I bet some of that kicked in to an unacceptable level. It can create incoherent moving/snapping, for example. Has been kind of crazy-making for a while, for my set-up where screens are not joined but adjacent in a triangular configuration.

iainmerrick 7mo ago
Yeah, that's something that was unambiguously better back in the "Classic MacOS" days (probably starting with the Mac II). Windows could overlap multiple screens and they were always drawn correctly. At some point in OS X in the switch to hardware acceleration, they started rendering windows on one screen only. I get that you hardly ever really want a window spanning two screens, but when you accidentally misplace a window it would be handy to be able to see it on each overlapping screen so you can track it down. Right now you can put a few pixels of the title bar on the wrong screen, and the rest of the window just vanishes. These regressions are weird given that modern hardware is vastly more powerful than a Mac II.
- timw4mail 7mo ago
  I'm pretty sure screen-spanning was better before "fullscreen"...In Lion, I think?

radley 7mo ago

Most likely (and natural): they tested it publically and the response wasn't positive, so they held it back until they could do it better.

msephton 7mo ago

I think it shows how difficult it is to ship a seemingly easy thing inside the Apple machine. I'm more interested in how or why this bug was approved up be worked on so quickly after it was surfaced, rather than other longstanding and arguably more impactful bugs.

StilesCrisis 7mo ago
It's because the bug got publicity. Apple marketing prioritizes what does and doesn't get built. Someone saw bad publicity on the front page of HN and requested a fix.
- 1over137 7mo ago
  Exactly. It got a lot of publicity, even inside Apple.
nozzlegear 7mo ago
The answer is probably a ho-hum combination of different teams work on different issues, and this one having annoyed one of the devs who could work on it.

deleted 7mo ago

[deleted]

lobochrome 7mo ago

Or it was just a botched git op

galad87 7mo ago

It broke some NSWindow styles: https://developer.apple.com/forums/thread/814798 https://developer.apple.com/forums/thread/814798

hbn 7mo ago
The sad part is we all know the real solution is to just UNDO THE DAMN FISHER PRICE ROUNDING NO ONE CARED THAT THE WINDOW CORNER RADIUS DIDN'T MATCH AN IPAD, IT DOESN'T NEED TO
- 1over137 7mo ago
  It's because touch screens are coming to MacBooks.

pdhborges 7mo ago

Maybe they reverted it because they are already planning to get rid of the super rounded corners!