Extinction-Level Event
Casey:
I have not heard John yet, but he probably just hasn't said anything.
Casey:
I'm here.
Casey:
Hi, John.
Marco:
John doesn't speak until spoken to or about.
John:
Not true.
Marco:
That's totally true.
John:
Name one podcast where you speak first.
John:
You didn't say first.
John:
You said not until spoken to or about, which is different than first.
John:
I could not be spoken to and not be spoken about and still speak second.
Casey:
Oh, my word.
Casey:
Is it going to be like that?
Casey:
That's how tonight's going to go.
Casey:
You know, when Marco called early, I was speaking the praises of the two of you.
Casey:
I was telling him I wasn't quite steeled, stolen, I don't know, S-T-E-E-L-E-D.
John:
What are you trying to go for?
Casey:
I wasn't steeled for the awesome that comes out of the two of you.
Casey:
Stolen?
Casey:
Yeah, I don't know where that went.
John:
The root word of that expression is not the thievery one, but the metal one.
Casey:
Yeah, well, hey, I recovered.
Casey:
I recovered.
Casey:
Anyway, the point is I was singing your praises before you showed up, and now I see how it's going to go.
Casey:
All right, so let's start with some follow-up, and we have some sad news from Safari.
Casey:
John, can you tell us about this, please?
John:
Last week was the second time I mentioned what I thought was my solution to my Safari extension woes, which was an option at the bottom of the develop menu that said allow unsigned extensions.
John:
since then i've learned that that option either doesn't do what i think it does or doesn't do anything and by the way even if you check it if you quit safari and relaunch it it forgets that you checked it so that setting is useless for my purposes and even if it did work and stick i'm not even as sure it does what i wanted to do so we are back to square one which is every time i launch safari i have to manually load my extensions which i continue to do
Casey:
because it turns out i don't launch safari that often like i launch it after when the computer boots and i just leave it running all the time so it's not great but that's what i'm doing in other news adobe is rethinking apps or their apps john alper writes they seem to be taking the photoshop approach you've been recommending to evolve premiere so premiere is their video editing app i believe it's their equivalent of final cut pro
Casey:
And they've said that they're announcing a new project.
Casey:
This just came out at VidCon.
Casey:
And they're announcing a new project called Project Rush, which is, and now I'm quoting from a link we'll put in the show notes, a new cross-platform editing application that's not released yet, but users can apply to be on the beta.
Casey:
And I guess this is just a rethinking of Premiere, kind of like how Final Cut Pro was a rethinking of Final Cut whatever was before it, 9?
Casey:
Yeah.
Casey:
I don't know.
John:
You're thinking of Final Cut Pro 10.
John:
Well, I mean, actually, I don't know if we mentioned this on the last show where we were talking about the clean sheet designs to applications like, oh, we've got a popular app.
John:
But what if we just rethought everything about it and threw out all the old stuff and just started fresh?
John:
And if we didn't mention it, we should have.
John:
iMovie was the first time Apple did that in a big way where they had a new idea about how iMovie could work.
John:
And there was at least a year where they shipped both the old and the new one or supported both the old and the new one because the new one was so new and didn't have all the stuff that the old one had.
John:
But they were so excited to be able to show us the new iMovie.
John:
And you may not be ready, but this is the future, so get used to it.
John:
And eventually the old iMovie went away.
John:
And the new iMovie is now the only iMovie.
John:
And then they took that basically the new iMovie design and brought it to Final Cut.
John:
And it went from Final Cut Pro 7 or whatever what version was to Final Cut Pro capital letter X, which may or may not be 10, depending on who you ask.
John:
I'm pretty sure it's 10.
John:
Is it 10?
John:
I don't know.
John:
I forgot.
John:
Yeah, it's always 10 with Apple.
John:
I don't think they've ever used it to actually say X. Anyway...
John:
And they didn't keep the old version of Final Cut around, and a lot of the Final Cut people were angry and kept using the old version for a long time.
John:
Those clean sheet designs were more like, we have a new idea about how the interface works.
John:
The Adobe ones, I think, are also part of leaving behind legacy code.
John:
I'm not sure how much code was shared between the old and the new iMovie, but I think it was mostly about the interface.
John:
But anyway, this Project Rush thing seems like it's similar in that it's not just like, oh, we're going to design the app UI and everything a different way.
John:
But it's like it's I think the reason it was, you know, related to like VidCon is like it's for it's cross device.
John:
So it will run on iOS devices and on the desktop and on phones because.
John:
people who are making youtube videos or whatever might actually be shooting and editing them on their ipad or on their phone not just on their desktop and you have to have a very different application if it's going to run in all those different environments and you have to start with a clean sheet you can't put adobe premiere on your phone because it would be a mess uh so here's another example of adobe trying to give itself a kick in the pants and maybe maybe this will stick maybe it won't maybe this apple stink or whatever but uh
John:
I think Apple did something similar with the Clips application of like, let's rethink what a video-related application looks like in the world of smartphones.
John:
I think these are all good things to do.
Casey:
We had a lot of people write in, probably 5 to 10, maybe even 15 people write in with examples of programs or scripts that they had written to find duplicate files.
Casey:
I think every single one that I noticed was Swift.
Casey:
That's probably not 100% true.
Casey:
I'm sure there were other ones that snuck by, but
Casey:
The submissions we saw were almost exclusively Swift.
Casey:
John wrote in.
Casey:
He was one example, not John Syracuse, a different John.
Casey:
He said that someone on the show was asking for a utility to find duplicate files and made a tool to do just that.
Casey:
And we will put a link in the show notes.
Casey:
This is just one example of many.
Casey:
Might have been the first example.
Casey:
I don't really recall.
Casey:
I didn't choose it.
Marco:
uh john writes the interface is all command line it doesn't try to manage your duplicates at all just gives you a list of duplicates in singletons and so this all stemmed from what was it marco it was trying to figure out when there were duplicates in tiff's photo library is that right yeah because basically like tiff's computer like over the years has evolved through a whole bunch because it's like one installation that's been carried forward for like a decade so it's evolved through a whole bunch of different photo management apps and solutions and archive drives and backup drives and everything else and so there's
Marco:
basically we think there's copies of photos kind of everywhere and i figured hey why don't we take the apfs free cloning feature and basically like find all these duplicates and replace them with apfs clones of one original that way the duplicates can stay where they are so we don't like you know accidentally lose things but they can at least uh you know not take up duplicate space uh that would be nice but uh yeah basically we got
Marco:
A whole bunch of people responding, almost all of whom had written their own scripts to do this.
Marco:
And my thinking after all that is, wow, I should write my own script to do this sometime.
Casey:
Of course.
John:
Yeah, the reason I put this one in the notes is because it doesn't try to do anything with them.
John:
And that's where the danger is.
John:
Like a lot of the other scripts, I mean, people would even say like,
John:
you know use it if you want i don't vouch it or whatever it's like finding the duplicates is great that's a read-only operation it's then deciding what to do where you can really hose yourself right i mentioned the metadata issues before but just the potential to destroy data is high so that's why any programmer looking at this might think of themselves like marco uh just said
John:
I should write one of these on my own, because at least when you write it yourself, you know exactly what it's doing.
John:
And if you hose yourself, you kind of, you know, have yourself to blame.
John:
I would not run any of these random things on here, which is why I link to this one, which doesn't do anything to your files.
John:
It just prints out the duplicates.
John:
And by the way, it's written in Rust, which I thought was novel.
Casey:
Oh, I did not notice that.
Casey:
My bad.
John:
.rs files.
John:
It looks like C++, but it isn't.
John:
Fun.
John:
Like Swift.
Casey:
Oh, that cuts deep.
John:
No, Rust looks a lot more like C++ than Swift does.
John:
Yeah, it's true.
Marco:
Swift tries to actually pretend like it's not C++.
Casey:
Oh, this looks a lot like C++, and I am not liking it.
Casey:
This has nothing to do with John's particular app.
Casey:
I'm just saying I do not miss the days of writing C++ for a living.
Casey:
Now I regret opening that.
Casey:
Moving on.
Casey:
A fan writes that PSA, iOS 12 now randomizes your music collection rather than simply selecting the first track in your collection when your car starts.
Casey:
I tried to find the episode where we were talking about this earlier tonight.
Casey:
I was trying to look it up.
Marco:
All you need to search for is a very good song.
Casey:
Oh, yeah, that's right.
Casey:
I forgot about that.
Casey:
I'll have to look again.
Casey:
Anyway, maybe somebody in the chat room can find it and I'll put it in the show notes.
Casey:
But what we were talking about was whatever is the alphabetically first song in your library, which is in some cases like the A-Team theme song, which I saw in this Reddit link we'll put in the show notes.
Casey:
Maybe it's like 10,000 Maniacs or some other numeral based.
Casey:
I think that comes first.
Casey:
It might not.
Casey:
It doesn't matter.
Casey:
One way or another, it typically ends up that you'll always hear the same song when iOS doesn't really know what else to play and you've started Bluetooth playback and it just has to figure something out.
Casey:
Well, apparently in iOS 12, it will just randomly select a song from your library.
Casey:
So I think the three of us can claim this as ours.
Casey:
I think this is our feature and you're welcome, everyone.
Yeah.
Marco:
I'm not sure that this is new.
Marco:
I started noticing, I don't know, six months ago or a year ago, that at least if you have Apple Music enabled on your iPhone, it would seemingly just play a stuff you might like kind of thing from Apple Music.
Casey:
Yeah, I'm not sure.
John:
I didn't confirm this.
John:
I put this link in there, but I didn't actually... Well, I don't know how I would confirm it.
John:
I have iOS 12 and an iPad, but...
John:
When I upgrade all my devices, I think I will be a good test case this because I continue to get fooled by it's like my pattern matching is not working with it.
John:
Like I'm, I'm a random, you know, random play shuffle person.
John:
Right.
John:
Um,
John:
And I, much to the consternation of everybody who was ever in a car with me, I want to want the play to be random, but I also want to skip if I'm not in the mood for that song.
John:
So it's basically like a radio station is like, how about this song?
John:
And I go, nah, not that one.
John:
How about this song?
John:
Nah, not in the mood for that one.
John:
Oh, that's a good, that's how I choose to do music.
John:
That's what I like.
John:
Don't, you know, don't at me as they say.
John:
I get enough of it from everyone in my family.
John:
You can't stand to hear me skip tracks.
John:
But anyway, the reason this comes up is because it takes me an average of like 5.7 tracks for me to figure out that it's playing alphabetically.
John:
Because it'll be like, I'm not in the mood for that one.
John:
I'm not in the mood for that one.
John:
I'll play that one.
John:
I'm not in the mood for that one.
John:
i'll play that one and then right about there i'm like wait a second all these tracks begin with the letter a my thing is hosed again and it very often happens because like the uh my ipod that i keep in the car for listening to music will go like uh thermally shut down and have to reboot and you know whatever it goes it forgets my state entirely and so it starts playing from the a's so if that never ever happens to me again i will know that whatever this random thing is working is but
John:
Rest assured, if this is not a real thing, I will skip my way through five A tracks before I stupidly realize that one of these songs begins with A.
Casey:
Well, you're welcome, everyone.
Casey:
And speaking of things that clearly we can take credit for, Marco, you've had your moment in the sun.
Casey:
Apple has announced a keyboard repair program.
Marco:
Yeah.
Casey:
Which is weird because they did the very, very non-confident thing of releasing this at like 5 o'clock on a Friday evening, which is not a terribly good look.
Casey:
Like, I understand it, but it does not imply a position of confidence or strength in any way, shape, or form.
Casey:
But basically, it says on the top of this article, which we'll put in the show notes, this is from Apple.
Casey:
Apple has determined that a, quote, well, this is my quote, small percentage of the keyboards in certain MacBook and MacBook Pro models may exhibit one or more of the following behaviors.
Casey:
Letters or characters that repeat unexpectedly.
Casey:
Letters or characters that do not appear at all.
Casey:
Or keys that feel, this is their quote, sticky.
Casey:
Or do not respond in a consistent manner.
Casey:
And basically for, what is it, four years total?
Marco:
Yes, four years after purchase.
Casey:
Then you can get your keyboard, either the key replaced or the entire keyboard replaced on any of the butterfly switch keyboards since early 2015 on the MacBook Adorable.
Casey:
So your congratulations are hopefully rolling in right now, Marco.
Casey:
So congrats.
Casey:
You have accomplished it.
Casey:
I expect to see you on an aircraft carrier with Mission Accomplished behind you any day now.
Marco:
Oh, God.
Marco:
Yeah, I don't take credit for this.
Marco:
One person complaining on a podcast is not going to make Apple launch a probably very expensive repair program.
John:
What about three people complaining?
Marco:
What about one person complaining three times a week?
John:
Does that change the math at all?
Marco:
Apple had to do this because it really is a real problem.
Marco:
Their number started showing, oh crap, this is a real issue.
Marco:
There was a pretty good discussion about it on Connected this week.
Marco:
What's interesting about it, I see two sides of this.
Marco:
One I tweeted about, which is
Marco:
Why only four years after purchase?
Marco:
There are some computers that Apple doesn't even update every four years.
Marco:
What do they think is the lifespan of a Mac?
Marco:
What I see, I mean, look, the computer I'm using is a 2015 computer.
Marco:
So I could have bought it then.
Marco:
It would now be almost three years old.
Marco:
It's still totally fine.
Marco:
And I expect after they make new ones, which we'll talk about in a second, and I will presumably buy one of those.
Marco:
And then sell it.
Marco:
And then I'll give this away to a friend or family.
Marco:
And then regret it.
Marco:
You know me so well.
Marco:
And then buy another one.
Marco:
And then buy another one.
Marco:
This one I have, a 2015 model,
Marco:
It's already 2018 and it's totally fine.
Marco:
I'm probably going to give it to somebody who's going to use it until 2021.
Marco:
How long does Apple think that laptops last?
Marco:
I have a feeling they know as well as I do that if there's some kind of critical flaw, because here's the thing.
Marco:
it covers you for four years after purchase.
Marco:
So you can, if you have a flaky keyboard, bring it in.
Marco:
They'll cover it.
Marco:
If you've paid for a keyboard repair on any of these butterfly keyboards, you can request a refund for that repair.
Marco:
But, like, I think four years is kind of cheap because...
Marco:
I know that they're going to be able to repair these.
Marco:
They're going to have the parts to repair these for more than the next four years.
Marco:
So I think they should actually extend it to the expected lifetime of a Mac.
Marco:
And I bet that's longer than four years.
Marco:
Anyway, so for this announcement itself, I think what's interesting about it is...
Marco:
It's one of the very few occasions where they've announced, basically they've admitted to a hardware flaw in a product line that not only is still for sale, but is still top of the line.
Marco:
All of their high-end and mid-range laptops.
Marco:
You cannot buy an Apple laptop today, except for the old models that are still for sale, but you can't buy a modern Apple laptop today that doesn't have this keyboard problem that they just admitted to.
Marco:
And nowhere have they said – we've had press people ask them – nowhere has Apple said that the new keyboards they're putting into these won't have the same problem.
Marco:
And I think the silence of that is deafening.
Marco:
People have asked them lots of other questions.
Marco:
They've been very forthcoming in answering questions from the press on anything except that.
Marco:
People have asked them and the press people have said Apple did not reply to that question.
Marco:
So it seems pretty clear what pretty much we all knew, which is this keyboard just has this flaw and Apple seems unable to fix it in this keyboard.
Marco:
Whatever the fix is going to be is probably going to be in a future model.
Marco:
So these computers are basically given a lifespan of four years.
Marco:
Even the one you buy fresh today after this has been announced has a useful lifetime of four years.
Marco:
And after that, it's just a huge risk.
Marco:
It could break at any moment and cost you $700.
John:
And keep in mind, during those four years, you may have to take it in any number of times to get it fixed for free, but still inconvenient.
Marco:
And people are saying who started to bring it in that they're being quoted repair times of like five business days without it.
Marco:
That doesn't make it okay to have these computers.
Marco:
Because if you are buying a $3,000 MacBook Pro and it maybe once a year or once every two years requires all of a sudden to be out of commission for a week to go get repaired, you probably can't afford to lose it for that long.
Marco:
And so anyway...
Marco:
I'm glad they did this.
Marco:
In typical Apple fashion, they admitted to a hardware flaw and started a repair program only very reluctantly, very late, and kind of are doing the minimum possible to kind of get out of it.
Marco:
But I do think it's interesting that they announced it.
Marco:
There was enough pressure on them to announce it before they have new models for sale.
Marco:
And we're all assuming that, you know, we all thought they were going to have them in June.
Marco:
The chips are out now.
Marco:
It seems like they should be able to have them.
Marco:
So hopefully this fall, I hope at the latest, an October event, we'll get these things.
Marco:
And I hope the next it may be the reason that laptops are now going to be a few months later than everyone thought.
Marco:
Maybe they pushed forward a design refresh that was maybe they were planning on having it start like next year, but they push it forward to this year because of all these keyboard problems.
Marco:
But I'm happy they did this.
Marco:
They could have done it better, but I'm not surprised they didn't.
Marco:
So what we have here is nice for people who own these computers.
Marco:
I still think it is the elephant in the room that these are the current models and that there is no keyboard for sale right now that Apple makes on a laptop that is now known to be reliable.
John:
Yeah, their statement of the problem is pretty damning.
John:
Not that they're doing the wrong thing.
John:
Again, they're doing the right thing finally, right, more or less.
John:
But the four-year limit, as you said, emphasizes the fact that Apple itself has no expectation that their fix will solve the problem.
John:
All it will do is start the timer again, right?
John:
That's why it's four years.
John:
That's why it's not forever.
John:
And look at the list of models, right?
John:
The eligible models are listed below, right?
John:
What they don't mention and what we all know is it's every single computer that ever shipped was a keyboard.
John:
Every variant.
John:
It's all of them.
John:
It's not like specific models.
John:
It's not just the 2017.
John:
So think of this.
John:
In 2015, you're excited by the new really, really skinny MacBook because you hate ports and you love lightweight things.
John:
and you get your 2015 laptop and it's got a wonky keyboard, you're going to wait three years before Apple acknowledges that there's a problem.
John:
And when they acknowledge it, it's going to go all the way back to your model and great, you can get your money back for your repairs or however many of them you had done.
John:
But this shows that
John:
Apple had this keyboard and just like, well, maybe there's problems with 2015, but let's soldier on.
John:
Like, as we said in many past shows, let's put this keyboard in every computer we make for every laptop we make for the next three years.
John:
Let's just keep doing it.
John:
The, you know, the 2016 MacBook.
John:
No, let's not change it.
John:
2017.
John:
Now make it a little bit quieter.
John:
The 13 inches, the touch bar is just we're going to keep using this keyboard.
John:
And it's just at no point that anyone say, wait a second.
John:
You know, they must have known surely by 2016 or early 2017 that there was a problem, but they just kept making computers with the keyboard.
John:
And part of that is just like the pipeline.
John:
Like, you know, well, we assume we would use this keyboard for the next three years.
John:
And, you know, this is a big ship and it takes a while to turn.
John:
But...
John:
It just honestly just doesn't look good, especially that they didn't have a new laptop hardware.
John:
Now, it seems like it was full steam ahead on all their laptops having this keyboard.
John:
And either they just couldn't bring themselves to admit that there was a problem or they learned there was a problem early.
John:
It takes this long to like turn things around.
John:
But it just it just it's not good, you know.
John:
if you wanted to if someone says oh what what laptop i should buy and we're all like oh all depressed about apple laptops like oh that's you're just depressed about laptops yeah i don't you know who cares you follow them too closely you're worried about small details this article from apple itself is the most powerful uh persuader of someone if you told someone now is not a good time to buy an apple apple this is why because no matter what you buy
John:
you know you are in for potential repairs and after four years you're on your own and the repairs are really expensive and there is no safe haven for the past three years all the new laptops have been like this so you know i kind of understand why apple would would want to hide this story but it's it's the most uh it's the most troubling and concrete evidence that now is not a good time to buy an apple laptop except for the 2015 model that marco has
Marco:
Yeah, it's – and I think if the explanation for this, which I'm sure will never actually be told, but if the explanation for this is truly that like, oh, it turns out in late 2015 after the MacBook 1 had been out for like six months, they realized, oh, these keyboards fail a lot but couldn't turn the ship around, as you said, John?
Marco:
and can't fix or replace or re-engineer a high failure rate critical component of their main computer for like three years, I think that signifies a pretty large problem in their process.
Marco:
It's not like Apple is strapped for resources here.
Marco:
And I know things take time, and I know things are complicated, but...
Marco:
That's a pretty major flaw to be not able to fix for three years for a company of their scale and their resources.
Marco:
If that is the explanation, that is unacceptable.
Marco:
And if the explanation is instead that it took them a while to realize it was a problem –
Marco:
then I think there was a huge problem in the pipeline somewhere because the users were realizing it in mid-2015.
Marco:
After a few months with those MacBooks, people said, you know what, these keyboards fail a lot.
Marco:
I even remember back when it came out, I remember hearing from a couple of little birdies that one of the problems with the MacBook, the very first one that came out, was that they had a lot of trouble manufacturing those keyboards and getting yields, which means that many of the ones they manufactured didn't pass...
Marco:
verification or didn't work or whatever else so like this was a problem back then why did it take them until apparently now to finally realize this or why have they not been why did they realize it earlier and have not been able to actually fix the products that they're shipping to people and that people are buying brand new and possibly having their first experience with an apple laptop like why why are they
Marco:
burning all these people for like three years something went really wrong in this process same thing like that with trash can mac pro same thing like that had all sorts of engineering problems that had the the gpu failure issue on that which by the way that was another example of a product that got a repair extension program while it was still the current top of the line product
Marco:
Which, by the way, it's still, I guess, technically, I guess the iMac Pro is now the top of the line product.
Marco:
But like, you know, that too, it had GPU failures from design flaws and GPUs would overheat and die.
Marco:
And that problem was never fixed in the trash can Mac Pro.
Marco:
It just is always a problem.
Marco:
If you have a trash can Mac Pro, your GPU is very likely to fail at some early point compared to the rest of the computer.
Marco:
And there's not much you can do about it.
Marco:
You know, same thing with the old Envida GPU stuff.
Marco:
Anyway, the problem of these laptops is so and this isn't even the only problem with these laptops.
Marco:
They also have like weird thermal issues where like the hinge will pop or other things will like kind of like metal will pop when it gets warm, even regular levels of warmth, like just being used.
Marco:
Uh, like metal keeps popping and things like that.
Marco:
Um, the USB C ports, at least in the 2016s had a lot of problems, especially the MacBook escape where like if you plugged in certain third party adapters, the wifi would cut out and stuff like that.
Marco:
Certain hubs just didn't work or they've worked only on some ports or work with only some things.
Marco:
Like there were a lot of problems in these laptops.
Marco:
And so I – in addition to the keyboard issues, like I think this points to larger problems with Apple's engineering quality control.
Marco:
Why did these things get out and then why are they taking so long to finally fix?
John:
So part of the human nature and, you know, Apple can do company is like focusing on the potential for like the yields being bad in the original ones.
John:
Like, oh, well, it's a product ramp.
John:
Like we just started making these.
John:
They're hard to make.
John:
Surely we're going to we're going to undertake.
John:
We're a smart company.
John:
We undertake a program to get our yields up.
John:
And I bet they did.
John:
I bet when they manufactured these keyboards in the beginning, it was really hard to get them to pass verification.
John:
And they had some metric that said, you know, X percent or failing verification.
John:
And they reduced that to like X divided by 20 and like, or, you know, X divided by a hundred.
John:
And now it's like practically all of them are perfect off the line.
John:
We did it.
John:
We made it better.
John:
Right.
John:
And the same thing with the, the, the failure is like the, you know, you're thinking, well, maybe if we modify it in some way and put those rubber gaskets, that'll help both with the sound and reliability.
John:
And we can't really tell until they get out of the field.
John:
And then finally, there's the money thing.
John:
It's like, well, some of them are failing, but how much is it really costing us versus how much would a repair program cost?
John:
And let's do the math and say, we'll just continue to... Is it actually hurting our customer satisfaction?
John:
Can we just afford to... Can we take this hit?
John:
What is the actual monetary cost?
John:
Not thinking, oh, they didn't know about the problem or didn't care.
John:
They knew and cared, but it was a question, what's the best thing to do about it?
John:
And it's potentially... Any big company is going to say, well...
John:
you know what do we care about here what matters do we care we care about customer satisfaction we care about money um so what's the best way to balance those two with this problem and only at a certain point does it tip over to say uh the the best way to deal with this is this repair program whereas every point before that when they did the math the best way to deal with it was just on a case-by-case basis and things are under warranty and so on and so forth so
John:
It's not good.
John:
You don't have to think that Apple is nefarious, merely that it's just made up of humans who have the same foibles as any other human.
John:
We hope Apple would be better and learn from this, but as the history of repair extension programs shows, this is kind of Apple's MO.
John:
This is how they handle issues like this.
John:
It doesn't seem to be evolving too much or changing.
John:
That's why we could predict, oh, here's what's going to happen with this keyboard, and it just happened again.
John:
That's how they deal with manufacturing problems.
John:
And the only real solution seems to be, and this is always a terrible solution of like, you know, when you do a postmortem, let's just be more careful in the future, which is not a solution to anything, but effectively is what they do with the phones.
John:
They have had problems with the phones, but...
John:
It's clear that they are much more careful about hardware problems with the phones, which are arguably more complicated and more difficult to get right than something larger like a laptop, just because everything is so small and crammed in there.
John:
And they have this huge manufacturing lead times because they have to make millions and millions and millions of them.
John:
And in recent years, they've been doing a pretty good job of not having any kind of catastrophic problem, even of this magnitude, with the phones.
John:
And that's extremely difficult to do, especially since the phones improve and get faster and are radically different, like the iPhone X and everything.
John:
So, you know, the final factor in all this might just be that...
John:
they pay more attention, spend more time and resources on the product that makes them more money.
John:
And so the Mac gets short shrift and a result of that is business as usual with hardware problems and how long it takes to get a repair program going.
Casey:
It was funny because this all happened, like I said, on Friday evening.
Casey:
Saturday, I'm using my beloved MacBook Adorable.
Casey:
And as I think I've said in the past, this keyboard, when it works, has actually won me over as my favorite Apple keyboard.
Casey:
I used to love the Magic Keyboard.
Casey:
I still do love the Magic Keyboard, the external ones.
Casey:
But this one, when it is working, is my favorite Apple keyboard.
Casey:
And as I'm typing something at my parents, it turns out one or two of my keys got sticky and was like not really working.
Casey:
And so I asked dad, hey, do you have any compressed air?
Casey:
What I forgot was that dad is an amateur mechanic and has a three horsepower air compressor in his garage.
Casey:
And so he said, yes, I do.
Casey:
And so we walked into the garage.
Casey:
How much do you need?
Casey:
Yeah, how much do you need?
Casey:
But it was kind of funny to me that this was the first time this had happened in a few months.
Casey:
And I needed to take compressed air to it in order to clear it out.
Casey:
And I did.
Casey:
And then the problem moved to another key.
Casey:
And then it went away a few minutes later.
Casey:
And it's just frustrating.
Casey:
And I hope that whenever the next laptops come...
Casey:
I hope that even if the feel of this keyboard has to change, and even if I personally find it worse, I too am annoyed enough by it that I would love to have a new keyboard design that is more reliable, even at the cost of what I consider to be an almost perfect feel.
Marco:
We are sponsored this week by Away.
Marco:
For $20 off your suitcase, visit awaytravel.com and use promo code ATP during checkout.
Marco:
Away makes really great suitcases at a much lower price compared to other brands by cutting out retail people and middlemen and selling directly to you.
Marco:
The Away suitcase are now available in over 10 colors and over five sizes.
Marco:
They have the carry-on, the bigger carry-on, a new bigger carry-on with a nylon pocket on the front of it, medium, large, and even a kid's carry-on so your kids can carry their own stuff.
Marco:
All of these have interiors with great designs such as a patent-pending compression system so you can fit a bunch of stuff in there.
Marco:
They have a removable, washable laundry bag to help keep dirty clothes separate from clean clothes as you travel.
Marco:
They have TSA-approved combination locks and four spinner wheels in the bottom, which is great.
Marco:
It's so much more maneuverable to have four wheels than you just have two.
Marco:
They also have additional options now.
Marco:
You can add packing cubes or garment sleeves to really customize your travel needs.
Marco:
And all this is backed by a great lifetime warranty.
Marco:
If you have any problems, if anything breaks, they will fix or replace it for you for life.
Marco:
And you can try it yourself.
Marco:
You can actually buy one of these suitcases, try it, actually travel with it, go somewhere with it for 100 days.
Marco:
If at any point you decide it isn't for you, you can return it for a full refund with no questions asked.
Marco:
And there's free shipping on any way order with them.
Marco:
They can take USUS.
Marco:
So there's really no risk to you.
Marco:
I'm seeing these everywhere now.
Marco:
When I travel now, I look through the airport and I see how many Away bags I see.
Marco:
I see tons of them.
Marco:
So many people have found what we found that Away is really cool.
Marco:
So check it out today.
Marco:
Once again, you have that 100-day free trial, that lifetime warranty.
Marco:
and these very nicely designed bags for very reasonable prices.
Marco:
For $20 off your suitcase, visit awaytravel.com slash ATP and use promo code ATP during checkout.
Marco:
Once again, awaytravel.com slash ATP and promo code ATP for $20 off your suitcase.
Marco:
Thank you so much to Away for sponsoring our show.
Ah!
Casey:
Marco, you were talking about this MacBook Pro as though you're using it right now.
Casey:
Is that what you're doing?
Marco:
No, TIFF's using it right now.
Casey:
Okay, but what are you using in general for your computing needs at the beach?
Casey:
Because last I heard, you got a super sexy carrying case for your iMac Pro and were treating that as your purse as you were walking around the beach.
Casey:
Is that not the case anymore?
Yeah.
Marco:
Alright, so I discussed last week how I had decided to bring an iMac to the beach, and I was probably going to bring my iMac Pro.
Marco:
And I had ordered a big fancy Gator case to carry it in a nice big padded way, and I was leaning towards bringing my iMac Pro, not like Tiff's old iMac that we were preparing to sell.
Marco:
And that's exactly what I did.
Marco:
I brought my iMac Pro.
Marco:
And to just give a brief review of this case, the case, the Gator case for the iMac Pro, or just for any 27-inch iMac, it actually is a really nice case.
Marco:
It is nicely made.
Marco:
It seems nicely padded.
Marco:
It has a bunch of pockets, like dedicated pockets for things.
Marco:
Like if you want to take the stock keyboard, mouse, and trackpad, it has dedicated pockets for those little icons on the outside.
Marco:
It includes a rain poncho cover.
Marco:
and a dedicated pocket just to hold the rain poncho when it's not in use.
Marco:
And it has a really nice strap.
Marco:
It makes carrying the weight as easy as it can.
Marco:
The downside is that the case itself weighs nine pounds empty.
Casey:
Oh, that is a lot.
Marco:
Yeah.
Marco:
The iMac Pro weighs about 22 pounds.
Marco:
So the combined weight, once you throw in the power cable, the mouse and the trackpad was about 32 pounds.
Marco:
And it's not small.
Marco:
So to have a, you know, pretty hefty 32 pound large rectangle hanging off of your shoulder...
Marco:
is very heavy and very awkward to carry for any length of time now i had to walk with it for about a half mile or so it was a hell of a walk it was not fun you have wagons for it don't you have wagons
John:
It wasn't up there.
John:
We had to walk.
John:
You should have waited patiently by the dock with your giant suitcase filled with either a body folded in half or an iMac Pro and had someone come back to you with a little wheelie wagon and then you could have wheeled it around like your beloved child that it is.
John:
Yeah, but the wagon that came with this house weighs... The wagon that came with the house.
Marco:
You were constrained by the wagon that came with the house.
Marco:
It's not a new, modern wagon.
Marco:
It seems like it was made before plastic or aluminum were known materials to work with.
John:
You feel like you shouldn't be constrained by the wagon that came with your house.
John:
You can get a new wagon, your car and your damn computer from, you know... All right, anyway.
John:
Anyway.
Marco:
How's your shoulder doing?
Yeah.
Marco:
my shoulder has recovered um but it was it was not comfortable um i i will say so you know this is not something i would ever want to do on a regular basis the the idea of like carrying this to panera or to a coffee shop or something or doing what that guy in that picture was doing even with the one that weighs a lot less and has the the foot hanging out flapping in the wind that's a completely ridiculous idea and i
Marco:
I can't see anybody ever actually wanting to carry their 27-inch iMac anywhere on a regular basis.
Marco:
But as a way to just like, you know, to do like large moves with it, to transport it infrequently, it did indeed work.
Marco:
There is actually a fairly humorous, unexpected bonus to this.
Marco:
Let me ask you guys a theoretical question.
Marco:
If you put your desktop computer into a bag and walked a half mile with it, what kind of surprises do you think might await you when you opened it up?
Casey:
A scratch screen?
Casey:
I would hope not.
John:
I mean, yeah, if you got any kind of grit in there that it's going up and down on.
John:
But I'm trying to think of if there's anything that can fall out of your computer.
John:
Yes, there is.
Marco:
what was i mean i don't know that the logistics of the case but is like are all the peripherals like separate in separate pockets like nothing is mixing in there with it right yes all the peripherals are in separate pockets it is nicely you know padded and isolated but something did indeed fall out of the computer spiders large blobs of dust
Marco:
Oh, gross.
Marco:
Because the iMac Pro intake vents are on the bottom edge of the screen facing down.
Marco:
I didn't think of this.
Marco:
Before I put it in, I dusted off the back, the foot.
Marco:
I dusted the whole outside of the computer, but I didn't run a towel under the lip of the bottom edge.
Marco:
So I open it up when we get to the house and I open it to make sure everything's okay.
Marco:
And I'm like, what the heck is all that stuff at the bottom?
Marco:
sure enough pringles dust yeah yeah lots of dust blobs that fall out of my computer on the walk can you imagine if you were walking with like a like a cheese grater mac pro tower like all the dust would fall out of that yeah the dust in my mac pro is structural now though it's load-bearing dust yeah it's yeah those things those things are quite impressive with their dust anyway so
Marco:
I am ultimately, though, you know, so even though it was kind of ridiculous getting it here and it's going to be equally ridiculous getting it back, I am really happy I brought my iMac Pro because I am getting tons of work done here.
Marco:
And it's really, you know, this is what everyone always says about laptops.
Marco:
It's really nice having all of my files and my apps already here and set up the way I want and everything.
Marco:
Like, I know how everything is going to behave.
Marco:
And I'm doing an unexpectedly large amount of work this summer, very heavy work that is maxing out my cores and my screen space, which is basically remaking from scratch the overcast Apple Watch app.
Marco:
I don't want to spoil anything or pre-announce anything yet, except to say the overcast Apple Watch update this fall is awesome already.
Marco:
And it's not even July yet.
Marco:
It is almost done.
Marco:
I mean, I'm just at the polishing stage now, but I am now taking walks every day with standalone watch playback of podcasts.
Marco:
And it is fantastic.
Marco:
It works.
Marco:
Apple finally gave me what I need to make this good.
Marco:
And I've made it.
Marco:
And it's almost done.
Marco:
It's basically done now.
Marco:
I'm going to start the beta pretty soon, I think.
Marco:
It is so good.
Marco:
I'm so happy.
Marco:
I've taken the opportunity that they gave me, that standalone audio now works, to also revamp some other parts of the watch interface.
Marco:
And so it's really, really good.
Marco:
And it's way better than the watch app I had before.
Marco:
And back during that brief period where I had offline playback, it's way better than that was.
Marco:
So I'm very, very happy with this.
Marco:
I'm feeling really good right now about this.
Marco:
And I'm so happy I brought my iMac Pro out here.
Marco:
Every time I'm doing some kind of big build,
Marco:
And I look up at my iStat menus, and I see all 10 cores pegged for a little while.
Marco:
I'm like, yep, this was the right decision.
Marco:
Even right now, as I talk to you, and I'm not hearing fan noise from a laptop somewhere that's working like crazy just to drive the screen.
Marco:
I'm really happy I didn't buy the Dell 24-whatever-whatever 4K display and use that on my 2015 laptop because that wouldn't have been enough screen space.
Marco:
As...
Marco:
As Casey, you know, and as many of our listeners know, iOS development burns screen space, as I mentioned last week.
Marco:
So the last thing you want is significantly less screen space when you're having an iOS development-heavy summer.
Marco:
So I'm really glad I brought this computer.
Marco:
I'm doing tons of work on it.
Marco:
This is a very work-heavy summer for Overcast.
Marco:
And I'm really, really happy with how the watch update is turning out.
Casey:
You're the only person I know that does his work while he's at his vacation home.
Casey:
You can't do work at your actual home.
Casey:
You have to go to your vacation house in order to get work done.
John:
I think it stops being a vacation maybe the second month that you're there.
John:
Like this vacation in there is here's where we live during the summer.
Casey:
Fair point.
Casey:
Fair point.
Marco:
I, I don't really take like for me, like vacation to me ends after like four or five days at most.
Marco:
Like that's, that's about as long as I can go on vacation.
Marco:
Then I'm like, I have to turn my brain back on now.
Marco:
Like I, I just, I can't, I can't let my brain just like stagnate and jello forever.
Casey:
Now, what about your HomePod situation?
Casey:
What's going on there?
Marco:
That's another thing that I've come to appreciate here.
Marco:
I brought both of the HomePods here because I figured... You had that big carrying case with two more HomePods strapped to your hat.
John:
They're heavy.
John:
Balance on your head like a water jug.
Marco:
Like beer cans.
Marco:
HomePods are ridiculously heavy.
Marco:
I bought the two at first.
Marco:
I bought two at a time.
Marco:
And just carrying one in each hand in their little square bags back to my car...
Marco:
which required you know maybe a quarter mile walk like that back to like the parking garage they were really heavy i was like damn like these handles are digging into my hands and they're filled with all that bass
Marco:
Oh, that's great.
Marco:
Anyway, so I now have had a lot more experience using the HomePod, not just as my computer speakers, but now I brought them here for the summer to test with, but I'm not doing AirPlay 2 stuff yet.
Marco:
I'm still in the Watch app, so I just put them out in the living room.
Marco:
One's kind of off the side of the kitchen, one's in the living room, still has a big stereo pair because it's kind of one big room.
Marco:
I've got to say, I really like the HomePod just as a music speaker that's in your living room.
Marco:
It is really good.
Marco:
As other viewers have mentioned, it hears you from great distances at very low speaking volumes, and you can talk really fast, and music can be playing.
Marco:
There can be a song playing at moderate volume, and I can say from 20 feet away, hey Siri, stop.
Marco:
And it does.
Marco:
I'm amazed how well it hears me.
Marco:
And I don't have to really try hard for it to hear me.
Marco:
This is something that... I have a lot of experience now with the Amazon Echo family of products.
Marco:
And the Echo hears you decently.
Marco:
But this is another league.
Marco:
In both...
Marco:
the consistency of how it hears me like how often it hears me and in what conditions it hears me with with the echo the echo hears pretty well when there's not a lot of noise but if there's really any like room noise you got to be pretty close for the echo to hear you and also if music is playing um whereas the home pod really beats it in that um i'm still not thrilled with siri of course um
Marco:
The intelligence of Siri is not that much of a problem in the context of using it as a music speaker so far.
Marco:
The thing that really bugs me is that it's so verbose in its response.
Marco:
It's just like, again, just like Siri everywhere else.
Marco:
But when you're used to the Echo where it's just like, okay, and it just goes.
Marco:
Siri is so verbose in what it says back to you.
Marco:
Unnecessarily so.
Marco:
It's almost like it's trying to be your friend.
Marco:
I don't want to be your friend, Siri.
Marco:
I just want you to say okay and move on.
Marco:
You aren't a human.
Marco:
But otherwise, as it stands right now, I would say, you know, in the kitchen, no contest.
Marco:
The Echo is still the device to have.
Marco:
But, you know, Siri could add just one feature to almost completely close that gap.
Marco:
multiple named timers why that feature is not there yet even after wbc everything is beyond me i have no idea what so i my only assumption is that maybe they're maybe they're going to mention the home pod in the fall event maybe give it some kind of small update or price drop or something and maybe they'll announce it there who knows but like multiple name timers i don't think this should be very difficult
Marco:
I really hope they add that soon because that could close the gap for how good these are in kitchens really well.
Marco:
Also, I've had a little more experience playing music on the HomePod since then, not from my computer but from everywhere else.
Marco:
AirPlay 2 and the integration it has with Control Center on iOS and the music app on iOS is actually really nice.
Marco:
you can use voice to control it, but you can also just like, you know, control it from your iPad or from your iPhone because when you force pushing in the music thing on Control Center, it pops down and you can see like one of the entries in there is whatever's going on in the HomePod right now.
Marco:
So any device on your network can control that and can change it to be what they want to be playing.
Marco:
And that's just really, or you can just do simple things like adjust the volume by your finger instead of saying, you know, hey thing, volume 25 or whatever.
Marco:
It's really very nice.
Marco:
Built-in integration with iTunes on the desktop, as I mentioned last week, is pretty crappy, but is sometimes convenient.
Marco:
Once you figure out that weird thing, you have to drop it down and scroll down past the separate entries to get to the combined one, which is kind of weird.
Marco:
And one other major area that the HomePod is way better than both the Alexa family of products and also the Sonos family of products
Marco:
is if you have your own music collection that you want to play from.
Marco:
I tried.
Marco:
I've had all these products.
Marco:
I've had Sonos.
Marco:
I've had Echoes.
Marco:
And I have tried Amazon's thing first to import my music from my computer.
Marco:
I paid for their weird upload thing, which I think they have just discontinued.
Marco:
With Sonos, I installed their Mac software and it indexed my library and had to play off that and everything.
Marco:
Both the Amazon Echo and the Sonos systems for playing your own collections are buggy as hell and basically unusable.
Marco:
They effectively don't work.
Marco:
I don't know if anybody actually uses them, but they're total garbage.
Marco:
So if you want to play things out of your own collection...
Marco:
the HomePod is where it's at.
Marco:
Because you can literally just ask for things by voice or start playing something on your iPad so you can pick exactly which Phish performance you want to play.
Marco:
And it just does it.
Marco:
And then you have the voice interaction for that music of yours.
Marco:
It's really nice.
Marco:
And it's something that the other players really don't do.
Marco:
So that's pretty nice.
Marco:
Overall, I really do like it a lot for music.
Marco:
There are the caveats that...
Marco:
It doesn't have good support for things like Spotify or other services like that.
Marco:
So if you need a speaker that is probably not in your kitchen, and you can probably afford two of them at $350 each, because it really does, like if your room is larger than a small room, if you have like a medium or large size room, you're going to want two HomePods to fill that room.
Marco:
So if you fit into this very narrow case of like,
Marco:
you don't mind spending $700 for a pair of them.
Marco:
And also, it's not going in your kitchen, you don't need timers.
Marco:
And also, you either want to play your own music collection from iTunes slash Apple Music Cloud and everything, or you're an Apple Music subscriber, then the HomePod is really great.
Marco:
But if any of those things aren't... Oh, and also, you also don't need these $700 pair of speakers to have inputs from your TV or anything.
Marco:
And so...
Marco:
With all those caveats, it's really nice.
Marco:
Fortunately, there are a couple of places in my life where this is nice, like here, for instance.
Marco:
I'm looking forward to how Apple matures the HomePod product line.
Marco:
I really hope they put some resources behind it.
Marco:
I hope they don't just Apple TV it and just half-ass it forever.
Marco:
It really could be great.
Marco:
It's already getting there, but there are some shortcomings here and there, some limitations here and there, some of which can be solved by pricing or hardware updates, some of which are just kind of fundamental things like Siri.
Marco:
But it's really nice if you fit into that very narrow set of needs and resources.
John:
You just better hope they don't iPod hi-fi it.
John:
Forget about Apple TV, half-assing it for a few years.
John:
How about just, nope, we never make another one.
John:
Big mistake.
Marco:
Yeah, I thought about that, actually.
Marco:
I really hope they don't do that.
Marco:
But, see, this is the kind of thing that I see Apple actually doing pretty well.
Marco:
Because, you know, it's kind of like, you know, AirPods being a big thing.
Marco:
AirPods are a way for Apple to flex...
Marco:
really over-the-top hardware engineering and industrial design without having to worry about pesky UI design.
Marco:
Because UI design is hard, and app platforms are hard, and all these things that plague the Apple TV, those are hard.
Marco:
Those are big problems over time.
Marco:
The only hard problem about the HomePod that Apple needs to work on over time is the quality of Siri.
Marco:
And again, that is hard.
Marco:
It is certainly a larger impediment to the HomePod than it is to the AirPods.
Marco:
but this is also a case where like apple can sell the same household a lot of these things and they can update them over time and sell them even more and they can change the shape or the size or the input situation and sell them to their existing customers again and so this is actually the kind of thing apple does pretty well these days like apple does like
Marco:
fancy over-engineered over-designed hardware with no ui and that you that you can make 300 from all of your customers with every couple of years like yeah apple's pretty good at those things now
Marco:
We are sponsored this week by Linode, my favorite web host.
Marco:
Go to linode.com slash ATP to learn more and get a $20 credit.
Marco:
Linode is, frankly, a great web host.
Marco:
I have been with a lot of web hosts in my day.
Marco:
I think I started buying web hosting in about the year 2000.
Marco:
Like, no numbers after it, just 2000 with all zeros after it.
Marco:
So it's been a while.
Marco:
I've been with a lot of different web hosts, lots of different types of web hosts.
Marco:
And Linode is the one I've been with the longest.
Marco:
I think I've been with them for about eight years now.
Marco:
I've stuck with them the longest and I've slowly moved all of my stuff to Linode because it's just nicer than everything else I've used.
Marco:
The services are great.
Marco:
The pricing is incredible.
Marco:
The prices start at just $5 a month for one gig of RAM.
Marco:
Now, when I first signed up, I think I was paying something like $50 a month for like 128 megs or something like that.
Marco:
But back then that was a great deal.
Marco:
But today it's an even better deal.
Marco:
I've never found a better value on an ongoing basis in the web hosting business.
Marco:
Sometimes somebody else will tie them for a little while, but then six months later, Linode beats them.
Marco:
It's such a great service.
Marco:
They have all sorts of features that you might need.
Marco:
Backups, load balancers, stats services.
Marco:
They have a full-blown API that you can use to script the creation and resizing and configuration of instances.
Marco:
So you can have a whole complicated application that automatically scales if you want to.
Marco:
All of this is running with native enterprise-grade SSDs, a 40 gigabit network, and my favorite Intel Xeon E5 processors.
Marco:
There's so much more to recommend about Linode, but what you need to know right now is that plans start at just $5 a month.
Marco:
They get you one gig of RAM in the Linode cloud.
Marco:
They have all sorts of bigger and better plans above that if you have higher needs than that, although you can do a lot with that, honestly.
Marco:
You can get your server running in under a minute, and all of this has a seven-day money-back guarantee.
Marco:
So try it.
Marco:
You have nothing to lose.
Marco:
If you need a web host, Linode is the place to go.
Marco:
Go to linode.com slash ATP and see for yourself why I love it so much.
Marco:
You get a $20 credit with that link, and so if you only use that $5 a month plan, that could be four free months.
Marco:
Once again, seven-day money-back guarantee on that.
Marco:
Thank you so much to Linode for keeping all my servers running for so long, for at least eight years now.
Marco:
I love Linode so much, and for sponsoring this show.
Casey:
Let's talk Marzipan.
Casey:
We've kind of made brief mentions of this in the last couple of shows, but the end, it was the end, right, of the WWDC keynote was all about this technology which was never really named, but was about bringing iOS apps onto the Mac.
Casey:
And the general gist of it is UIKit on the Mac, which is something that we as a community have been wondering, hey, is this a thing?
Casey:
Could this be a thing?
Casey:
Would this be a thing?
Casey:
And this was in no small part...
Casey:
um inflamed by or or spurned on by the discovery of ux kit which apparently was this sort of a thing but it was for just photos is that right on the mac um it was just one or two apps that were using this thing called ux kit that apple apparently had written as kind of like a shim between um you the the app written for ui kit and an app kit which is what you use on the mac um
Casey:
So there's been a lot of chatter about Marzipan, what it means, where we're going to go from here.
Casey:
And I'm not I'm not sure what we don't really have like a narrative arc with the stuff in the show notes.
Casey:
So I'm just going to start picking it off one by one.
John:
Don't do that because I have a narrative arc.
Casey:
Okay, perfect.
Casey:
John, take me on your narrative arc.
John:
Yeah, there is a bunch of random stuff in the notes, but there is an arc, an overall arc, at least as far as I'm concerned.
John:
So, yeah, we talked about this at WWDC and haven't talked about it much since.
John:
And part of that, at least for me personally, is that I've been kind of like...
John:
ruminating on it right like i didn't i didn't want to i didn't want to rush to judgment and i needed some time to sit with this and just really think about what this is going to mean i think maybe i mentioned on the wwc episode potential parallels uh with carbon and coco which were the two apis for making mac os 10 applications uh back when mac os 10 was launched
John:
carbon came from the classic world and was a bridge to the classic world and it was an evolution of the classic mac toolkit and all that stuff and coco of course was the next stuff and apple spent a lot of years with both apis a lot of wwcs were like we introduced a new control and it's only available in coco or only available in carbon or last year this thing was only available on either carbon or coco but now it's available in both or now we're going to update them in parallel and then eventually it evolved to you know what just
John:
not so much carbon anymore.
John:
Everything new is going to be in Cocoa, and eventually carbon doesn't even make it to 64-bit, and eventually we crown a clear winner, which is Cocoa.
John:
Say goodbye to carbon.
John:
But that took many, many years.
John:
And thinking about the marzipan stuff, I know lots of people have been discussing this.
John:
I didn't know how I felt about sort of my gut instinct towards, you know, who is in the battle of marzipan, the battle of UI kit versus app kit.
John:
uh is one of them a carbon and one of them is a cocoa or does that analogy not fit and neither one is fits neatly into many of those slots and the historical precedent doesn't make any difference like but what does this do um so i kind of have been setting aside the carbon versus cocoa thing and start thinking more in terms of
John:
uh animals and nature and like invasive species and somehow that got its hook into my brain i really hope some other podcasts didn't already use the exact analogy i've been consciously avoiding reading and listening to anything having to do with this topic just to give myself time to stew with it but
John:
I keep thinking of UIKit on the Mac as like... I'm probably going to make a bunch of bad analogies based on half-remembered things from popular movies.
John:
Like introducing rabbits to Australia or bringing some invasive plant or fish species into North America that wasn't previously here.
John:
Or such as situations where you...
John:
You have an ecosystem that is what it is, and you bring some unexpected item into the ecosystem, and it's not equipped to deal with that, whether it's a predator that starts eating everything or a prey animal that reproduces very quickly or a plant that can grow in more harsh condition that totally shuts out all the other plants.
John:
Those are all sort of like thinking of it as a bad way.
John:
But just that I feel like the Mac ecosystem as it exists today, the Mac software ecosystem,
John:
is not like dropping ui kit into there is going to have a big effect right because the ecosystem itself is not it's not prepared for that it's not it's not strong the mac software market is not the powerhouse that it once was uh certainly nothing compared to the ios app ecosystem right and
John:
There are way more iOS developers than there are Mac developers of any stripe.
John:
That will seemingly continue to be the case.
John:
And you're going to drop UIKit onto the Mac.
John:
And I'm trying to think of any scenario in which this doesn't spell doom for AppKit users.
John:
and traditional mac application is not written in some thing that is derived from ui kit and that sounds like overblown right it's like that that's why i've been thinking about this for a while just like you know that's your gut instinct but you know come on marzipan is some weird separate process that like variant of the ios simulator that takes your ios applications and run them in little windows how is that a threat to like real native mac applications they're nothing like native app they don't look like it they don't behave like it
John:
They have their own little engine running with their own little version of iOS.
John:
You can't even mix AppKit with them.
John:
How is that a threat to anything having to do with the Mac?
John:
Kind of like introducing that one weird snail or rabbit or, you know, vine species.
John:
Seems like it's not going to be a big deal.
John:
Uh...
John:
But then fast forward a couple of years and all of a sudden you realize you've made a terrible mistake.
John:
And suddenly Marzipan is out of the little iOS system support thing.
John:
And applications are able to link against both AppKit and UIKit and mix and match them within the same application.
John:
And the frameworks are just loaded as normal.
John:
And the UIKit variant for the Mac starts having the ability to use more Mac-like controls and spawn new windows and do toolbars and all the other things that the Macs can do.
John:
and i mean this is where i'll throw it to you guys am i being too uh pessimistic do you see a scenario in which app kit long term not like this year next year but app kit can survive a successful invasion by ui kit on the mac platform
Marco:
What if, you know, if you look at like, well, there's the native way to write apps with AppKit, and you can make the best quality apps with that, that have the most native system behavior, the most system integration, feel the most, you know, quote, Mac-like.
Marco:
But there's also then this cross-platform thing that you can write apps for that can run in the same system.
Marco:
Won't everyone just start making apps for that?
Marco:
Won't it mess up the conventions?
Marco:
Won't it do things like that?
Marco:
And you could say the same thing about when web apps became a thing.
Marco:
We already have a cross-platform system where things that are kind of app-like run in kind of Windows with this kind of cross-platform language.
Marco:
They're called web apps.
Marco:
And so maybe the effects could be similar to that, which is... And I think the economics are similar to that, which is the people who are real Mac enthusiasts or are real hardcore Mac developers or are companies that have the resources where making a native Mac app make sense will continue to make AppKit apps.
Marco:
But there's this other thing that in the past has been web apps, and now could be the iOS unified code base with Mac and stuff, where if they don't have the resources or don't want to spend the resources to make an AppKit app, they're going to make one of these cross-platform apps.
Marco:
And in the past, that was the web app.
Marco:
In the future, maybe it'll be Marzipan app also, or instead.
Marco:
So I think the effects of it could be seen similarly to the effects of what web apps have done to the platform, which is, yeah, we're going to see a lot of them.
Marco:
A lot of things are going to be Marzipan only on the Mac.
Marco:
They're not going to have native Mac apps.
Marco:
And it is going to mess up some stuff.
Marco:
But I don't think it's necessarily a massive threat to the platform anymore than web apps and the economics of cross-platform development have been.
Marco:
That being said, it depends a lot on the implementation.
Marco:
It depends a lot on how good are these apps?
Marco:
How usable are they?
Marco:
Is it like web apps where they can be functional but that they always kind of feel a little bit off?
Marco:
in the environment, that they never quite feel like Mac apps, that they never quite feel right, you can always tell it's going to be like that, or are they going to add enough functionality to them that you can actually make one pretty well that you kind of don't notice, that it's not a quote real Mac app or not a Napkit app.
Marco:
The other thing to consider is that AppKit, as you mentioned, it's not in a good place right now.
Marco:
The ecosystem is not in a strong place right now.
Marco:
It's really very vulnerable to attack because it's been just beaten down by iOS and general neglect and cross-platform frameworks over the last 10 years.
Marco:
maybe it's time for AppKit to go the way of Carbon.
Marco:
I don't know.
Marco:
I don't think it is yet, but I think that time is not that far off if it's coming.
John:
I want to address your earlier point about comparing to the web stuff, although I think you could probably argue against your own point if you stood on it a little bit.
John:
But there's some prerequisites for that to happen.
John:
And one of the prerequisites is that
John:
UI kit.
John:
That's why I mentioned Mars Ben, we, the weird thing that it is now that the UI kind of the Mac stays as like, Oh, it's a way to get iOS applications to get in your Mac, as opposed to it evolving into the new way to write Mac applications.
John:
Again, we're far from that now with the demos that we've seen and with the stuff that Apple's running in Mojave.
John:
Right.
John:
But my assumption based on all the conversations and all the information I was able to glean from being at WWDC and putting my ears to the ground or whatever, is that
John:
The current weird implementation of Marzipan and Mojave is not representative of the long term vision of how this is supposed to work.
John:
It is merely what had to be done to make it happen in this time frame.
John:
And.
John:
On top of that, I feel like once you're out of this weird.
John:
you know, implementation of Marzipan and into a more like, oh, I just link against UIKit in my application.
John:
I don't see any reason for Apple not to continue to evolve UIKit on the Mac in a Mac-like direction.
John:
They already have.
John:
They added a bunch of classes to UIKit when it runs on the Mac to be able to do things like have a menu bar, which you can't, you know, there's no menu bar on iOS, right?
John:
There is in the Mac ones.
John:
They added classes to UIKit.
John:
That makes me think they're not going to leave UIKit as a cross-platform thing.
John:
They're going to try to make it into
John:
the new way to write Mac applications.
John:
And the biggest difference, the two biggest differences between this and web stuff is one, it really is actually native.
John:
It's not a web view.
John:
Like it is as native as native can be, right?
John:
And two, Apple is using it
John:
to make its own applications that's one of the few things we can pull from the notes here right so we have the four demo applications which are ios supports right but there are a bunch of applications on the mac that are extremely likely candidates for a marzipan uh conversion so just one example that that has you know existed for years and i feel like it's got to be right up there in the list is messages on the mac which does not have feature parity with the ios version
John:
Despite being written in AppKit and despite Apple presumably having AppKit developers, the easiest way to get feature parity for messages on the Mac is to replace messages on the Mac with messages from iOS tweaked to be a Marzipan app.
John:
That is way easier than, you know, adding the features that are in the iOS version to the AppKit version on the Mac.
John:
And by the way, speaking of web views, it's my understanding that the message list that you see in messages on the Mac is, in fact, a web view, which explains why it might be difficult to implement, say, the laser beams or any of the other special effects.
John:
Yeah, maybe they use WebGL, but then the thing would probably crash.
John:
There are lots of applications like that, that on the Mac do not have feature parity with their iOS counterparts, and the Mac ones are written in AppKit.
John:
Apple will ship UIKit versions of those applications, whereas Apple would probably never say, we're replacing messages with an Electron app.
John:
We're replacing messages with a WebKit view, and it will be entirely web-based.
John:
We're replacing pages with iCloud.com's version of pages, and it's just a giant web view.
John:
Apple would not do that.
John:
Apple will do that with UIKit.
John:
They will be native.
John:
And, you know, if if Apple continues to pursue that type of strategy and doesn't just say this is just a way for you to quickly port your iOS application to the Mac, again, I see it as an extinction level event for AppKit, which I don't.
John:
And I'm not making any technical judgments like you mentioned, like maybe it's time for AppKit to go.
John:
I don't know.
John:
Like, I don't have experience writing applications.
John:
These are one of the things I have.
John:
I have no idea what the pros and cons are and understand.
John:
Obviously, AppKit has more cruft and so on and so forth.
John:
But.
John:
I mentioned all those months ago that, like, we don't know what Apple's opinion of, like, what is the best thinking about how to make a GUI application?
John:
And to me, the Marsman effort makes me think that Apple thinks UIKit, what we've been doing in iOS, that's our current best thinking on how to make applications for any platform where you have a GUI.
John:
And there's a GUI on the Mac.
John:
And so the best way to make Mac applications will be
John:
a variant of ui kit extended with classes that do mac specific things and you know granted this implementation is weird but slowly over time we'll expand it it will be very native if anything it will be you know it has the potential to be faster than app kit because it's things that were originally designed to run on a phone uh and it has more modern thinking it takes advantage of more modern hardware yada yada anyway casey what do you think
Casey:
So I think I have an optimistic view of this.
Casey:
I think that UIKit kind of appearing on the Mac is Jeff Goldblum uploading his virus into the Independence Day alien spaceship.
Casey:
Spoilers.
Casey:
Spoilers.
Casey:
Yeah, I know, right?
Casey:
I do think that it is quite likely that that is going to be the first step in the either death or significant reworking of AppKit.
Casey:
I don't think you're wrong to see that as a potential, if not inevitable, end.
Yeah.
Casey:
The difference between the way I think you're thinking of it, John, and the way I think of it, though, is that I do think that Apple believes that UIKit is their best and greatest approach to GUI development.
Casey:
And I think that...
Casey:
it could very well be that UIKit coming to the Mac today seems like it is very, not even half-baked, like quarter-baked.
Casey:
But that's why it's a preview.
Casey:
And it's not, well, with the exception of the four apps that they're shipping.
Casey:
But it's in general a preview.
Casey:
And that's why we don't really have access to it, except for what Steve Troutensmith and Mr. Rambo himself, if you please, have been doing to kind of make this work anyway.
Casey:
But
Casey:
I feel like and I hope that if AppKit does have to wither and die, that this new Marzipan, you know, it's UIKit, except it isn't, will expand in such a way that it will embrace all the unique things that makes a Mac a Mac.
Casey:
It will embrace the menu bar in a way that maybe it isn't doing today.
Casey:
It will embrace a preferences window in a way that maybe it isn't doing today and so on and so forth.
Casey:
Because if you look at the way things are today,
Casey:
As someone who really loves the Mac, and I really love the Mac, and I don't know which one of the three of us loves it the most, doesn't really matter, but I love it a lot.
Casey:
It's me.
Casey:
It's probably you.
Casey:
But either way, I mean, Marco and I can fight over second.
Casey:
It's me.
Casey:
Fine.
Casey:
As the guy who hates the Mac on the show, I really love the Mac, and I feel most at home on the Mac.
Casey:
And I don't want the Mac to change, and I change in ways that are unfamiliar and scary.
Casey:
But I do think that this very well could be a time where this change is healthy and it will be for the best.
Casey:
Now, I can give you a million and seven ways where this could go all kinds of pear-shaped and terribly wrong.
Casey:
And where we only get half-baked apps, it's basically the second coming of Electron, it's just mildly less offensive.
Casey:
We get apps that are clearly a five-minute port from iPad or iPhone where the menu bar is just an afterthought and so on and so forth.
Casey:
There's a million ways where this can absolutely go wrong, and we will be really, really, really sad pandas.
Casey:
But there's several ways, I think, where this can go right.
Casey:
And I think that for now, I'm going to choose to be optimistic and think that, you know what—
Casey:
This isn't 100% there today, but it may be 100% there in a year or in a couple of years or in a few years.
Casey:
And anything that I can do to get more native, not Electron apps onto the Mac, I think is a win.
John:
I'm on the same page with you with the extending.
John:
Like I said, they already extended it with menu bar stuff.
John:
I...
John:
truly believe that if things go according to apple's plan when you know and plans change that they will improve ui kit on the mac they will add even more classes to extend more functionality like that their goal is not just to make ports and we will get the shovelware 100 we'll get the shovelware there's no there's no avoiding that and there'll be a long period of time before ui kit on the mac can match all the features that are available to app kit but it just like to do the reverse of it just fit to figure out like you know
John:
Can you envision the opposite, where UIKit and AppKit continue to march along, each one of them being enhanced and improved long term?
John:
I can't envision that scenario.
John:
Obviously, AppKit's not going to disappear.
John:
There's a huge legacy code base that will continue to work for a long time.
John:
Gus Mueller, creator of Acorn and many other great pieces of software, had a good piece on trying to figure out how Apple...
John:
could ever leave app kit behind and he pointed out that the the place the convenient place that apple has frequently dropped frameworks and stuff has been architectural changes whether it's from 64 bit to 32 bit or power pc to intel or 68k to power pc those are great inflection points to be able to finally drop the legacy framework or the you know
John:
drop support for all the things that you previously could never get rid of because people are doing big changes anyway and it kind of makes sense to people.
John:
That's how they got rid of Carbon.
John:
They couldn't get rid of Carbon until 64-bit came along because if some point before that they had said, yeah, we decided Cocoa won.
John:
We're not going to do Carbon anymore.
John:
They'd be like, but wait, we ported Photoshop to Carbon.
John:
Office isn't Carbon.
John:
The Finder isn't Carbon.
John:
Like, what are you even doing?
John:
You can't do this.
John:
And it's like, okay, how about this?
John:
How about when we go 64-bit?
John:
That's the time we'll drop.
John:
although we'll completely develop carbon 64 and just change your mind at the last minute like and i think that was probably a wise decision whoever made that call probably was like we really dodged a bullet there because otherwise they'd still be supporting carbon and we'd still be running carbon applications so how can you get rid of app kit uh gus is saying hey when the arm max come out that's a perfect time to say well coco's not coming to arm uh you know we'll have some sort of emulation solution or whatever the heck we're gonna do
John:
but you know i mean depending on the timing of these things that may not work out because you can't you can't drop coco until ui kit on the mac is way better than it is now right but you know the only way i can see this this going app kit surviving long term is that it has to win this ecosystem battle that it would be like okay we tried marzipan and it turned out not to be a big thing and we were going to take a different approach like they change their mind or they bail out or they say like oh it's just a way to support ios applications and
John:
but we're not committed to we were we were on that path of like we're going to keep enhancing and make it the great new mac framework where we decide now we're not going to do that and that would leave room for say okay well app kid is still king of the hill because its competitor ran away right that's you know i feel like that's the only way that app can continue and as for optimism and pessimism like the shovelware stuff aside which is going to be gross but still better than electron like we're going to have to live through that no matter what i'm not entirely sure like i don't i don't have enough
Thank you.
John:
you know, knowledge or experience of developing applications to say whether like, I know everyone loves UIKit and there's tons of UIKit developers.
John:
People who never learned that could think UIKit is better, but there's also a lot of people who I know and respect who think AppKit is pretty great.
John:
And I'm wondering like, you know, is this good or bad net net?
John:
Obviously like technology aside, it's good because like there's tons more iOS developers and it's, you know, the more popular platform and so on and so forth.
John:
But technology wise, part of me wonders if,
John:
you know if if the early our earlier discussion tomorrow is a band of like what if they make a new framework that is better than both app kit and ui kit and is able to write applications for both platforms not that you write one application and run in both places but the framework spans everything it can do menu bars it can do toolbars it can do all the stuff on ios it can do touch it can do mouse pointer it can do stylus it can do everything
John:
And you use that one new framework that is better than the thinking in UIKit, better than the thinking in AppKit, has all new ideas and whatever.
John:
It's Swift native from top to bottom, whatever you want to do.
John:
They didn't do that.
John:
They're instead saying, we're going to go with UIKit and we're going to make UIKit better and bring it to the Mac and extend it to the Mac functionality.
John:
I do wonder, tech nerd-wise, whether... It's always nice to... It's kind of like I did with the language that would replace Objective-C.
John:
Let's imagine the most magical, wonderful language there ever could be, unconstrained by practical concerns that's just merely better than everything that came before it, and it turns out that's really hard to do.
John:
So you take what you can get.
John:
So again, Apple probably made the right decision here.
John:
But I'm not either optimistic or pessimistic about it, but I am... I have sort of...
John:
accepted or come to terms with the idea that this, that things, you know, that things don't look good for AppKit.
John:
And I don't think that's necessarily a bad thing or a good thing, but I think it's going to be a big change on the Mac and,
John:
Hopefully a positive one just because for all of the great AppKit apps that start to get left behind, presumably they'll be replaced by even more great applications written by formerly iOS developers.
John:
I'm willing to... I don't know if we have time to get to this in this episode, but I'm willing to...
John:
I have to have been willing to accept the idea that what makes a Mac application a Mac application changes over time because it has.
John:
Believe me, what makes a Mac application in 1984 is not the same thing as it makes now, and there's been a million iterations of it.
John:
Becky Hansenmeier asked on Twitter, you know, like, has anyone written a rundown of the unique characteristics of a native Mac app?
John:
Like, what is it that makes a Mac app an app?
John:
I don't want to dive into that today because I think it's too big a topic, but...
John:
I am 100% willing for what makes a Mac app to change.
John:
And UI kit coming to the Mac necessarily will change that, hopefully for the better.
John:
It's changed so many times before, and mostly it has been for the better.
John:
So I'm not pessimistic about that.
John:
But...
John:
I am, as with the Mac OS 10 transition, as with many transitions before, and as Casey pointed out, there is great potential for things to go terribly wrong, and you're not going to get every decision right, file name extensions.
John:
So we have to be on the lookout for things that get screwed up along the way.
John:
But I think I'm like...
John:
both terrified and cautiously optimistic?
John:
Is there some combination emoji for that, Casey?
John:
Maybe you can look that up for me.
Casey:
I'll work on it.
Marco:
I also would not rule out the possibility.
Marco:
John, you mentioned earlier we talked a little while back about a new cross-platform framework, possibly.
Marco:
That seems to be what Mark Gurman was talking about at some point, or what John Gruber was talking about at some point, and what Mark Gurman named.
Marco:
I don't think that what we've seen so far from this UIKit on the Mac effort,
Marco:
rules that out.
Marco:
Basically, because when you're talking about running UIKit on the Mac, you're talking about a number of different things.
Marco:
One of them, which they talked about, was reunifying all the underlying frameworks.
Marco:
The networking frameworks, the graphics frameworks, all that stuff that has diverged from between iOS and Mac over time.
Marco:
Reunifying that.
Marco:
That's not a small job.
Marco:
That's probably actually more work than the interface side.
Marco:
The other part of it that they're doing is making UIKit work on the Mac.
Marco:
Well, UIKit has been running in the simulator for a decade.
Marco:
So the actual part of making it operate in some functional form on Intel Macs
Marco:
They did that already.
Marco:
Now it's just down to the details of giving it a window, giving it a menu bar.
Marco:
Again, that's not a small amount of work either, but I think all the underlying system stuff is probably more work than that.
Marco:
They're selling this right now as, look, here's a way to take this handful of random, fairly low effort Apple apps and basically bring their iPad versions to the Mac.
Marco:
But what if that's just like the demo?
Marco:
What if that's just what we get this year?
Marco:
And what if one of the reasons why we can't write these yet is that they would rather us use the new thing that's coming out in the future?
John:
I don't think the new thing can be a separate thing, though.
Marco:
Well, it can be a separate UI framework.
Marco:
They do have this significant problem of they have multiple different platforms that all use different UI frameworks for the most part.
Marco:
They have AppKit, they have UIKit on the Mac, or they have UIKit on iOS, even though UIKit on the iPad is...
Marco:
kind of weird in certain ways and kind of need some things from app kit.
Marco:
Uh, it's as they, as, as they push more into like iPad pro areas and multiple windows, multiple apps running, things like that.
Marco:
Uh, it kind of needs to borrow some of that stuff.
Marco:
Um, the TV OS and the watch OS stuff are totally different.
Marco:
Each totally different from each other and from everything else.
Marco:
Um,
Marco:
uh tv os kind of runs ui kit but only parts of it and it has all of its own stuff it has to add on top of that watch os has watch kit which is nothing like ui kit has no support for ui kit and uh and it's this whole different thing not to mention you have swift
Marco:
Like, that's a huge thing.
Marco:
And you have changing paradigms in what is considered, you know, a good way to write UIs from the old, like, you know, manual state based way to the more modern, like, you know, reactive slash declarative ways that Casey knows about.
Marco:
Like, this is a pretty good time to take this opportunity to launch a new UI framework.
Marco:
if they want to do that.
Marco:
And I don't think anything we've seen precludes that.
Marco:
I think these are not mutually exclusive things.
Marco:
They could run UIKit on the Mac and also support a new framework for apps to use.
John:
Well, there are always lots of projects in flight at Apple, so I totally believe that something like this
John:
could have happened and like it is important to remember that apple hasn't committed to anything yet because like the commitment event is essentially the publishing of a public api for third-party developers and they're pointedly not doing that this year like there's no there's no api for you to use like yeah apple's doing it but that's not for you it's just like ux get apple did it with ui the difference is this time like they're they're hinting at the idea that next year this will be a thing that you can do right but they have an entire year to decide
John:
Is this what we're doing?
John:
Are we going to let people use our Mac version of UI kit with a bunch of extra classes for menus and toolbars?
John:
Or, to your point, Marco, what about that other project that we had stewing for... And I don't want to call it a cross-platform framework.
John:
I want to call it like a platform-spanning framework, which I feel like is different.
John:
Cross-platform is like, all right, one set of code, and when it runs here, it does this, and when it runs here, it does that.
John:
A platform-spanning set of code is basically if you took...
John:
app kit plus ui kit and union them and say here's an api that can do everything you can't call the menu bar ones on ios and you can't call the touch ones on the mac for now um but it's just a framework that spans everything yeah they could have a new framework like that um and then the more but the more tame version assuming they stick to their current plans is oh now you can have an application that forget about the i forget what it's called like ios system server or something like the the the basically the the ios simulator that's not an ios simulator um
John:
that lets your iOS applications have little windows and do all that crap that runs all your stuff, which is why you can't link against AppKit.
John:
Like, it will forcibly not let you link against AppKit if you're running inside that thing.
John:
Instead of that, just have your Mac application link against UIKit for the Mac, link against AppKit, and then mix and match them the same way you can mix and match carbon and cocoa or whatever.
John:
I think...
John:
I think the fact that they went public with this means some kind of decision has been made that if there was a, like, here's a new way to... Here's a platform-spanning API that we can eventually extend to everything.
John:
If that project existed, it lost to this project.
John:
And this definitely feels like a...
John:
you know swift aside it feels like a more apple way to do things in that they've kind of picked a winner like they picked a winner with coco and the winner is ui kit and they realize the new api will be ui kit on the mac extended with ever more classes that are mac specific they did like the minimum possible classes that you needed to get anything running in a reasonable way for for you know the the mojave thing
John:
But they could double the size of UIKit on the Mac, just trying to keep pace with all the stuff that AppKit could do.
John:
And that would be the new API, because it would be a bunch of new classes that never existed before that are basically UIKit-ified ways to do things that AppKit can do, plus the continued evolution of UIKit.
John:
And the unified substrate, I remember seeing that slide and being super excited about it, but it's hard for me to gauge exactly how far they've drifted, like...
John:
Because the core has been the same forever.
John:
Obviously, they had to hack it to hell to get it to work on the original iPhone.
John:
And there's tech debt and there's drift and so on and so forth.
John:
But I hope they haven't drifted so much that that actually is the bigger job.
John:
It could be.
John:
It could be the bigger job.
John:
I don't know how badly they've spread from each other.
John:
I don't know how much tech debt has accumulated there.
John:
But at this point, the iOS devices are just as powerful as most of the Macs.
John:
There's no real reason for that drift.
John:
I'm glad to see them unifying and I'm hoping it's not a big job.
John:
I think the job of, hey, make UIKit-ish versions of all that stuff that AppKit does is a huge job just because of the psychic weight of knowing that this API that you come up with, you're going to be stuck with for a long time.
John:
Same thing with UIKit.
John:
making a public API, Apple making a public API is one of the most dangerous and scary things that Apple can do because of Apple's policy of trying to support it.
John:
You can't just make an API and say, oh, we made a terrible stake, never mind.
John:
People build apps on it and you have to support them.
John:
Like that's why they're taking so long with the ABI compatibility and Swift.
John:
It's like, you get one chance to get this right.
John:
You can't really say, Oh yeah, we tried last year, but we changed our mind.
John:
All your applications are going to break.
John:
Um, so yeah, this is regardless of the way this goes, this is like, what is the, you know, may you live in interesting times, the curse, whatever.
John:
Uh, it's an exciting, it's an exciting slash terrifying time for the Mac.
John:
Uh, these next few years are going to be as many people have pointed out, uh,
John:
The biggest change in the Mac's history since the classic to Mac OS 10 transition, maybe not potentially not as big, but also potentially bigger.
John:
Like it's not with the OS transition.
John:
It was so clear.
John:
It's like old OS gone, new OS here, like very little share between except for Carbon and this.
John:
It could be a gradual evolution or that invasive species could rush through our ecosystem and just change it overnight over the course of like a year or two.
John:
But anyway, we've been talking about the Mac.
John:
Some people would say it's stagnating or not evolving as much as it was before.
John:
And regardless of how this goes, I don't think our complaint over the next five years will be
John:
a lack of change or or uh excitement or terror on the mac i think that we'll be getting all that in spades
Marco:
Betterment is the largest independent online financial advisor.
Marco:
At Betterment, hidden costs are nowhere to be found.
Marco:
They believe in low fees.
Marco:
No matter who you are or how much money you invest, you get everything for one low transparent management fee.
Marco:
And Betterment's advice is in your best interest because as a fiduciary, they make recommendations that they're not incentivized by certain funds to recommend to you, and they don't have their own investment products to sell.
Marco:
And they offer personalized advice and a suite of tools to help you know whether you're on track to hit your goals or to get the retirement you want.
Marco:
And when you need it, their tools and guidance can help you get back on track.
Marco:
Betterment gives you all this for only a 0.25% annual fee with unlimited messaging access to their team of licensed financial experts.
Marco:
These are very low transparent fees compared to traditional services.
Marco:
For more complex situations, if you want, Betterment Premium gives you unlimited phone call access to their team of certified financial planners for only 0.4% annually.
Marco:
And everything they do is designed to lower your taxes and increase returns.
Marco:
So they also have something called the tax-coordinated portfolio.
Marco:
On average, Betterment's tax-coordinated portfolio can increase your value by an estimated 15% over 30 years.
Marco:
Thank you so much for Betterment for sponsoring our show.
Casey:
All right, let's do some Ask ATP.
Casey:
Let's start with an interesting kind of simulation or scenario is a better word for it from the comedian James Veach, who wrote, I'm placing all three of you in charge of security at Apple, putting to one side the leaky supply chain.
Casey:
How are you going to work out how Gurman and other people like him are getting his information and
Casey:
and how are you going to put an end to it once and for all tim cook is relying on you guys casey you have a desk desk job again marco you have a job and john very little has changed for you you have an unlimited budget be reasonable with this john things to consider how is german getting his stories is it just friends in high places or does he have other more nefarious means remember those health app mock-ups why did german get those so wrong and case manufacturers got it really wrong with the iphone nano and the teardrop iphone
Casey:
James writes, I've often wondered whether schematics for one or both of these products were disseminated in an attempt to root out the leakers.
Casey:
And I find this fascinating.
Casey:
So what would you do?
Casey:
I think that last thing is the thing that I find most interesting and most exciting is deliberately telling people the wrong data just to see where it ends up.
Casey:
Another thing I would do is just figure out, like, what did the CIA and like FBI do in these sorts of scenarios?
Casey:
Like, presumably, there have been people in intelligence operations, presumably, that have tried to figure this out before.
Casey:
You know, what do they do?
Casey:
How do they, you know, sniff out when there's a leak?
Casey:
And how do they how do they figure that out?
Casey:
Additionally, I mean, I've heard – well, we have heard as a community and I've heard from friends that work at Apple that disclosure is a big thing.
Casey:
Like my understanding is there is actually an app or it's part of an app that Apple has where you can look up, okay, Marco and I both work at Apple.
Casey:
I want to talk to Marco about Project Titan.
Casey:
Let me go look real quick and see if Marco is disclosed on Project Titan.
Casey:
Oh, no, he's not.
Casey:
Okay, well, Marco, let me just tell you what I'm working on these days.
Casey:
Something interesting.
Casey:
And that's all I can tell you.
Casey:
So compartmentalizing even more, that's a roundabout way of saying compartmentalizing even more is probably a good way to prevent the problem.
Casey:
But in terms of sniffing it out, that's a tough question.
Casey:
And other than planting bogus data, I'm not sure what to say.
Casey:
Marco, how would you handle it?
Marco:
I mean, there are certain things you can do to actually, like, you know, track down and catch individual leakers.
Marco:
You know, I'm sure Apple's – I mean, we don't – the fact is none of the three of us have ever worked in this kind of field before of, like, you know, secrecy and security and stuff as far as I know.
Marco:
So I don't – Sort of.
Marco:
Well, but, like, were you in charge of enforcing it and, like, tracking people down?
Marco:
If we were, we couldn't say.
Marco:
Yeah.
Marco:
but yeah so like you know these suggestions might be ridiculous you know compared to people who actually know what they're talking about in this area but with that disclaimer you know obviously one angle is to catch the people who are existing leakers and you do that it
Marco:
Who knows?
Marco:
One idea is what you mentioned, kind of like fake leaks, just to kind of find out where things are leaking from.
Marco:
One little idea I thought of, which I'm sure they've thought of and might even do, is there's been a lot of leaking of memos recently.
Marco:
What if every copy of an email memo that went out to everybody had software that slightly varied some of the wording?
Marco:
Because you can do things like try to embed invisible Unicode space characters and stuff like that.
Marco:
But that's easy to filter out.
Marco:
But changes to the wording are not easy to detect if you're wanting to report on or quote a memo unless you have more than one copy.
Marco:
Then you can diff it and stuff like that.
Marco:
But if you only got one copy...
Marco:
then you could basically make enough minor wording variations in it that you can kind of binary search it down to whoever is doing the leaking.
Marco:
So that's part of it too.
Marco:
But ultimately, I think most of it's probably less on the technical side and more just on the human side.
Marco:
There have been, over time, a lot of crazy Apple leaks.
Marco:
Most of the recent ones, honestly, have boiled down to Apple slipping up and accidentally publicizing HomePod software or things like that.
Marco:
That's been a lot of them recently.
Marco:
Otherwise, there are human factors involved.
Marco:
What makes someone leak?
Marco:
What motivates people to do that?
Marco:
Oftentimes those are issues that you can't really do anything about.
Marco:
Oftentimes it's people who are mad that they maybe lost an argument internally or that the product they're working on was gutted or they have some other axe to grind with the company.
Marco:
And so they leak stuff that will basically argue in their favor or that will kind of, you know, make the company look bad in a way that gives them some kind of vindication.
Marco:
And those people like you're kind of always going to have that risk.
Marco:
And I'm not sure there's that much you can do about that, except what Apple is doing about that, which is basically like scaring people and saying, look, if you do this, we're probably going to catch you and you might go to jail like that.
Marco:
That's a pretty effective thing, actually.
Marco:
It seems like from their language around this recently, it seems like they have tried to lean heavily on the appeal to emotion.
Marco:
You're letting the team down if you leak.
Marco:
Stuff like that.
Marco:
Honestly, that probably isn't very effective.
Marco:
I can't see that being a major thing.
Marco:
But ultimately, you're always going to have some amount of leaks.
Yeah.
Marco:
And I'm not sure they're necessarily that bad.
Marco:
I mean, sure, you want the official company line to be, leaking is bad, you're letting the team down, you shouldn't do this, you'll get in trouble.
Marco:
But these leaks are also really good PR, usually.
Marco:
And they cultivate this...
Marco:
this like community around apple and this hype around apple that we're all just so excited about what they might do in the future that there's this huge demand for leaks and rumors about things they might be working on and that that all plays into the reputation the brand the hype the pr cycle i think i think most of the time these rumors actually help apple
John:
so leaks are helpful marco you're fired from your security job there's the wrong attitude for your position uh unfortunately james so victim to one of the classic blunders uh the most famous as you know casey is what i have no idea never get involved in a land war in asia oh of course only slightly less well known as this no i'm not gonna do that is that princess bride is that right yes the the classic blender that he fell victim he knows he fell victim he says it right here in the question
John:
Here is the problem with your question, James.
John:
You have an unlimited budget.
John:
Be reasonable with this, John.
John:
I love that he knew that Keisha and I wouldn't give too crap about that line, and he knew you would focus in on that.
John:
That is the crux of the entire question.
John:
The easy solution to this question is, how do you stop Mark Gurman from leaking?
John:
You have an unlimited budget, I would pay Mark Gurman whatever he wanted to pay.
John:
Everyone has a number for the rest of his life, and boom, problem solved.
John:
I get promoted.
Okay.
Casey:
You know, it's funny you say that.
Casey:
As Marco was talking.
John:
$100 million a year.
John:
Gurman is done.
Casey:
As Marco was talking, I was thinking to myself, you know, if I really want to just think outside the box, what if I just said, and I was taking a more negative approach, you know, what if you said, if you can get us, if you can lead us to a leaker, your bounty is a billion dollars, like literally a billion dollars, because money, no object, why not?
John:
You don't have to lead to a leaker.
John:
You know it's Gurman.
John:
Just get him off the board.
John:
Pay him $100 million a year.
John:
Your Gurman problem goes away.
John:
100% guaranteed.
Marco:
Yeah, but there's always going to be more Gurmans.
Marco:
Gurmans wasn't... Gurmans is not the only person.
John:
Well, I mean, before there was Gurmans, how many Gurmans were there?
John:
Gurmans is like, you know, to deal with the Gurmans issue, buy Bloomberg.
John:
Buy the whole company that they work for.
John:
You have an unlimited budget, the question says.
John:
So this is a very bad question, James.
John:
You told me to be reasonable, but it's not possible.
John:
The terms of your question is you have an unlimited budget...
John:
And, you know, that just destroys it.
John:
So try to be more precise next time.
Casey:
OK, well, how about this?
Casey:
You have a budget of whatever Apple has in the bank right now.
John:
Now, that's not the question.
John:
That's basically an unlimited budget.
John:
And that's also pretty much an unlimited budget.
Casey:
We can move on.
Casey:
But but, James, if if you would like to reward your question, perhaps we'll approach it another time.
John:
That's it.
John:
This is your one and only chance to ever get an ask ATP question, given the the huge volume of questions we get.
Casey:
Robert Barrett would like to know, on a recent show, Marco advised that when getting a 4K monitor, you shouldn't get anything bigger than a 24-incher.
Casey:
Can you elaborate on why this is, please?
Casey:
And actually, I can field some of that.
Casey:
When I was exploring a 4K monitor, really what I wanted was an external retina monitor at work.
Casey:
This was like a year ago.
Casey:
And we had gotten in a 27-inch 4K monitor.
Casey:
And when I sat down at it, it was clear to me that I could actually see pixels.
Casey:
And if you remember way back when, to the original Retina Screen announcement, was that iPhone 4?
Casey:
Is that right?
Casey:
Yep.
Casey:
uh the the the def the colloquial definition if you will was that you wouldn't be able to see the pixels at the distance at which you would generally hold the device they also gave like a a dpi number whatever the hell it was but they but they basically said thank you but they basically said hey listen you can't see the pixels and that's the whole point and on a 27 inch 4k monitor
Casey:
Even with my crummy eyes, I could see the pixels or maybe I felt like I could.
Casey:
But with about a 22 to 24 inch 4K monitor, I could no longer see those pixels.
Casey:
And to my eyes, that was the sweet spot.
Casey:
So if you're going 24 below, 4K is fine.
Casey:
If you're going above 24, you need 5K.
Casey:
Otherwise, you're not really living the retina dream after all.
Casey:
You're just living a very, very large amount of real estate dream, if that makes any sense.
Casey:
But Marco, anything you would like to clarify or add on that point?
Marco:
you know as computer monitor technology has advanced we've we've kind of had like standard size monitors for most of you know personal computing history they're kind of evolved like the standard density range of like this is roughly the dpi range that monitors were and so like for lcds you had like you know the 15 inch monitors i think those are usually like
Marco:
1024 by 768.
Marco:
The 17-inch was 1280 by 1024.
Marco:
The 19-inch was 1600 by 1200.
Marco:
And then the 24-inch class monitor was 1920.
Marco:
And then the 30-inch class monitor was 2560 across.
Marco:
And then in the retina era...
Marco:
The way that most monitors have gone retina is by just doubling the pixels in each dimension.
Marco:
So that way the OS can render everything at a perfect 2x.
Marco:
It makes a lot of things simpler.
Marco:
It makes a lot of things look nicer.
Marco:
And it's just generally a good way to go high DPI is just double everything.
Marco:
So the problem is 4K is double the 1920 wide resolution that was the common resolution on 24-inch monitors.
Marco:
Actually, then, what happened a little bit later is things got slightly smaller.
Marco:
24-inch monitor resolution of 1920 across, or just 1080p.
Marco:
Well, that was the shorter version, but anyway.
Marco:
We'll ignore that difference for the 16x9 versus 16x10 difference.
Marco:
We'll ignore that for now.
Marco:
Sorry, 16x10 fans.
Marco:
We lost.
Marco:
I was one of you, but we lost.
Marco:
Anyway, at some point, maybe 10 years ago, they started making...
Marco:
21 inch monitors that actually had the resolution of 24s and 27 inch monitors starting with 27 inch iMac that had the resolution of previous 30 inch monitors so there is a slight correction downward where you had the same number of pixels just in a slightly smaller monitor
Marco:
so other than that correction things have stayed pretty much the same now that correction makes for 4k being the ideal size at either the old pre-correction size of 24 inches or the new post correction size of 21.5 inches which is why the 4k imac is 21.5 inches
Marco:
The correct, quote, correct version of 5K is, as Casey said, 27 inches or 30 inches, depending on what you can find.
Marco:
I don't even know if anybody makes a 30-inch 5K, but this is like the standard sizes.
Marco:
So the problem is if you get something that falls between them, so for example, 4K at 27 inches, which is what the question is about,
Marco:
You have to either run the monitor at 2x, which I would want to run a 4K monitor at 2x unless it's like 40 inches wide.
Marco:
So run it at 2x, which means at that size, everything will be like, quote, too big compared to most other computer monitors you've seen.
Marco:
or run it at 1x, which means you're going to have things be really tiny.
Marco:
You will have a lot of real estate, but it will be really tiny.
Marco:
And if your eyes are good enough for that, more power to you.
Marco:
But I think most people would not probably want to run that at 1x.
Marco:
So that is why.
Marco:
And there's lots of other screen sizes out now.
Marco:
We're kind of in a glorious heyday of...
Marco:
but really good monitors out there like you can get like there's not those that whole class of ultra wide ones have you seen those that are like they're like 34 inches wide but kind of short so it's almost like having like two 20 inch monitors next to each other kind of like that yep but like in one big screen
Marco:
Those are not yet available in anything I would call a high DPI resolution at that size.
Marco:
I think you pretty much have to run those at 1x, and so you're getting real estate but not really getting retina quality.
Marco:
But a lot of people love those things, and they're not that expensive.
Marco:
So anyway, you have a lot of choices these days, but...
Marco:
Yeah.
Marco:
unless you're in the certain size ranges.
Marco:
And then finally, there's a great blog post by our friends at Bajango, who make iStat menus for the Mac.
Marco:
They have a great blog post that I think we linked to last time we talked about this, but I linked to it again, that basically shows you the two good ranges, the good range of 1x and the good range of 2x, and what size and resolution monitors fall on which part of that spectrum.
Casey:
Will Law writes in to say, what kind of sick, sad world do we live in where WWDC comes and goes and there is no discussion of box lunches or cuisine?
Casey:
I expected more of you all.
Casey:
I am deeply disappointed in myself that we did not talk about this in any way, shape or form.
Casey:
I only ate like one or two WWDC lunches this year because I was running around like a crazy person.
Casey:
The keynote day, by the time I made it to the lunch area, the particular lunch I wanted was long since sold out, if you will.
Casey:
It's not actually for sale, but all of them had been cleaned up and people had claimed them.
Casey:
Also, I would like to file a formal complaint that I only had one bottle of Mango Tango Adwalla.
Casey:
This is unacceptable.
Casey:
I only saw it once very briefly, and it was actually a friend of mine that grabbed it for me.
Casey:
But I am upset.
Casey:
This is not the way the Odwalla containers or the Odwalla selection should be.
Casey:
And I am disappointed, Tim, and I'm holding you personally responsible.
Casey:
John, as the only other person who was in the conference, anything you would like to add about the cuisine this year?
Casey:
It seemed to be basically the same as last year, as far as I could tell.
John:
So I think I had a box lunch every day.
John:
I think I even had breakfast every day.
John:
So I'm on my normal, like, WWDC meal plan.
John:
Before we get to box lunches, I just want to make a brief comment on the breakfast.
John:
It's the second year at San Jose, and the second year they've done a thing that I don't like for the breakfast, which is to try to add variety.
John:
by having different things at breakfast each day the problem oh yeah no good no good their variety consists of taking what used to be at breakfast at wwdc and taking one third of it on this day and then one third on this day then one third on this day so some days just have donuts some days just have bagels some days just have little pastries like you got to have donuts bagels pastries cream trees all of it every day why because that is the style to which we have become accustomed
John:
Like, Moscone, you know, it was so much better for food service in terms of traffic flow and everything, but they had all that stuff every single breakfast, right?
John:
I don't like coming on a day where there's just donuts.
John:
I don't want to have a donut for breakfast.
John:
I want to, you know, like, you got to have everything every day.
John:
I have to decide, you know what, today is the day I'm going to have a donut and make it my call, not like, oh, guess what, you have donuts today because that's the only thing.
John:
So...
John:
Setting that aside, oh, and on the Odwala front, I never even saw a container of Odwala.
John:
I didn't even physically see one in someone else's hand.
John:
I have no idea where they were.
John:
I don't know how you managed to get one.
John:
I'm not as obsessed with them as you are, but I feel like the Odwala supply has dwindled to startlingly low levels.
Casey:
I mean, it was still there, which is better than a couple of years, but I only saw it a couple of times.
Casey:
And like I said, it was a friend of mine that actually saw the mango tango and grabbed it and tweeted at me to say, hey, I've got a mango tango if you want it.
Casey:
So if it wasn't for him, I would not have had one at all.
Casey:
But but yeah, I could not agree with you more about breakfast.
Casey:
I didn't even think about the breakfast scenario, which was awful because as much as the West Coast does not understand what a bagel is like, they truly and utterly do not grasp what a bagel is much in the same way Montreal doesn't.
Casey:
But but with that said, at least give me your crappy bagel esque bagel.
Casey:
baked good so i can slather some cream cheese on it assuming i can open the container i can slather some cream cheese on it and and use that for my breakfast every day but yeah one of the one of the days i went in for breakfast i really really wanted this bagel like contraption and it turned out they only had like really crappy baked like pastries which i had zero interest in i want to make that choice i'm a grown man let me choose please hey
John:
Gotta have all the breakfast options every day.
John:
Also, the butter balls, meaning they have like little tiny grape-sized balls of butter.
John:
Wait, just like loose?
John:
Yeah, like in a bowl.
John:
A bunch of butter balls in a bowl with a knife.
John:
And you just go like grab one?
John:
Yeah, those individually foil-wrapped pats of butter are way better choice when you're trying to serve a lot of people.
John:
Otherwise, people are trying to dig out these butter balls with the butter knife and just like put the ball on their plate and then hope that when they get back to their seat, it's soft enough so they don't break their plastic knife trying to spread it, right?
John:
Anyway, breakfast had problems.
John:
But to get to the box lunches, it was an interesting turn of events this year on the box lunches.
John:
I've complained a lot about them in the past.
John:
Externally, they looked about the same.
John:
You're like, it wasn't the same as every year, but there was a difference.
John:
They leaned much more heavily on salads this year than usual.
John:
It used to be that they would lean a lot on...
John:
sandwich things and things that look kind of like dinner meal and then there'd be like one salad i saw a lot of salads and this protected them from one of their biggest problems which was historically anything they try to make a sandwich
John:
has either terrible bread or bread that might have been good except it ended up sitting in some liquid so it got soggy and a sandwich with soggy bread is no good right so they did a lot of salads and salads are good because if they're not out in the sun and you know the pro tip i learned from last year take get your lunch indoors not outdoors because the outdoor ones may have been baking in the sun
John:
they're they hold up better like it's like greens and fruit and some dried thing like there's nothing really to get soggy like the the the salad dressing is usually on the side in a little container and if a little bit spills out it's not a big deal
John:
uh and it avoids them having to find some way to get decent bread or decent filling for their sandwiches um so i i mostly give a thumbs up to that because i feel like the average quality of the lunch i had was higher than in years past that said i like a good sandwich and i miss the sandwiches so i'm not sure i'm not sure what they need to do like they haven't cracked the sandwich codes now they're just avoiding it by avoiding their weakness and just not making many sandwiches which improve the average quality but you know you get tired of salad after a while
Casey:
Now, I was going to just move on from this topic, but it occurred to me, Marco also had conference issues at your conference, from what I've understood, because my understanding is social policy did not have a good system set up for them either.
Casey:
Yeah.
John:
He ordered lunch and social policy every day, but only received one.
John:
And presumably his other six lunches are arriving now to whoever is sitting at his table.
Casey:
It's probably accurate.
Marco:
Yeah.
Marco:
Social policy, as much as I love it as a hangout spot, the food service part of it seemed to only get worse this year, not better.
Marco:
so uh i i've started to i started in the uh later half of the week to just start exploring other options like beer and sausage place yeah the beer and sausage place is great if what you want is beer and sausage that is amazing i i wish i had discovered it last year amazing they give you your food in a timely manner it's cheap and it's good it's like oh thank god where was this place yeah like the only downside is their menu is fairly small yeah no it's fine if i find one thing i like i'm fine
Marco:
yeah like and it's not small in total it's small it's small in diversity like if you want beer they have like 60 beers if you want sausage they have like 60 sausages but then they also have they have like um what's that weird montreal fries and duck fat and curds that's it yeah poutine yeah they have regular fries too they have a bunch of different kinds of sausages and french fries that's all you need yeah and poutine and grilled cheese that's that's their entire food yeah no i think i had a grilled cheese there too it's good it's good i know
Marco:
and it's like it's not cheap cheap but like for 10 or 11 you get a very filling meal yeah and and it's called something public house for anybody looking at san jose it's like i thought it was called it's not called original gravity that's it original gravity public house that's it all right all right teamwork good all right yeah that place also i went across the street from social policy across that little plaza to taco mania one time
Marco:
And that was surprisingly good.
Marco:
It looks like some kind of weird cheesy chain thing, but you go in and it's surprisingly good.
Marco:
And I would say it still has some of San Jose-ness to it, but it's almost normal.
Marco:
The beer and sausage place, I would say, is normal.
Marco:
100% normal.
John:
They hustle.
John:
They get you your food.
John:
They find where you are.
John:
They bring it to you.
John:
You don't have to wait long.
John:
I was very impressed.
Marco:
Yeah, the beer and sausage place is by far the most up-to-speed, consistent eatery I've found there.
Marco:
Also, a good word to – is it called Good Karma, the vegan place across the street from that?
Casey:
Yes.
Marco:
I finally got to eat there.
Marco:
Last year, I couldn't because there was always a big line.
Marco:
This year, I finally got to eat there a couple times, and it's really good.
Marco:
Again, somewhat limited menu, but if what you want is on their menu, it's good, and the service is pretty good too.
Marco:
So I think what I've what I've found is I've explored San Jose one more year is in a one block radius of the hotel.
Marco:
Yes.
Marco:
Yes, exactly.
Marco:
Is that, yeah, social policy.
Marco:
I ate very few like lunches there because I was just finding better places for lunch.
Marco:
Anyway, thanks to our sponsors this week, Betterment, Away and Linode.
Marco:
And we will talk to you next week.
Marco:
Now the show is over.
Marco:
They didn't even mean to begin.
Marco:
Cause it was accidental.
Marco:
Oh, it was accidental.
Marco:
John didn't do any research.
Marco:
Marco and Casey wouldn't let him.
Marco:
Cause it was accidental.
Marco:
Oh, it was accidental.
John:
And you can find the show notes at atp.fm
Marco:
And if you're into Twitter, you can follow them at C-A-S-E-Y-L-I-S-S.
Marco:
So that's Casey Liss, M-A-R-C-O-A-R-M-N-T-M-A-R-C-O-R-M-N-T-M-A-R-C-O-R-M-N-S-I-R-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S-A-C-U-S
Casey:
So long.
Marco:
So, Casey, how is Not Your Jeep going?
Casey:
We've had a bit of a falling out.
Marco:
Already?
Marco:
It's been, what, like a week and a half or something?
Casey:
Yeah, something like that.
Casey:
It was Father's Day that I got it.
Casey:
And I think what I've realized is I want to own a Jeep as like a second car, which is not really in the cards for me.
Casey:
I think some of this would get better with a more modern Jeep and or if I treated the Jeep more like a traditional car and less like an erector set.
Casey:
But because it's rare that I have a car that's a convertible and even more rare that I have a car that the doors can come off, and because it's summertime, naturally I've been trying to roll with the doors off and the top down as much as possible.
Casey:
However, what I forgot about is that in Virginia, it's like a light version of Florida when it comes to weather, summer weather, in the sense that, well, both in temperature, but more in the terms of precipitation.
Casey:
Because my experience of Florida is that every friggin' day, it is unbearably humid, then it torrentially rains for about four and a half minutes, and then it's beautiful.
Casey:
Still fairly humid, but otherwise beautiful.
Casey:
Well, Virginia is kind of like that, but way less extreme in every measurable way.
Casey:
Not as humid.
Casey:
Humid, but not as humid.
Casey:
The rain is not a thunderstorm often, and sometimes it doesn't even rain every day.
Casey:
The problem, though, is if you're going to go and park a vehicle with no top and no doors outdoors for eight hours, say if you're, I don't know, at work.
Casey:
All you end up doing is looking out the window to see, oh, it's getting a little dark.
Casey:
Oh, it's getting a little dark.
Casey:
Oh, dark sky says no, but the windows say maybe.
Casey:
So I've been every day running out in panic because I've decided to at least put the top up.
Casey:
So there'll still be rain coming in from every measurable part of the car except the roof.
Casey:
And putting the top up is doable as one person, but it's not easy.
Casey:
Putting the top down as a single person is pretty easy, but putting back up is a little bit of a pain.
Casey:
And doing the doors, absolutely a one-person job, but I don't bring the doors with me.
Casey:
I mean, it's a two-door Wrangler, so it's not like I have a place to store the doors.
Casey:
I don't have any really reliable place to put the windows, the rear and side windows.
Casey:
So...
Casey:
What ends up happening is I just stress out all day about whether or not my dad's car is going to get rained on.
Casey:
So I could, of course, I could absolutely just leave everything put together and just treat it as like a regular SUV.
John:
Just treat it like a really bad, uncomfortable car.
Casey:
Right, exactly.
Casey:
Exactly right.
Casey:
But where's the fun in that?
Casey:
It's a Wrangler.
Casey:
It's a Wrangler for a reason.
Casey:
It should be fun.
Casey:
So what I'm realizing is it's probably...
Casey:
It's one of those things that I think we've talked about many times, although I can't think of a specific example, where it's fun in your head, but in reality, it's a lot less fun than you thought.
Casey:
Actually, a great example is, Marco, when you had two cars.
Casey:
You've said many times that it was fun in principle, but the reality of it was that it was just kind of a pain in the butt.
Casey:
Yeah.
Casey:
And I think that's kind of where I'm getting with the Wrangler.
Casey:
And then this was the deal.
Casey:
I mean, it's still a possibility, officially speaking, but the deal was really sealed when we had all four of us in the car, top down, and two things happened.
Casey:
Number one, anytime we stopped moving, the poor kids in the back roasted because there's no top blocking the Virginia sun and there's no airflow.
Casey:
Because even though I cranked the AC and pointed it directly at them and not at me at all, it
Casey:
It's a wide open car.
Casey:
Of course, it's just going to flutter out into the surrounding area.
Casey:
So I was trying to air condition all of Richmond in order to lightly cool my children.
Casey:
And and so, you know, there they are baking.
Casey:
And if every time we hit a red light and then as we're driving somewhere and this was all, you know, surface streets, Aaron and I got to talking about what it would be like if we got in an accident with no doors on the car.
John:
m which is something that the three of us discussed again this is just a curse to you now we've been yelling at you about this for months well when it comes from your wife you pay closer attention and so pay attention to me casey you made you made a vow to me when you started we left obey in that's right oh man
Casey:
So anyway, so she did not say that this is not an option, but I'm starting to feel like maybe I should explore other alternatives.
Casey:
And so I don't really have a good answer for what the other alternative is.
Casey:
I keep coming back to I feel like my only choices that I'm interested in are GTI or Golf R.
Casey:
Aren't those basically the same car?
Casey:
Basically, except the GTI has a sunroof and the Golf has four-wheel drive.
John:
Oh, the sunroof.
John:
I always forget what a big factor that is.
John:
I like my sunroofs.
John:
I love how hard you're trying to say Golf.
Casey:
I know.
Casey:
Well, I can't.
Casey:
I keep wanting to say Golf.
John:
I know.
John:
He's working on it.
John:
He's doing a good job.
John:
Encourage him.
Casey:
I'm trying very hard, you guys.
Casey:
I expect to see this on my performance review next quarter.
Casey:
Anyway, so I like both of those cars in principle, having driven neither of them.
Casey:
And everyone I know, and I think I've made this speech many times, everyone I know has ever driven a GTI says it is the far and away best all-arounder that you can buy today.
Casey:
That if you wanted to have a car, if you want to be a one car person, but that one car can do anything within reason, of course, get a GTI.
Casey:
But I kind of like the idea of the Golf R. And if I got a GTI, I think I would always say, well, why didn't you get the R?
Casey:
Conversely, if I got the R, I would always say, man, I really wish I had a frigging sunroof.
Casey:
Also, the Golf R's wheels are not good in the 2018 models.
Casey:
The 2017 models were great.
Casey:
The 18s are no good.
Casey:
So I don't know what I'm going to do.
Marco:
You just happen to find a white 2017 model.
Casey:
Well, I could get a 2017.
Casey:
Actually, that is the same generation.
Casey:
Maybe I should just get a 2017 and see if I can find one.
Casey:
The other thing I looked at was you can get OEM 2017 wheels for like $1,500 or something like that.
Casey:
And you can actually get, apparently my friend recommended a company out of Canada called Replica.
Casey:
I think I saved a link somewhere.
Casey:
I don't have it in front of me.
Casey:
But there's a company out of Canada that basically does fake OEM wheels that, yeah, it's Replica, R-E-P-L-I-K-A.
Casey:
And they have a version of the wheels that I like that are like $150 a wheel.
Casey:
So it would be what, like 600 bucks or something like that for all four, which I actually think would be a reasonable alternative as well.
Casey:
But anyway, so we'll see what happens.
Casey:
I plan on test driving the stupid Accord, which I'm fearful that I'll actually love, in which case I don't know what I'll do.
John:
You should bring your family so they can bask in exactly how much room there is in that backseat compared to a Golf.
Casey:
That's very true, actually.
John:
Or any of the other cars you're looking at, frankly.
Casey:
Yeah, then I plan to test drive the Golf and I plan to test drive the GTI and see what I think.
Casey:
Really, on the one side, my life would be so much easier if I was willing to get an automatic.
Casey:
But the thing that occurred to me is I'm still not sure what specific car I would get.
Casey:
Even if an automatic was an option, what would I buy?
Casey:
And I don't know that it really changes anything.
Marco:
Yeah.
Marco:
Let me point out too, with your Jeep experimentation here, your very quick Jeep phase, and by the way, thank your dad profusely for making you not actually need to buy one to get this out of your system, right?
Marco:
That is true.
Marco:
Anyway, you've already said by trying the Jeep experiment, by almost convincing yourself to buy a Jeep, that fun and stick is more important than speed and luxury.
Casey:
yeah yeah so i honestly think you should give the accord serious consideration i know i should i just don't it's so boring i'm sorry john i don't mean that to be offensive but it strikes me so boring and i gotta drive it because i very well maybe not at all boring but i don't know it just nothing about it makes you go who's got car it's got carplay support does that make you go well that's about the only thing
John:
I would like that right now.
Casey:
Yeah, you would.
Casey:
So I don't know.
Casey:
I mean, this can be an exercise for the listener slash for me slash for you guys to think about.
Casey:
But I don't know.
Casey:
I just I don't know what I want.
Casey:
And that's the problem.
Casey:
And the right answer is probably to get nothing.
Casey:
I mean, if you look at my total cost of ownership of the BMW over the six years I've had it, it's been like 500 bucks a month.
Casey:
And it occurred to me when I don't have a traditional job.
Casey:
I could lift a lot of times for $500 a month, and it would not make me as happy, but it would save money, which right now would be very useful.
Casey:
So maybe we'll just be a one-car family.
Casey:
I don't know.
Marco:
$500 a month is a lot more than you would pay to lease something new that's fairly reasonable.
Marco:
If you wanted to lease a new stick version of an Accord,
Marco:
You're probably looking at well under that.
Marco:
Like, what's a decent Spectre-Core lease?
Marco:
Like, in the 300 to 400 range, probably?
Marco:
I don't know.
Marco:
I've never leased a car.
Marco:
I have no idea.
Marco:
It's probably in that range.
Marco:
Probably, like, 300-something, you know.
Marco:
I honestly think you would have... First of all, you get a lot more utility out of being a family person now.
Marco:
I mean, you had a second kid and bought a seven-seater SUV.
Yeah.
Marco:
So I don't see you fitting comfortably into a hatchback, into a Golf.
Marco:
You have the SUV.
Marco:
You got the Jeep out of your system.
Marco:
I think you'd be very happy with a sedan.
Marco:
You've been driving a sedan.
Marco:
You know you like them.
Marco:
You know they're practical.
Marco:
They're a great balance of good driving dynamics versus also having pretty good cargo space.
Marco:
And it's really hard to beat the accord for that, for the kind of variables that you are prioritizing.
Marco:
And
Marco:
When you're self-employed, things like being able to have predictable cash flow become more valuable to you.
Marco:
And when you do something like a lease, it totally gives you predictable cash flow.
Marco:
After all the costs of getting a lease started, you're probably into it for like under $2,000 and then you pay a couple hundred bucks a month and you know it's going to be only that.
Marco:
And you know it's going to be three years from now that's going to end and you can start a new one or you can do something else at that point.
Marco:
That kind of predictability is awesome when you're first getting started because what you want right now is more of your financial and hassle life that you can find a way to control and to make predictable.
Marco:
Because it's about to be very unpredictable in a lot of other ways.
Marco:
And so the more things you can fix down to a predictable level in both money and in hassle, the better.
Marco:
This is why I think no matter what you get, I think a lease is the way to go for you right now.
Marco:
And also, I think separately from that, I think you should also seriously consider the Accord stick, basically just copy John's car.
Casey:
Oh, I can't.
Casey:
I realized I can't have an Accord because don't they petulantly insist on putting the sunroof controls to the left of the steering wheel, which is barbaric.
John:
I have no idea where those controls are because I would never buy one with a sunroof.
Casey:
Every Honda I've ever seen is like that.
Marco:
At this point, can you really afford to rule out cars based on things like that?
Marco:
Where the controls are.
Yeah.
Casey:
what you want is so insanely specific well no what i want the problem is what i really what i want what i really really want is a three series is a new three series but i'm not going to do that to myself i know what you should really do is lease an m3 uh no sir no sir
John:
well it looks like you can get this accord really nicely done if you don't want to have a six speed yeah because it looks very luxurious on the inside when you look at the gallery uh yeah if you were saying like well what kind of car would i get if i gave up on the stick you can you know you can get the fancier accord without a stick with a 10 speed auto they have a 10 speed auto as the fancy option so you don't have to have the cbt but honestly it's gross you should get the stick it's a good stick