5 ms·

Apple is gonna do what apple wants.

by deadbunny 22d ago

cute_boi 22d ago
[flagged]
- arkon_hn 22d ago
  Not to mention how updates are tied to OS updates...
  - tengwar2 22d ago
    Hasn't been the case for some time.
    - spartanatreyu 22d ago
      Not true. MacOS releases a new version each year, the current MacOS landscape looks like: - MacOS Sequoia (previous version, everything works as expected) - MacOS Tahoe (current version, broken experience, basically Apple's "Windows Vista/8 moment") - MacOS Golden Gate (next version, fixes what was broken in Tahoe, comes out in a month) I'm on MacOS Sequoia because I have things that can't be broken by updating to Tahoe. I also cannot test how my websites/webapps will work in a month, because Safari's beta (called Safari Technology Preview) only works on Tahoe and Golden Gate. I cannot wait a month to update to Golden Gate because Golden Gate drops support for my iMac. And I can't test the new version of Safari on my Windows or Linux devices because Safari isn't available for them. I can test the Webkit browser, but that doesn't include the Safari specific changes that apple makes which I need to be able to test. --- So, I can't test Safari until I wait a month and purchase a new apple machine. (Oh by the way, apple keeps cancelling orders for new machines)
      - alwillis 22d ago
        > And I can't test the new version of Safari on my Windows or Linux devices because Safari isn't available for them. You can download three Linux-compatible WebKit-based browsers from Apple's WebKit page: Epiphany Technology Preview: https://webkitgtk.org/epiphany-tech-preview https://webkitgtk.org/epiphany-tech-preview WPE: http://wpewebkit.org/download http://wpewebkit.org/download WebKitGTK: http://webkitgtk.org/download http://webkitgtk.org/download
        tosti 21d ago
        There are subtle differences. From the top of my head, differences with osx include the font rendering and the tab order (which is broken for everything except form elements).
        alwillis 21d ago
        I get it; when Safari was available for Windows, the font rendering was different from the Mac version.
  - dlahoda 22d ago
    What Updates tied? App Store updates use same networking and storage as OS? Why it is bad?
    - deleted 22d ago
      [deleted]
    - flyingjoe 21d ago
      because updating a single app via the app store is faster than updating the whole OS. Having a security vulnerability in a browser could be fixed immediately, but having to ship out a whole new OS leaves it open for a while. Especially with users generally being against/too lazy to do OS updates
      - arkon_hn 21d ago
        Exactly this. We so often see people still using iOS versions from ~4 years ago despite having options to update. Apple holds the ecosystem back.
      - kekdkrjfjjwfj 21d ago
        Except that they can and have pushed security updates that are not necessarily OS updates. Granted the process is still through the settings app, but the point still stands. They have a channel for pushing yellow and red alert updates. Anything else can easily wait a couple of months.
  - Unai 21d ago
    A non-evergreen browser in 2026 should be publicly ridiculed any time its name is brought up.
    - account42 21d ago
      Web developers who think you need the latest and greatest features to build a hypertext document are the ones who should be ridiculed.
      - Unai 21d ago
        Thankfully, people with ridiculous opinions ridicule themselves. Like pretending the web is just documents, as if we were living three decades ago. Or pretending that "latest and greatest features" is the only reason to keep a browser updated. Or pretending that new features are somehow bad or not useful. Or defending poor Apple for wanting people to spend a grand on new hardware to update be able to update their browser.
- nchmy 22d ago
  [flagged]
  - chuckadams 22d ago
    Maybe because they don't want to see this thread dragged down into an open-ended gripe-fest against Apple, especially when it's concerning a feature Apple did ship before everyone else.
- dlahoda 22d ago
  My wife, son and me not using Safari. Do not see how Safari relates to App Store. We use App Store.
  - SR2Z 22d ago
    The point of a PWA is that instead of downloading an actual binary app, you essentially get a webpage that runs like it was an app. They can be installed from anywhere and are safe by nature because they're really just webpages. That was the original conception of iPhone apps, until Steve Jobs realized just how much money could be made from the app store. Now you get to pay Apple a 30% cut for the privilege of installing software on your own device!
    - kekdkrjfjjwfj 21d ago
      > Now you get to pay Apple a 30% cut for the privilege of installing software on your own device! Kneejerk reactions everywhere! Wow. And to think HN commenters like to think themselves superior to other reddit/instagram/linkedin/social media users.
      - SR2Z 20d ago
        Am I wrong? Was Apple's cut not 30%? Did it not generate a quarter of their revenue last year, over a hundred billion dollars? I have an iPad. I don't need nannying from a trillion-dollar corporation to use my device and yet that's what I get - every excuse Apple makes (security, consistency, whatever) are obviously possible without the level of locked-down their devices are.
llm_nerd 22d ago
What a funny tangent to go off on. JXL was dead. Apple is who brought it back to life[1], and the only reason Chrome resurrected JXL, and now Firefox followed their path, is because Apple pushed JXL support to a billion plus devices. I know people like complaining about Apple, but there's a "read the room" kind of moment where people just seem to either not know the context or are just knee jerking. [1] Worth noting that Apple used the reference implementation, libjxl, and that project still remains the reference implementation with the Rust port being experimental (and of course Apple deployed JXL support over a year before the Rust port even existed). Maybe they'll switch to it at some point, but it's a bit premature to complain about.
- deadbunny 22d ago
  [flagged]
  - concinds 22d ago
    I don't see what this has to do with the topic, sorry.
    - wongarsu 22d ago
      Their point is that Apple is the Nintendo of computing. They don't care what others do, they just do their own thing. Which produces some great things and some stupid things. They also don't care whether you think what they are doing is great or stupid, they just continue doing their thing Which then tracks back to the beginning of the thread: the correct answer to whether apple will adopt jxl-rs or keep libjxl is "who knows, no point trying to predict them". Which is not a value judgement How you square all of that with the iPhone regularly copying features Android had for years is your decision. Might be a symptom of the same, might be that this all was an entirely inaccurate description of Apple
  - _joel 22d ago
    That useless strip could play lemmings and doom, it wasn't all bad
  - 22d ago

Apple is gonna do what apple wants.

cute_boi 22d ago

[flagged]

arkon_hn 22d ago
Not to mention how updates are tied to OS updates...
- tengwar2 22d ago
  Hasn't been the case for some time.
  - spartanatreyu 22d ago
    Not true. MacOS releases a new version each year, the current MacOS landscape looks like: - MacOS Sequoia (previous version, everything works as expected) - MacOS Tahoe (current version, broken experience, basically Apple's "Windows Vista/8 moment") - MacOS Golden Gate (next version, fixes what was broken in Tahoe, comes out in a month) I'm on MacOS Sequoia because I have things that can't be broken by updating to Tahoe. I also cannot test how my websites/webapps will work in a month, because Safari's beta (called Safari Technology Preview) only works on Tahoe and Golden Gate. I cannot wait a month to update to Golden Gate because Golden Gate drops support for my iMac. And I can't test the new version of Safari on my Windows or Linux devices because Safari isn't available for them. I can test the Webkit browser, but that doesn't include the Safari specific changes that apple makes which I need to be able to test. --- So, I can't test Safari until I wait a month and purchase a new apple machine. (Oh by the way, apple keeps cancelling orders for new machines)
    - alwillis 22d ago
      > And I can't test the new version of Safari on my Windows or Linux devices because Safari isn't available for them. You can download three Linux-compatible WebKit-based browsers from Apple's WebKit page: Epiphany Technology Preview: https://webkitgtk.org/epiphany-tech-preview https://webkitgtk.org/epiphany-tech-preview WPE: http://wpewebkit.org/download http://wpewebkit.org/download WebKitGTK: http://webkitgtk.org/download http://webkitgtk.org/download
      - tosti 21d ago
        There are subtle differences. From the top of my head, differences with osx include the font rendering and the tab order (which is broken for everything except form elements).
        alwillis 21d ago
        I get it; when Safari was available for Windows, the font rendering was different from the Mac version.
- dlahoda 22d ago
  What Updates tied? App Store updates use same networking and storage as OS? Why it is bad?
  - deleted 22d ago
    [deleted]
  - flyingjoe 21d ago
    because updating a single app via the app store is faster than updating the whole OS. Having a security vulnerability in a browser could be fixed immediately, but having to ship out a whole new OS leaves it open for a while. Especially with users generally being against/too lazy to do OS updates
    - arkon_hn 21d ago
      Exactly this. We so often see people still using iOS versions from ~4 years ago despite having options to update. Apple holds the ecosystem back.
    - kekdkrjfjjwfj 21d ago
      Except that they can and have pushed security updates that are not necessarily OS updates. Granted the process is still through the settings app, but the point still stands. They have a channel for pushing yellow and red alert updates. Anything else can easily wait a couple of months.
- Unai 21d ago
  A non-evergreen browser in 2026 should be publicly ridiculed any time its name is brought up.
  - account42 21d ago
    Web developers who think you need the latest and greatest features to build a hypertext document are the ones who should be ridiculed.
    - Unai 21d ago
      Thankfully, people with ridiculous opinions ridicule themselves. Like pretending the web is just documents, as if we were living three decades ago. Or pretending that "latest and greatest features" is the only reason to keep a browser updated. Or pretending that new features are somehow bad or not useful. Or defending poor Apple for wanting people to spend a grand on new hardware to update be able to update their browser.
nchmy 22d ago
[flagged]
- chuckadams 22d ago
  Maybe because they don't want to see this thread dragged down into an open-ended gripe-fest against Apple, especially when it's concerning a feature Apple did ship before everyone else.
dlahoda 22d ago
My wife, son and me not using Safari. Do not see how Safari relates to App Store. We use App Store.
- SR2Z 22d ago
  The point of a PWA is that instead of downloading an actual binary app, you essentially get a webpage that runs like it was an app. They can be installed from anywhere and are safe by nature because they're really just webpages. That was the original conception of iPhone apps, until Steve Jobs realized just how much money could be made from the app store. Now you get to pay Apple a 30% cut for the privilege of installing software on your own device!
  - kekdkrjfjjwfj 21d ago
    > Now you get to pay Apple a 30% cut for the privilege of installing software on your own device! Kneejerk reactions everywhere! Wow. And to think HN commenters like to think themselves superior to other reddit/instagram/linkedin/social media users.
    - SR2Z 20d ago
      Am I wrong? Was Apple's cut not 30%? Did it not generate a quarter of their revenue last year, over a hundred billion dollars? I have an iPad. I don't need nannying from a trillion-dollar corporation to use my device and yet that's what I get - every excuse Apple makes (security, consistency, whatever) are obviously possible without the level of locked-down their devices are.

llm_nerd 22d ago

What a funny tangent to go off on. JXL was dead. Apple is who brought it back to life[1], and the only reason Chrome resurrected JXL, and now Firefox followed their path, is because Apple pushed JXL support to a billion plus devices. I know people like complaining about Apple, but there's a "read the room" kind of moment where people just seem to either not know the context or are just knee jerking. [1] Worth noting that Apple used the reference implementation, libjxl, and that project still remains the reference implementation with the Rust port being experimental (and of course Apple deployed JXL support over a year before the Rust port even existed). Maybe they'll switch to it at some point, but it's a bit premature to complain about.

deadbunny 22d ago
[flagged]
- concinds 22d ago
  I don't see what this has to do with the topic, sorry.
  - wongarsu 22d ago
    Their point is that Apple is the Nintendo of computing. They don't care what others do, they just do their own thing. Which produces some great things and some stupid things. They also don't care whether you think what they are doing is great or stupid, they just continue doing their thing Which then tracks back to the beginning of the thread: the correct answer to whether apple will adopt jxl-rs or keep libjxl is "who knows, no point trying to predict them". Which is not a value judgement How you square all of that with the iPhone regularly copying features Android had for years is your decision. Might be a symptom of the same, might be that this all was an entirely inaccurate description of Apple
- _joel 22d ago
  That useless strip could play lemmings and doom, it wasn't all bad
- 22d ago