Re:The 0.5 MB of nothing in all Apple Music files (2020)
by JKCalhoun on Thursday April 07, 2022 @09:17AM
(#30944023)
Curious as well. All I can add is that iTunes also needed to run on Windows (and I believe QuickTime had, in effect, the old MacToolbox running cross-platform). So add throw that on the pile.
iTunes had to move fast. There was not time, from what I understand, to step back and refactor it in any meaningful way.
Re:The 0.5 MB of nothing in all Apple Music files (2020)
by at_a_remove on Thursday April 07, 2022 @10:35AM
(#30944945)
There never is time to refactor.
Re:The 0.5 MB of nothing in all Apple Music files (2020)
by easton on Thursday April 07, 2022 @09:54AM
(#30944454)
Adding on to this, I heard a rumor (probably here) that iTunes for Windows was ported by Apple porting Objective-C and Cocoa to Windows, which is part of the reason it acted so funny. I have no idea if that's true though.
Re:The 0.5 MB of nothing in all Apple Music files (2020)
by jfb on Thursday April 07, 2022 @10:35AM
(#30944935)
Safari for Windows was a side effect of the porting work that was happening on the Store to move away from a custom renderer to just using WebKit. And the reason iTunes on Windows was the way it was, and indeed, why iTunes on Mac stayed in this hellacious status for so long, is that it was built on _QuickTime_, which brought most of the Mac Toolbox over to Windows, and then -- eventually -- Carbon.
Re:The 0.5 MB of nothing in all Apple Music files (2020)
by kitsunesoba on Thursday April 07, 2022 @10:02AM
(#30944542)
Objective-C and Cocoa for Windows dates back to the NeXTSTEP/OPENSTEP/Rhapsody days, but yes it’s true. Safari for Windows also utilized this, perhaps to a greater extent, because its UI looked significantly more like its Mac counterpart than iTunes did, to the point that even the text rendering was the same between Windows and OS X.
Y'know, iPod (and later iPhone) sync, music browsing and purchasing, (payment handling), intelligent media organization (or some approximation thereof), working with giant media libraries...
I get the idea that everyone just feature-piled on top of the SoundJam code without fully scaling the design to the point of being able to coherently load-bear the additional functionality. So basically failure to adequately PM where it counts. That requires PM that understands engineering, which is sadly a tall order out of the gate and generally the most crucial before projects get big and the need for support becomes obvious.
*IFF* that happened in this case (I have absolutely no concrete idea), my question would be a) where "Steve really wants this - put a good PM on it" and/or b) where "this code explosion is killing everyone, we need PM help", ended up.
iTunes history anybody? (Genuinely curious, wondered for a while)