Re:Developing iOS 11 Apps with Swift
by spike021 on Thursday November 16, 2017 @12:55AM
(#15710523)
I don't understand why Apple removed iTunes U from the Mac iTunes Store. Not everybody has an iPad to use alongside their Mac while working through this series.
Re:Developing iOS 11 Apps with Swift
by srikz on Thursday November 16, 2017 @02:38AM
(#15710825)
What's more annoying is I can browse all the content on iTunes on the Mac but if I click on anything it takes me to a Safari page which says '.. only available on iPhone and iPad'. Why?
Some suggest that it will be back and right now they are decluttering iTunes and it'll be broken into multiple apps. I'm not too hopeful.
Re:Developing iOS 11 Apps with Swift
by the_common_man on Thursday November 16, 2017 @02:49AM
(#15710858)
Wow, delivering videos via an app.. This is so hostile. Why would somebody do it this way and not publish on some video site like vimeo or omg coursera, khan academy etc?
Re:Developing iOS 11 Apps with Swift
by bobnarizes on Thursday November 16, 2017 @06:59AM
(#15711997)
I think the problem with those sites it's that they have some kind of profit. Either by hosting ads or by selling some certificate, where iTunes U really offers the course for "free" on compatible platforms. Maybe this is the focus of Standford
Re:Developing iOS 11 Apps with Swift
by oblio on Thursday November 16, 2017 @03:18AM
(#15710979)
True, but it's ridiculously hostile to restrict access to free, public videos in such a way...
What if I want to just check things out because I might be interested? Should I buy an iPhone on the off-chance that I find things interesting and might want to develop something later? Sheesh.
Re:Developing iOS 11 Apps with Swift
by valuearb on Thursday November 16, 2017 @09:17PM
(#15718442)
You might be interested in developing for iOS but don’t have an iOS device? Not even an AppleTV or Mac, both of which play itunesU content?
Apple wants to still promote iTunesU, which offers a better user experience for learning content than Vimeo or YouTube. I don’t think they do, or should, worry about the 1% who want to watch and don’t have iOS devices.
Re:Developing iOS 11 Apps with Swift
by ubernostrum on Thursday November 16, 2017 @04:11AM
(#15711243)
The videos are only public because the creators chose to do that. Why is it "hostile" of them to choose a distribution mechanism relevant to the material? Why do you feel you have a right to demand they distribute this content -- which they made available for free -- in a manner you prefer?
Re:Developing iOS 11 Apps with Swift
by oblio on Thursday November 16, 2017 @04:18AM
(#15711282)
It's "hostile" because uploading to Youtube or Vimeo is just as much effort, if not less, than what they're doing.
So it was a conscious choice to do what they did, in order to limit distribution. It's the same kind of control-freak, developer hostile attitude that Apple has in general regarding its development tools: total lock-in. Compare with Android in this regard.
Re:Developing iOS 11 Apps with Swift
by harrisi on Thursday November 16, 2017 @03:18AM
(#15710976)
I haven't really looked at this but I do have a general dislike that this is an app/something on iTunes. I find it somewhat strange that when opening it on my iPhone SE the description is unrendered HTML: https://imgur.com/a/miJXw
Hence, you can detach from the update train with this version:
https://support.apple.com/en-in/HT208079
Some suggest that it will be back and right now they are decluttering iTunes and it'll be broken into multiple apps. I'm not too hopeful.
https://developer.apple.com/library/content/referencelibrary...
What if I want to just check things out because I might be interested? Should I buy an iPhone on the off-chance that I find things interesting and might want to develop something later? Sheesh.
Apple wants to still promote iTunesU, which offers a better user experience for learning content than Vimeo or YouTube. I don’t think they do, or should, worry about the 1% who want to watch and don’t have iOS devices.
So it was a conscious choice to do what they did, in order to limit distribution. It's the same kind of control-freak, developer hostile attitude that Apple has in general regarding its development tools: total lock-in. Compare with Android in this regard.
Yes.