I don't know, there are definitely some rough edges (particularly with the menu bar for some reason - big rewrite there?), but overall I'm quite happy with Golden Gate. "Buggy mess" is some serious hyperbole.
Of the issues they report:
- The centering bugs seem... not very important.
- The Mac User Guide looks fine to me. Shows "for macOS 27."
- Network app?
- Why are you looking at the Mission Control app icon at 20x zoom? And in any case, doesn't it seem reasonable to simplify the traffic light design to a flat circle for an icon that will be displayed very small 99.9% of the time?
- Firefox bugs are bugs in Firefox. (I also keep experiencing the stuck menu bug, but again, Firefox bug.)
- "You can find references to NeXTSTEP, the ancestor of macOS, in its UI!" No, that's not what that means.
- "I have a folder open in the Dock. If I click on another folder, shouldn't that then open?" Yes, and it does.
NS hasn't had anything to do with NeXTSTEP since, well, NeXTSTEP. The author's wording makes it sound like this is some crazy remnant of forgotten 30-year-old code poking through, but it's really not. It's Swift (most likely) string concatenation being passed a view instance instead of a string by mistake.
rafram · · focus · HN ↗
Of the issues they report:
- The centering bugs seem... not very important.
- The Mac User Guide looks fine to me. Shows "for macOS 27."
- Network app?
- Why are you looking at the Mission Control app icon at 20x zoom? And in any case, doesn't it seem reasonable to simplify the traffic light design to a flat circle for an icon that will be displayed very small 99.9% of the time?
- Firefox bugs are bugs in Firefox. (I also keep experiencing the stuck menu bug, but again, Firefox bug.)
- "You can find references to NeXTSTEP, the ancestor of macOS, in its UI!" No, that's not what that means.
- "I have a folder open in the Dock. If I click on another folder, shouldn't that then open?" Yes, and it does.
- The rest, sure.
alanbernstein · · focus · HN ↗
rafram · · focus · HN ↗
NS hasn't had anything to do with NeXTSTEP since, well, NeXTSTEP. The author's wording makes it sound like this is some crazy remnant of forgotten 30-year-old code poking through, but it's really not. It's Swift (most likely) string concatenation being passed a view instance instead of a string by mistake.
alanbernstein · · focus · HN ↗