Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

ADSP: Algorithms + Data Structures = Programs

ADSP: Algorithms + Data Structures = Programs artwork

Episode 40: Star Trek vs PowerPC (with Sean Parent)

Aug 27, 202140 minAudio

In this episode, Sean Parent tells the story of the battle between Project Star Trek and PowerPC. About the Guest: Sean Parent is a principal scientist and software architect for Adobe Photoshop. Sean has been at Adobe since 1993 when he joined as a senior engineer working on Photoshop and later managed Adobe’s Software Technology Lab. In 2009 Sean spent a year at Google working on Chrome OS before returning to Adobe. From 1988 through 1993 Sean worked at Apple, where he was part of the system software team that developed the technologies allowing Apple’s successful transition to PowerPC. Show Notes Date Recorded: 2021-07-28 Date Released: 2021-08-27 Blue Meanies Taligent Motorola 68000 Pentium RISC (Reduced instruction set computer) Novell Apple Star Trek project MacHack PowerPC John Sculley GARY DAVIDIAN AND HIS 68000 EMULATOR Rhapsody (operating system) Epic Games v. Apple Intro Song Info Miss You by Sarah Jansen https://soundcloud.com/sarahjansenmusic Creative Commons - Attribution 3.0 Unported - CC BY 3.0 Free Download / Stream: http://bit.ly/l-miss-you Music promoted by Audio Library https://youtu.be/iYYxnasvfx8

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

Sean ParentUh Roger gave this amazing little uh monologue where he said, Hey, he said he's sick and tired of all these engineers complaining about people leaving. And and they had to understand that uh Apple gets thousands of resumes every single day. And he said, if you want to see the impact, you're gonna leave leaving the company. He said uh uh uh put your hand in a bucket of water and pull it back out and look at the hole you left.

ConorWelcome to ABSP the podcast, episode 40, recorded on July 28th, 2021. My name is Connor, and today with my co-host Bright, we interview John Perrin, and he tells us the story of the battle between Project Star Trek and PowerPC.

Sean ParentSo a little background here. At Apple, when I joined Apple, I was working on QuickTry GX, and then I switched to a team uh which was known as the Blue Meanies, uh, which were uh the purpose of the Blue Meanis is uh they were the system integration architects. This was around uh macOS System 7 during Mac OS System 7 development. So the Blue Meanis basically went around and figured out what all the various teams at Adobe were doing and tried to find uh uh uh areas where teams should be talking together more and coordinating more and and just kind of making connections there.

Sean ParentUh uh and they would also help with you know difficult to solve uh uh uh engineering problems that came about in in kind of integrating components.

ConorIs this like meanies as in like M-E-A-N-I-E-S, like someone who is mean to someone?

Sean ParentYeah, it you know, the references to the uh the the the the blue meanies in the uh uh Beatles uh uh uh what is it, yellow submarine movie.

ConorSo oh it's a cultural reference that I'm out of the loop on.

Sean ParentYeah, so so just search Blue Meanies and you'll see a little cartoon figure of what a blue meanie looks like. Do you know what this is, Bryce?

BryceUh no, I think we are uh I think we're wrong generation for us to understand this, Connor.

ConorYeah.

Sean ParentI do know who the Beatles are.

ConorOkay, well that's good. You know. The disappointment in the back voice. I guess yes, that that's a good thing.

Sean ParentYes. So uh yeah, so look up what a Blue Mini is and and their cute little cartoon characters. But uh, you know, Apple at the time was divided into pink and blue, where Pink eventually spun off to be Teligent. It was kind of future Mac OS thing, which never shipped. It ended up in a partnership with IBM as a company called Teligent. And um uh blue was kind of traditional macOS, and so the Blue Minis, that's where the blue comes in. And so uh yeah, so so I was working on Blue Meanis, and then part of what I was doing on Blue Meanis was I got uh uh task to start tracking uh a couple of projects that were shaping up.

Sean ParentThe context here was Macs were sitting on Motorola 68,000 processors, and uh uh Intel had the first Pentiums uh coming soon. And even though the first Pentiums were a a uh uh uh you know flaming hot uh uh uh you know massive energy consuming device, uh they were faster than anything that Motorola had in their pipeline in the 68K thousand line.

Sean ParentAnd uh uh Motorola was struggling uh with process manufacturing to build faster 68000s and to kind of move to standard to to smaller uh uh uh uh uh manufacturing processes. And so the answer seemed to be either to switch to switch Macs to Intel or switch Macs to uh RISC architecture. And so somebody at Apple, a guy named Gary Davidian, uh wrote an emulator uh for uh uh uh the 88.110, which was Motorola's RISC processor.

Sean ParentAnd uh uh he wrote a 68K emulator and showed that he was able to run Macintosh in kind of a fully emulated environment on an 88110 uh with reasonable performance, right? Right, it it it wasn't it wasn't fast, but but it didn't didn't suck. And uh uh uh Apple established a partnership with Novell, which was a non-Microsoft company that had a a competitor to DOS at the time.

Sean ParentUm uh uh but didn't, you know, uh uh Windows was kind of uh fairly new at this point. Novell didn't have an answer to Windows, and so Apple also entered into a partnership with Novell to investigate uh moving Macintosh onto Intel processors using Novell's underlying kernel um uh uh and Apple kind of providing the GUI interface on top of that.

Sean ParentAnd that was known as the Star Trek project. You can look these things up online now, they're they're fairly well documented. Well the the the Star Trek project was this very high profile partnership inside of of Apple, and the team had like a tremendous amount of resources and it was a large team, and they were, you know, this uh you know pirate team, you know, semi-super secret. They had their own floor of a building and you know, pool tables and and uh perks and uh uh uh uh lots of the best engineering talent, several of the Blue Minis kind of slid over into the Star Trek project.

Sean ParentAnd I was monitoring the uh 88110 and the RISC project, and out of that we created a little uh uh uh group to see if we could run uh uh uh with this idea of having some native code and some emulated code and bring up a machine in that environment using a risk processor. And uh and so it started as just a bunch of committee meetings exploring it, and eventually we got to the point uh where things were coming pretty far along uh and it was starting to look look feasible, and then I kind of had this aha moment uh at uh at Mac hack of all things.

Sean ParentI got ended up staying up all night kind of scribbling in a notebook of how mixed mode could actually work across for the seamless integration between 68K and PowerPC code, and neither code had to know about the other, and you could get existing Mac software to run, even though everything in uh existing 68K Mac was running in supervisory space, so you could have interrupt handlers and uh and all of these things, you know, executing in in user applications or system extensions or things of that, how I could make all of that work.

Sean ParentAnd uh uh, you know, even though I kind of have the aha moment, you know, this was not just me. There were a whole bunch of people who worked on this and were all listed on a patent for for mixed mode and uh and you know my my ideas were just putting together pieces that that that that other people had. Um so in any case I go back to to Apple and I start like, oh, I got this figured out, this is how it all works, and scribble it on the diagram, and everybody's like, okay, and uh and from there we uh we kind of moved out of committees and formed a team, the PowerPC team.

Sean ParentAnd one of the people who we brought in was an individual, Phil Koch, uh, who had been a professor at Dartmouth, and he joined uh joined Apple uh to be engineering manager on this team, and we ended up with several uh first interns and then later hires who had been uh his students at Dartmouth who who kind of came in. But we were a very small team. It was just uh uh uh a handful of us literally working on this, and we had a small cluster of offices mixed up with a bunch of other teams and and kind of you know no support.

Sean ParentThere was it was a secret Skunkworks project, but it this was not like Star Trek's project. We were not like well funded, we didn't have perks, we were just kind of struggling along. And uh eventually, well, Scully came in at one point and said, Oh, okay, so I cut this deal with IBM and and we're going with uh uh power architecture, so this will be a new processor, power PC, and and honestly, we had been evaluating risk chips and like power power architecture was you know like not even on the first page of candidates.

Sean ParentUh but to Scully's credit, Scully was like, yeah, I he was like, I I looked at your list. There aren't that many companies that can produce chips in the volume that we need. And and uh uh uh you know IBM is one of them. And so it became this very complicated uh partnership with IBM and with Motorola, which is where PowerPC came from. So there was a three-way partnership around the processor chips, uh there was an extended partnership with IBM, uh around uh Talligent, which would would was Apple's pink operating system, which would maybe be a future operating system running on PowerPC.

Sean ParentAnd uh there was an effort to uh bring up Macintosh software on top of AIX, and that actually shipped at some point. AIX is IBM's flavor of Unix. And uh uh and then there was our project, which was secret even to IBM, because IBM thought that when they were shipping these things that it would be their AIX kernel sitting underneath Macintoshes uh uh uh that were PowerPC, and Apple wanted a kind of side bet on maybe we could do this just with all Apple software.

Sean ParentAnd so that was the team that I was working on. And and so we got to the point where we were, you know, first we prototyped everything. We like prototyped all of mixed mode running 68k to 68k, which sounds kind of weird, but it but it you know actually worked as a proof of concept and kind of prototyped the architecture and then started building things on power machines, which are not quite power machines, to get things kind of limping along. And then eventually we had PowerPC silicon and we built boards that you could plug into 68k Max uh uh uh Quadra 800s and you know went through like how do you use logic analyzers to get to the point where you can boot these devices.

Sean ParentAnd then we were able to get them up inside of an emulator booting on them based off of Gary Davidian's work, but now ported to to uh to PowerPC. And and then uh uh finally we get to like show mixed mode. And the first thing we moved over to mixed mode was there was uh an old Mac toolbox routine called setRect, which all it did was it took you know four coordinates as 16-bit integers, top left, bottom right, and returned a struct of those four integers that were passed as arguments.

Sean ParentSo an almost do nothing routine, it's basically just copying four integers from from the stack into a struct on the heap, or or in a struct on the stack. So it's just just copying four integers. And the um uh uh the but the interesting thing about set rect uh uh was it got called all over the place. It got called at interrupt time, it got called from patches to the operating system, it got you know uh uh uh called from signal handlers, it was it was everywhere.

Sean ParentAnd so uh uh we were able to take that routine native and show that you know native code could call it, native code could call it even if it had been patched with 60 AK code, um uh 60 AK code could call it regardless of the execution context, and it would execute correctly and return correctly and keep the sh state of the machine and and nothing fell apart, right? Everything still worked. And so that was our our uh proof of concept.

Sean ParentAnd and after after we got that running, uh uh uh the next next day we got it running kind of late in the evening, and and the next next morning Phil Coke walked into my office and closed the door and said, I I owe you an apology. And I said, said what for? And he said this whole mix mode thing, I didn't think it was gonna work. And and I said, Well, you know, you should have said something. He's like, he's like, oh no. He said, I you know, you explained it, you I would, you know, explain it to anybody who wanted to hear.

Sean ParentYou know, walk up to the whiteboard and walk ever walk through the logic of how it worked through all the transitions. He said, he said, I saw what you were doing. I couldn't poke a hole in it. He said, just my gut said this isn't going to work. And I said, Well, you know, you don't owe me an apology for that, right? Thanks for letting us run it out. And uh and he said, No, no, he said, he said, you don't understand. My reports to my bosses and the executives have been this team's doing this, you know, wacky mix mode thing.

Sean ParentI don't think it's going to work. He said, So you want to know why this team doesn't have the funding that Star Trek has, why other teams aren't excited about porting their code to PowerPC, uh, why this team has like zero support, why it's just a handful of people. He said, because you're you're the side bet that I didn't think was going to work. Okay. So so, you know, i in in reality, in in retrospect, I think that that keeping the team small, keeping the team focused, uh uh keeping all the outside distractions from pouring in was was critical to actually getting this to ship.

Sean ParentUh I give Scott Boyd, who was technical lead on this project for most of the duration of the project, uh, a lot of credit for getting this thing shipped, and he coined the acronym NNTS, which was not necessary to ship. And kind of anytime was like, oh, I think you know we should be doing X, he would respond in with an email of just NNTS, you know, meaning like good idea, bad idea, I don't care, it's not necessary to ship. So so very much trying to keep the team focused.

Sean ParentUh uh so uh uh uh you know so that all happened and we shipped PowerPC and PowerPC launched and it was a big success, and and uh PowerPC was known as as V0 internally because there was a plan. Apple had a roadmap that was kind of v1, v2, v3 of what they were going to do with their new with their new kernel work, and and PowerPC, we scaled it back so much to get it out the door that we called it v0.

Sean ParentAnd the the team pitched a uh a follow-on, which was called Alberto, which is VO5, if anybody knows the hair product Alberto V05. Uh but yeah, so it was it was a half-step between v0 and and and v1. Uh uh uh but management at the time said no, we have to drive towards uh uh uh uh uh uh V1, and so that project got canceled, and Roger Heinen, who was leading system software at the time, uh uh Apple was losing a lot of talent at this time.

Sean ParentApple was kind of bleeding cash and was was scrambling even with PowerPC's success. Uh you know, Apple was looking to uh to enable clones, and this is like soon after kind of this this unwinding is when when Steve Jobs kind of did the reverse takeover thing and came back to Apple. Um so Apple had been bleeding talent, and and uh uh uh there was a meeting with Roger Heinen, who was head of system software, and the engineers were raising the concerns in the audience, going, you know, what are you going to do to to keep talent here and keep people from leaving?

Sean ParentAnd and uh uh uh Roger gave this amazing little uh monologue where he said, hey, he said he's sick and tired of all these engineers complaining about people leaving, and and they had to understand that uh Apple gets thousands of resumes every single day. And he said, if you want to see the impact you're gonna leave leaving the company, he said, uh uh uh put your hand in a bucket of water and pull it back out and look at the hole you left. Uh, you know, basically meaning that like no engineer mattered.

Sean ParentAnd uh uh one of the senior colonel engineers uh like walked up to the the the the front of the little amphitheater we were in and uh handed Roger his badge and just kept walking.

BryceAnd uh uh so moral morale was clearly high.

Sean ParentMorale was clearly high. We also had in in one of the hallways, we had uh uh tombstones, whereas each engineer left, we kind of drew a tombstone and put rip in their name on it. So yeah, morale was really high.

ConorUm you said amazing speech, I thought it was gonna be this like uplifting, you know.

Sean ParentOh it it was like it was a lesson in like how not to manage is is what this was. Um so yeah, so after uh uh the Alberto project got shut down, pretty much everybody who was on the PowerPC team left in about six months, and that's when I went to to Adobe and and and joined the Photoshop team. Uh so the end result was a good thing for me. And so now fast forward, you know, we kind of talked about the I'm I'm at uh at Adobe and I'm I'm Macintosh tech lead on Photoshop, and I come up with the Cyan proposal now that Steve Jobs is back at Apple and they're doing a transition.

Sean ParentUh uh there was going to be Rhapsody, and then there's the Cyan proposal, and then uh uh uh uh and then we find out about uh OS 10 when I get a call from Steve Jobs and get to go over to Apple and and and and and learn about OS 10. And so so all of that happens, and uh and then I get a phone call from Phil Coke at Apple, and Phil says, Hey, I'm I'm I'm leaving Apple and I I just wanted to come and have lunch with you.

Sean ParentAnd and I'm like, oh, oh that's that's great. And uh uh so he comes over and we're sitting at lunch and he said, Yeah, he said, I'm I'm gonna retire and and and and leave Apple. He said, but uh I I wanted to let you know something that you're probably not aware of. And he said, when this uh Cyan proposal happened, he said this uh uh Apple executive who who who I won't name, but he's the the the person who had had led to us cutting off negotiations around around Rhapsody, who had had had written emails to John Warnock about both Greg Gilly and myself being impossible to work with.

Sean ParentUm he said, yeah, so so so he said that at one point during that whole thing, uh the executive walked into my office and put a paper on my desk and said, I need you to write up uh why this won't work. And and he said, I I looked at the cover, he said, and it said, you know, the Siam proposal, Sean Parent. He said, and I handed it back and said, It'll work. And he and he said, he said no.

Sean ParentHe said said the executive was like, like, no, that that it wasn't a question of will it or won't it work. I need a report from you that says it won't work. And uh And and Phil said, he said, I flat out refused. He said, said I won't do that. He said, I'll tell you right now. He said I can I can I can read the paper and tell you why it will work. Or you can just take my word for it. It's it gonna work. And um and and handed it back and uh he said so.

Sean ParentSo he said I I you know he said after what what happened with PowerPC, he said I th I thought you deserved to know that. So I thought that was uh an an interesting side story. So that's what the story that uh Tony was was referencing. So the question is, is that the genesis of what ended ended up, you know, the start of the what was it, two-year path to Steve Jobs then calling you back and like, hey, we gotta we'd like you to come over to Apple and uh Yeah, you know, if I had to guess, I think the time frame there was was was probably just before the meeting where I blew up at this executive, right, in between the meeting with uh with Greg Gilly and the meeting that I had, and because at you know I mentioned before that that meeting was supposed to be um uh uh with uh uh uh Apple explaining the cost of them doing the Cyan proposal and and kind of walking through the the business aspects of this whole thing.

Sean ParentAnd and Apple just came in and said, you know, it's impossible and we're not doing it. And that's what led me to get into the argument about saying, you know, you're you're full of crap, and uh, you know, if if you know if you want it built, you can hire me and I'll go build it, right? Right? It's it's it's a hundred percent doable. And so so I think like before that meeting, uh, this executive had gone to Phil looking for ammunition.

BryceAnd uh Do you I I'm I I doubt that you'd be able to share it, but do you still have a copy of the report?

Sean ParentYou know, unfortunately not. Um uh the the Cyan proposal. I would love to have it just kind of as a historical artifact. And I've kind of asked some friends at Apple to see if anybody kept it. And uh uh uh uh yeah, you know, I uh I keep a lot of old email, but like like not anything that far back, and I kind of dug through and and after you know leaving the company and coming back, I could not find find the Cyan proposal.

Sean ParentUm so yeah, if any of your listeners have an old copy line about someplace.

BryceWhat year would it have been?

Sean ParentUh so let's see. This would have been I'm guessing ninety-five.

BryceSo if you worked at Apple in nineteen ninety-five on their operating systems.

Sean ParentYeah, you might have had a copy if you were working at uh at Adobe 2.

BryceUh, or if you were at Adobe.

Sean ParentUm I should ask uh I don't know that I've ever asked uh uh uh uh uh Russell Williams. He worked on uh what was going to be the V1 kernel at Apple and then hired him to work on uh to work on Photoshop and he's been at Adobe working on Photoshop ever since and uh um uh you know one one of the key people on the Photoshop team.

BryceDo you remember how how long was the proposal? Was it just like a white paper? Was it just a couple pages, or was it like super?

Sean ParentIt was just a couple pages. It was like two pages. It was a short thing.

ConorWould you have been able to share it? I feel like it's been like a couple decades that that'd be similar with Apple.

Sean ParentI don't even think it was you know particularly interesting, right? It was it was uh uh uh you know basically it was an outline of what we had planned to do with uh with Alberto and with V1. And so and what Apple finally did with what was known as the the uh the blue box um uh uh on Mac Mac OS X. Uh uh but it was basically saying that yeah, you could uh you know have an environment where you could run existing apps that were written against the existing toolbox, and then you could also have an environment where where uh those apps could call out to kind of new Coco-based functionality and you could mix and match the two.

Sean ParentAnd and you know, it uh uh d but technically I don't think it was it was all that that interesting. I don't think it was like you know, interesting in kind of the mixed mode space, and I think anybody who seriously looked at the problem was like, oh sure, of course you could do that. Um uh you know, it was just Apple's reluctance. Apple wanted kind of this clean move to to next step and to jettison the the Mac baggage.

Sean ParentAnd so it was much more the combined strength of uh uh you know Adobe and Microsoft at the time that basically refused to make that move that convinced them to go the other direction. And and you know, I've heard you know, I've heard mixed reports from people in different parts of Apple as to how much of an impact the Cyan proposal had anywhere from from none. It you know, it it would have happened anyways to to to it wouldn't have happened because uh because Apple was so dead set against it and there wasn't any clear path in doing it to succeed unless somebody wrote down and committed to say, look, we'll move Photoshop if you do this.

Sean ParentRight? And so so that was the real the real impetus. And, you know, uh uh we got a lot of flack from Apple then because, like I said, you know, we we found out about this and then two weeks later we gave a demo on stage, but it hit at a really bad time in the Photoshop development cycle because you know we were kind of running 18-month product cycles and we were just finishing up a release, and so we didn't really have time in finishing up that release to do the Mac OS X support in that.

Sean ParentAnd so we ran in the in the in the blue box, which had a bit of a performance penalty, right? Right, basically it was an environment that lets you run you know old, old Mac apps that hadn't been ported yet. Um uh uh for for almost two years, right? It was almost two years until we shipped a quote unquote native native Photoshop.

BryceAnd you know, since since both machines were, you know, both the blue box and uh and outside the blue box were uh uh you know power PC processors, it wasn't like we were running some big performance penalty, but we didn't have the uh the new kind of lickable looking UI and and the app looked dated and and Yeah, I I remember I bet the one time in my life when I used uh Macs was around that era, right around the switch.

Sean ParentWhen yeah, yeah. Yep. Yep. So you know I somewhat think that uh uh uh that time period and the amount of pressure that Adobe and Microsoft could exert, right? To put it in perspective, you know, f at at there was a period there where where Photoshop accounted for more than 10% of the total software revenue on Mac. Okay.

BryceNot Adobe's, just in general.

Sean ParentYeah, not of Adobe's general, of like all developers that were developing Mac software, uh uh Photoshop was taking a 10% cut of that pie.

BryceBut that that that has that changed? Because like I know I know, you know, back during that era and and even for like 10 years after that, uh, you know, Macs were the platform where that you'd go to if you were doing that sort of creative work. But it seems like it's changed a bit in recent years.

Sean ParentYeah, yeah. Well, yeah, I I still think you know, Macs tend to be uh uh uh more prevalent in kind of the the the creative industry, but that segment of the market isn't as important for Apple anymore. Even Macs aren't as important for Apple anymore, right? I mean they're completely dwarfed by by iOS sales at this point.

BryceYeah. Yeah, I I saw I saw this funny graphic the other day that um like the the Apple's total business for AirPods is like larger than the than the business of like a number of notable tech companies.

Sean ParentYep.

BryceIncluding I think Nvidia both NVIDIA and Adobe, I'm sure. Yeah.

Sean ParentOh yeah. Yeah. And you know, the you know, I somewhat think the App Store rules are structured around trying to make sure that you don't have any companies that dominate.

BryceInteresting.

Sean ParentRight.

BryceAnd what what why is that bad why is that why is that something that Apple wouldn't want? Yeah.

Sean ParentBecause a company that dominates uh can exert control on Apple. Right? Right.

BryceAnd so they don't want to have to deal with the Sean Terrence of the world.

Sean ParentThey don't want to have to deal with me. That's the whole thing. It's uh interesting. Apple doesn't want to deal with Sean. That's why you guys all have to live with the App Store. You can put that in the podcast.

ConorThat makes a lot of well, that's sort of the uh what was the Twitter beef or whatever some company was it that they came out that they were breaking the rules and starting this feud because of the Epic? Yeah. Um I guess yeah, as soon as that happens, then like you said, they can sort of start a conversation or force their hand and be like, we're not paying this 30% fee. Yeah. Is there still like a loss lawsuits happening around that? I heard that's basically they they said that they weren't gonna pay.

BryceNow the Epic versus Apple lawsuit and the discovery, the discoveries in that lawsuit has just been hilarious. The the the the documents that were that were revealed during Discovery have just been uh very hilarious because they've happened to incidentally reveal a bunch of like secret projects and plans that other companies were undertaking. Um there's gonna be lawsuits branching off of this lawsuit from uh but uh but yeah, it's it's interesting.

BryceI've been reading the news about it a little bit. And I follow Tim Sweeney on uh on Twitter. Yeah.

ConorOh yeah, he said some unkind things about C the other day or a couple months ago. Uh because I remember on CPP Cast they were like, oh, maybe we should get Tim Sweeney on. And then like fast forward three weeks, I see Tim Sweeney saying that C is I don't know. I can't remember what he said, but it wasn't it wasn't nice.

BryceWhat do you what do you think will happen with this sort of stuff, Sean? Do you think that the the app developers like Epic will eventually prevail in uh in regaining some control of the ecosystem?

Sean ParentWell, I think the interesting thing is now, you know, Microsoft is in a position where they're no longer dominant and they're they're the the hungry player uh with still significant market share. Um uh you know, as far as desktop computers go, you know, they have a problem that they never made a successful transition to the to the mobile space. But if you look, they announced you know, with Windows 11 uh very reasonable terms for their app store, which is basically, you know, you put things in the app store, and if they handle the financial transaction, then they take a uh cut, which is like a 5% cut, which is you know more in line with what you would expect for kind of a little co-marketing and a uh uh uh and uh you know a credit card fee basically, right, for running the financial transaction for you.

Sean ParentUm uh uh and uh uh you know they've even said if if they don't handle the financial transaction uh then then they won't take their cut. And so I think that's going to change the the dynamics a bit. You know, Apple is so big at this point, I don't know how much pressure that puts on them. But I think it will uh uh make uh uh uh I I I think it will certainly be good for for the Microsoft ecosystem and for kind of expanding the Microsoft store offerings.

Sean ParentAnd there is something nice about having kind of a centralized store and knowing that your software is up to date and that at least somebody's looking at it to make sure it's certified, right? You know, you you feel confident like buying an Adobe product or a major product over the web, but a lot of times if it's a little utility or something, I'll see you be like, Do I want to download this from this sketchy looking website that hasn't been updated since the nineties, or maybe there's something that will work that's in the store, or at least know, you know, there's uh uh a little bit of a gating factor into what I'm installing and running on my machine.

Sean ParentSo so yeah, so so so I think uh you know Microsoft might successfully start to change the dynamics, and I think if uh I think there's an opportunity uh for for Google there, if Google wants to more differentiate the Android space from the iOS space to kind of follow suit with what what uh Microsoft is doing. And in the case of of of Google, I think that's a reasonable thing because I you know, I'm sure they make a lot of money, but they don't make Apple size money out of the Android App Store.

Sean ParentUm but they uh you know and and most of their money generating on the platform is is advertising revenue, right? That's their main business. And so so I think that that they might be able to to improve their platform to net benefit for them by actually reducing their cost structure, but whether or not they'll do it, I have no insight, you know, 100% pure conjecture here. Uh uh, but that again might start to put put competitive pressure on on Apple to cave.

Sean ParentOr somebody like Epic might just win a lawsuit in in this space and and uh uh uh uh open it up. You know, or you know, the right to repair folks might might win some lawsuits and uh uh uh you know establish better right to repair. Which is yeah, it's it's related.

BryceCertainly an an interesting time for uh uh for these legal issues in tech, because there's a bunch of these cases coming to a head right now.

Sean ParentYeah.

ConorYeah. There's gonna be another massive one, uh the Blizzard stuff that's coming up. Yeah.

BryceYeah. Blizzard does does not sound like a nice place to work. Does not sound like a nice place to work.

Sean ParentYep. So send your resumes to uh Adobe. We're a nice place to work.

BryceYeah, folks got the the ST, the software technology lab is uh is restarting that's gonna be an exciting an excit it's an exciting time to to go go work at Adobe, I bet.

Sean ParentIt is, it is. And uh uh yeah, and I think you know Adobe, if you look, you know, consistently ranks in the top in the in the list for for one, if not the top places to work. Uh and I think kind of the way we've been managing the the pandemic and now kind of getting people starting to to migrate back to work and the amount of flexibility the company is shown in that space, I think, has been has been very good and enlightening. And the company's been listening to their employees and trying to uh you know be very flexible.

BryceNot not insisting that everybody go back to the office like uh Apple and Google.

Sean ParentYes, not insisting that everybody goes back to the office. Uh uh the company's basically come out and said, you know, we're gonna have flexible time as the as the default uh for people.

ConorI didn't know that Apple, I heard that Facebook and Twitter both decided like a year ago, they were like, oh, this seems to work fine. Stay, feel free to stay forever uh working remotely. But Apple and Google both are mandating people have to come back at the same time.

BryceAt least somewhat, yeah.

Sean ParentYeah, at least somewhat. They're coming up with different terms. I I haven't been following all the news in and out, but I was reading something this morning where where basically I think the gist of it was that that Apple's policy was was either you register as a remote worker, you know, or you come into the office on a full-time, and and if you're a remote worker it means you're not in the office on a regular basis, and that comes with you know ramifications for pay and benefits and and and things of that nature. And and you know, it some of that is unavoidable, right?

Sean ParentSome of it is just kind of baked into into uh uh tax laws and employment laws and and and things like that. Uh but uh uh Adobe's basically dividing it into you can be a remote worker or you can be a flex worker. And a flex worker is everything from in the office all the time to just in the office on some regularly scheduled uh uh pattern. Thanks for listening. We hope you enjoyed and have a great day.

Open the transcript file

Hosts and Guests

Guests

  • Sean Parent Guest Inferred

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Episode 313: C++26 Reflection vs CRTP, AI, Kids & More with Zach Laine

    Nov 20, 202647 minAudio

    In this episode, Conor and Bryce chat with Zach Laine about C++26 Reflection vs CRTP, AI, kids & more. Link to Episode 313 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP:...

    • Apple Podcasts

    Credit the people on this episode

  2. Episode 312: The C++26 Contracts Fiasco

    Nov 13, 202652 minAudio

    In this episode, Conor and Bryce chat with Zach Laine about the C++26 contracts fiasco. Link to Episode 312 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP: The Podcast:...

    • Apple Podcasts

    Credit the people on this episode

  3. Episode 311: Career Changes, GPUs & More with Zach Laine

    Nov 6, 202628 minAudio

    In this episode, Conor and Bryce talk with Zach Laine about his career and the career changes he has made. Link to Episode 311 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials...

    • Apple Podcasts

    Credit the people on this episode

  4. Episode 310: Leaving NVIDIA for... ?

    Oct 30, 202624 minAudio

    In this episode, Conor and Bryce talk about Bryce's next chapter and where he is leaving NVIDIA for. Link to Episode 310 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP: The...

    • Apple Podcasts

    Credit the people on this episode

  5. Episode 309: Default Construction & CppCon 2026 with Jason Turner

    Oct 23, 202629 minAudio

    In this episode, Conor and Ben chat with Jason Turner about default construction in C++. Link to Episode 309 on Website Discuss this episode, leave a comment, or ask a question (on GitHub) Socials ADSP: The Podcast:...

    • Apple Podcasts

    Credit the people on this episode