On the latest episode of The Talk Show John Gruber very clearly says “the M1 MacBook Pro” a couple times.
Did he just let the cat out of the bag or just misspeak and meant the M1 MacBook Air?
Of course I want to know. 😀
UPDATE: John didn’t slip, I did. I forgot there is a 13in M1 MacBook Pro. Sorry for the mistake.
https://iam.fahrni.me/wp-content/uploads/2021/05/img_8096.movSix Colors: “Leaving big, bad Spotify aside, consider Overcast or Castro or Pocket Casts. These independent apps are likewise prevented by Apple’s policies from doing what Apple is doing. Even if they could figure out a way to implement Apple’s per-podcast subscription approach, they would have to hand Apple its cut, which is basically the same cut that Apple’s taking from Apple Podcasts Subscriptions.“
You knew it was only a matter of time before Apple created its own Podcast service. They’ve had the plumbing for years by serving the largest podcast directory in world. It’s still there and it’s still free, for now.
If I were a podcaster I’d worry about that benevolence continuing forever. Talk about an easy to Sherlock industry. With Apple holding the keys to the directory, a new paid service, and the most popular podcast player it would leave me going hmmmmmm, if I had a podcast or a podcast network.
For those, like Snell, who have invested years of blood, sweat, and tears to build their own networks I have to imagine they’ll have some restless nights trying to decide if they should just go with the flow and move their catalogs to Apple Podcasts 100%, keep their podcasts on their own network, or do a 50/50 split between their network and Apple’s.
An observation. At one point the podcasts I listened to were all ad supported. I have to believe advertisers, for some reason, decided the money they were paying for podcast advertising wasn’t paying off. Most of the tech podcasts I listen to began offering memberships. Those memberships may include special stuff for subscribers, as Snell points out.
That to me was a signal of a change in the podcast market. Advertising dollars were drying up or, at the very least, not as lucrative, so business models changed.
Enter Spotify and now Apple. We expect Facebook to announce their own podcast network. Being an indie is going to become as difficult as being an indie app developer or blogger who makes a living from their website. I fear we’ll see a lot of podcasts we love disappear as soon as they no longer make a living for their hosts.
In the end it would be really nice for Apple to offer a way for podcasts to use their own payment systems for subscribers. I’ve thought about this for indie app developers too. Having a way to provide Apple approved payment providers would be amazing. This would give players like Stripe or PayPal the ability to qualify as a payment provider for Apple Podcasts and the App Store. That alone would open the App Store and Podcast ecosystems to a new world of possibilities, not to mention possibly putting more money into the pockets of developers and podcasters.
On the client side Apple could provide a payment kit, possibly StoreKit, that allows for multiple payment providers to be selected by app developers for in app purchases. That framework would also provide third party podcast apps with a way to subscribe, download, and play podcasts from Apple Podcasts. Even if it means podcast players need to do work to support this system at least they’d be given the choice to support the framework or not. More choice is better, right?
As for the definition of a Podcast. I don’t think Apple or Spotify’s service meet the definition of a Podcast. To many of us a Podcast is an MP3 file delivered to a client via inclusion in an RSS feed. It’s not simply spoken word delivered by a proprietary service. It’s specifically connected to the open RSS format. That may seem a bit pedantic but that’s how we feel about it. To layer a service on top of that is fine. But to call it a podcast seems disingenuous.
I had a couple hours of driving to do today, had to take my busted computer in for repair. To while away the time on road trips I often listen to a podcast or two. Today’s selection was The Talk Show, Episode 75.
Messrs. Simmons and Gruber discussed scripting languages and asked if Apple needs to create a modern language for iOS and Mac development. The discussion was good, but I think there were a couple topics they could have touched on.
Pointers
Every C, C++, and Objective-C developer has had to deal with them. With the introduction of ARC a few years back pointers are all but an afterthought in Objective-C. Sure, there are exceptions, but mostly we no longer have to worry about freeing memory and it’s taken care of by the compiler, not a garbage collector. We have the best of both worlds with Cocoa and Objective-C; Native speed and memory management.
C#
Something they mentioned was Microsoft’s creation of a modern language based on a C lineage. It makes sense to do that because there is a big pool of developers that understand it, but I digress. I think the more important technology is Microsoft’s creating of the CLR and the .Net framework. One of the reasons these two items are so important is, they’re language agnostic. You don’t need to know C# to realize the full power of the CLR and the .Net frameworks. Take a look at CLI languages. It’s big. This gives developers the ability to use libraries from other developers and still work in their preferred language.
In the end I’m not so sure Apple needs to do anything. They’ve build, and continue to build, a great developer ecosystem. The Cocoa Framework is mature and is a huge benefit to iOS and Mac developers because we get a lot of shared code between the two.
Do we need scripting languages? Absolutely! Do we need them to build high performance native applications? Not really.
I’ve keep harping on this next point. Where we need advancement is in the browser. It’s locked in JavaScript hell. The browser is the new OS. The browser really needs a full CLI implementation.
If you have some time to kill download the episode. I really enjoyed it.