ChatGPT The comments on the Hacker News post about web apps on macOS Sonoma 14 Beta are generally mixed. Some users express excitement about the development, while others voice concerns about potential abuse and the nature of web notifications.
Positive Sentiment One user named "jessmartin" expressed great excitement about Safari Progressive Web Apps (PWAs) on macOS, calling it "a very good start." They appreciated the fact that credentials in cookies are copied over, links are handled in-app or in the default browser based on their origin, and that web apps run independently of Safari.
The post appears to be a discussion about transitions between two Document Object Model (DOM) states. The main sentiment appears to be mixed, with several themes emerging:
Explanation and Clarification: Some users seek to clarify the functionality of the new feature, explaining that it allows for transitions between two DOM states without needing to keep something in the DOM during an animation. There's also a discussion about whether or not this approach is typical of native platform view transitions, with some disagreement over its implementation in iOS and MacOS.
Based on the Hacker News thread you provided, here is a summary of the discussion surrounding the new installation pop-up for Progressive Web Apps (PWAs) on Chrome:
The distinction between a Chrome app and a webpage is very minimal, leading to questions about the value of this new feature. Some users wonder why there's a need for a screenshot of the app/webpage already in use Some users suggest this pop-up could be useful for non-technical users, and for avoiding the use of Electron.
The discussion on Hacker News revolves around the implementation of memory management in Photoshop, especially when dealing with large files. The article in question is not accessible, but we can piece together some insights from the comments.
One contributor states that Adobe has been solving this problem for a long time by using the filesystem smartly. For web applications, Chrome provides a filesystem for them to use, allowing them to use the same essential solution that the native app would use
The discussion on the new Popover API introduced by Chrome revolves around various aspects, including functionality, usability, and the impact on the user experience.
Introduction of the Popover API: The new Popover API is seen by some as a reinvention of native popups, which were successfully blocked a decade and a half ago. There's a concern that new blockers will need to be developed to handle these popovers, which could potentially be used for intrusive advertising or annoying prompts like "subscribe to my newsletter" or "5% off now" popovers Blocking the Popovers: Some participants argue that the new Popover API could actually make blocking easier.
