3 ms·

It doesn't matter if the implementation is the same. Apple has access to API's that the rest of us don't and it's not so they can have more power than us. They

It doesn't matter if the implementation is the same. Apple has access to API's that the rest of us don't and it's not so they can have more power than us. They can't be expected to make public API's for everything and maintain them for every release. Not to mention I'm sure Apple has been working on this for a while. The whole f.lux thing didn't occur too long ago.

Karunamon 11y ago
Apple has access to API's that the rest of us don't and it's not so they can have more power than us. Sometimes I wonder. It sounds like if an API change breaks your app, then your app is broken and should simply get pulled for that. Furthermore, they tapped the flux guys on the shoulder and told them hosting their code with the instructions for people to sideload it themselves isn't allowed. https://justgetflux.com/sideload/ https://justgetflux.com/sideload/ Don't confused Apple's infamously controlling nature with some desire to adhere to good development practices. It's just Apple being Apple.
- k-mcgrady 11y ago
  >> "It sounds like if an API change breaks your app, then your app is broken and should simply get pulled for that." A simple solution but a terrible one for users. Imagine apps on your device regularly breaking and having to wait several weeks for developers to update them. If they update them at all. Apple would also have to monitor user reports, test supposedly broken apps, then make a decision to pull them. And if they got the decision wrong they would be killed for it in the press.
  - Karunamon 11y ago
    Imagine apps on your device regularly breaking and having to wait several weeks for developers to update them. You mean like we get right now whenever there's an iOS update? And if they got the decision wrong they would be killed for it in the press. You mean like they already are when they make an arbitrary, asinine, illogical decision about pulling someone's app? Apple's approach to developer relations can be charitably described as that of the honey badger.
icebraining 11y ago
The whole f.lux thing didn't occur too long ago. Just for reference: f.lux first released an app for iOS in 2011. So there's been four years, half of the entire lifespan of iOS.
- Symbiote 11y ago
  The first commit on Redshift is November 2009, and I don't think it was the original implementation of this idea. https://github.com/jonls/redshift/commit/4818f331cedeba94bb769fb15fd972dc759fd31f https://github.com/jonls/redshift/commit/4818f331cedeba94bb7...
  - icebraining 11y ago
    Oh, f.lux was released in February 2009 for desktops, I was just talking about the iOS app.
  - Luyt 11y ago
    That's correct. Way back in the 90's I was tweaking the VGA color palette registers of my MSDOS computer to make the colors more easy on my eyes at night. I never released that small program...

Karunamon 11y ago

Apple has access to API's that the rest of us don't and it's not so they can have more power than us. Sometimes I wonder. It sounds like if an API change breaks your app, then your app is broken and should simply get pulled for that. Furthermore, they tapped the flux guys on the shoulder and told them hosting their code with the instructions for people to sideload it themselves isn't allowed. https://justgetflux.com/sideload/ https://justgetflux.com/sideload/ Don't confused Apple's infamously controlling nature with some desire to adhere to good development practices. It's just Apple being Apple.

k-mcgrady 11y ago
>> "It sounds like if an API change breaks your app, then your app is broken and should simply get pulled for that." A simple solution but a terrible one for users. Imagine apps on your device regularly breaking and having to wait several weeks for developers to update them. If they update them at all. Apple would also have to monitor user reports, test supposedly broken apps, then make a decision to pull them. And if they got the decision wrong they would be killed for it in the press.
- Karunamon 11y ago
  Imagine apps on your device regularly breaking and having to wait several weeks for developers to update them. You mean like we get right now whenever there's an iOS update? And if they got the decision wrong they would be killed for it in the press. You mean like they already are when they make an arbitrary, asinine, illogical decision about pulling someone's app? Apple's approach to developer relations can be charitably described as that of the honey badger.

icebraining 11y ago

The whole f.lux thing didn't occur too long ago. Just for reference: f.lux first released an app for iOS in 2011. So there's been four years, half of the entire lifespan of iOS.

Symbiote 11y ago
The first commit on Redshift is November 2009, and I don't think it was the original implementation of this idea. https://github.com/jonls/redshift/commit/4818f331cedeba94bb769fb15fd972dc759fd31f https://github.com/jonls/redshift/commit/4818f331cedeba94bb7...
- icebraining 11y ago
  Oh, f.lux was released in February 2009 for desktops, I was just talking about the iOS app.
- Luyt 11y ago
  That's correct. Way back in the 90's I was tweaking the VGA color palette registers of my MSDOS computer to make the colors more easy on my eyes at night. I never released that small program...