Steve Greenblatt

So today, Dan is going to ask us some questions and help to moderate the conversation.

So I'll turn it over to you.

Yeah, I was interested to hear how James would take this because I think it's an easy argument for us because of our background to always say that centralized is the way to go because we're programmers.

Programmers like to be able to have the ability to perform and not minimize what we do and our livelihoods.

by putting it into different devices or taking away the magic that we used to create.

That's really what it was when I first started doing this.

People would be scared to press a button because you're talking about these way before touch panels were mainstream and way before we had phones in our pockets.

um, that, that had screens on them.

They were just buttons.

So, um, the things that I thought of, you know, because I think it's an easy argument to say that we want to go the, the centralized route.

And I was thinking about, there's a lot of products out there more and more that have control capabilities built in.

So when do people use stuff like that?

And when is that, that, when, what, what, what is desirable about it?

Um,

Because obviously manufacturers are spending the money to put it in and therefore people must be using it or it must be in demand.

So the things that I thought of are situations where you have isolated systems that aren't going to change a lot, that

don't require a high level of customization or expertise, and you are going to leverage the UI, the experience that the manufacturer has invested in developing.

So Zoom, I think, is a good example where we all are very comfortable with Zoom.

Zoom's probably put a lot of time into making

their UI and to, to be something that's user friendly.