Debate: Lightning vs Classic - Episode #299 of CloudFocus Weekly
Debating Salesforce Lightning, pros and cons, what we love and hate.
Machine transcript generated in 2026 from the episode audio (Whisper speech-to-text with automatic speaker separation). Speaker labels are automatic and may be wrong in places. Timestamps shown every few minutes.
00:11 Jason Atwood: This This is the 299th episode of CloudFocus Weekly for the second week of December 2018 If you are a Salesforce consultant and want to be part of a unique and growing company, send your resume to careers at arkusinc.com. I'm your host, Jason Atwood, and, and joining me 299 times in a row, co-host.
Justin Edelstein: I would amend the if you're a Salesforce consultant and want to be, part of a union, you can just say you're interested in Salesforce and want to be a new and growing R- and growing company. and-. F is not capital F. That's the way I used to capitalize it for all. My phone for some reason, it's to the capital F and it bothers me to know A. It's learning. But it's the wrong capital. Well remember too,
Jason Atwood: The old logo had that logo. But it was a different color F. It was sales with a red. Thanks for watching force. So you know, maybe that's why.
Justin Edelstein: Yeah. And visual force, I think, started to confuse people. It's like cloud focus, it's two words. Yeah. The camel case thing, because it's a techie thing, I think, is what gets people. Yep. So we have really low bar. Just don't capitalize the F and you're all good. Very low bar. Now you have to include the F. That has to be there. It can't be a sales source.
Jason Atwood: We need that. Our HR department would be very happy with this conversation.
Justin Edelstein: Well, they can take it up with me.
Jason Atwood: All right. Well, let's get to our very special episode again. Lightning experience versus classic, aloha. We're gonna do a little debate. We talk about it a lot, but I thought it'd be kind of fun to go over what are the goals that we love or don't love. Debate, again, not traditional. We're not going to get time and time, whatever, but let's talk about it. Sure. So we said the rules were we came up with five It was hard to pare down. It was hard to pare down. Sure. I was trying to go for big things, not like little things. Yeah, yeah, yeah, yeah, yeah. I'm running a little stuff all the time. All right. It's the little little things. And I will tell you, just like this running myth out there that I do like Astro.
04:18 Justin Edelstein: I do like Astro. You don't like Astro. I, do like Astro. like Astro, but you don't dislike Astro. You're neutral on Astro, like Astro's gender. You're just neutral on it.
Jason Atwood: No, I like Astro. I think I think it is cute. I love it. But so anyway, let's go beyond that. So it's lightning. I'm not against lightning. Like, I was just so just start just saying that has been a lot of my time.
Justin Edelstein: RYAN LAMBERT He's very anti-lighting. I'm anti-bad software. He's anti-lighting. Let's talk about it. Which he just called bad software. By the way. Ahhh, alright.
Jason Atwood: MBB status. Revoked. Revoked. Goodbye MBB. It's been five years, it's been fun.
Justin Edelstein: Nice knowing you. Emeritus. Hello. Yes. I don't think they do that. Hello Emeritus.
Jason Atwood: That's a... OK, so let's talk about it. So give me one.
Justin Edelstein: Ah, screw it. I'll leave it the same. All right, so this isn't necessarily a pro of a feature of lightning. I'm just I'm just making a comparison here. So I think of lightning lightning is to the user interface as classic is to the command line. So I'm just going to make that analogy right now. On the command line, you can be very powerful. On the command line, you can be very fast. You can be very efficient. There's a steep learning curve to the command line. And if you're a non-technical person, and getting on the command-line could be a little daunting. It's not graphical, it doesn't look like anything. It doesn't give me any like. feedback. It's mostly like green screen geeky stuff, right? But you can get a lot about this sometimes when we talk about the company that shall not be named that we used to work at where we worked on the broker desktop.
Justin Edelstein: I a green screen that was essentially a command line interface. You had to know the verbs, you had to type them in and get, but if you knew them, you were a speed the demon demon. And, and you didn't.. It was the thing that was innovated on and kept getting better year over year over year over year over year whereas the green screen thing got left behind and stayed there.
07:19 Jason Atwood: So what is the pro to lightning when you're talking about two user interfaces?
Justin Edelstein: Because when you're using lightning it actually puts more emphasis on the actual user interface and the user experience than classic does. Classic does what it does unless you want to go crazy and create visual force pages for things, a but related lists are where related lists are. That's it. You've got your home page, and that's it. You can put a handful of things, you want a full dashboard on your homepage? Too bad, build a custom homepage. In Lightning, you can do a lot more with the same platform in terms of putting data and actions and things, ways to do things. You can put so much more in one place that I think it's easier and more palatable for end users to learn than classic.
Jason Atwood: Okay, my con to that, maybe I'll just argue against your things. Well, that's what you're going to do. Well, I wasn't gonna, I didn't, I wasn't gonna go against your piece, but maybe I will. I find lightning to that while there are a lot, while I agree with that, there's also way too many clicks. They have taken through the UI and they've... taking things that were very quick and easy to do and were just one click away and they buried them sometimes under two, sometimes under three clicks and when you're doing stuff in a system that you you have to do over and over again, you know those clicks add up a relent and so with a new UI and all the sort of underpin pinning stuff of it, they didn't have to go and just start really really changing where things existed.
Jason Atwood: And I feel like they've made, I think there's too many clicks and lightning. That's my one of my biggest complaints. I go to do something I'm like this used to take this used to be right there, right in front of me. whether it's a report, whether it's a filter, whether it's a list view, and now it's three away. I'm like, oh man, I know how to do it here, but why do I have to go three levels down to go do this, this same thing that I do? But that's not always the case. You see, you're saying things that are sometimes true, but not always true. But a lot of common tasks that used to be very easy are now...
Justin Edelstein: That are now buried underneath and they're under multiple clicks. That's again a very common task is actually marking a task complete right? That's great! Right so when I want to mark a task complete in lightning I check the box next to the task yeah and it marks. It marks it complete.
Jason Atwood: That's very simple. You want to change the date range on a report? Hold on.
Justin Edelstein: Hold on. Are you going to talk over me, or are we going to have a civil conversation? No, it's debate. It's all, it's war. I'll just sit here then. You can do that what you're going to do? Yeah. of the it's three-clicks deep, it's whatever. Well, actually I can get to the list views of tasks really simply from right in that component, which is totally buried in classic. Show me my delegated tasks. Simple, I just change the dropdown to delegated, done. In classic, super hard to do. And then when I wanna mark them done, I just check the box. If I wanna do a followup task, I just create followup and boom, I can create a followup and it's super simple and that's something that people do all the time. So the argument of like, Things I do all the time are three, four clicks deep.
11:09 Justin Edelstein: Isn't always true. But they didn't have to bury.
Jason Atwood: That's fine. They took stuff that was, if. You really get into it completely broken in classic and terrible for 10 years like tasks, which were a broken, broken, broken set of functionality that nobody used in classic because they were terrible. Because you couldn't get to them. You couldn't do them.. And they made them much better. Look at that a pro. I told the pro. I agree with the pro, but. the con is they, but it doesn't mean a lot of stuff that was really easy and then they made it harder, but it doesn't a you didn't have to do both.
Justin Edelstein: There's no pro to tasks in classic.
Jason Atwood: Again, reporting, huge piece of functionality, so glared tasks, but you know, being being able to go in and I this is where I find myself over and over going back to classic. I'm like, I just want to get the thing I need to get done done. And then, then, sometimes I go back to the lightning because it's like, Oh, yes, yes, that thing is actually easier. The home page of lightning. Beautiful. But there are things that for no reason, well, actually, I know there's reasons behind them. There's uniformity and all the stuff they wanted to do. But I just I just wish they could have I wish they could have studied a little bit more and said hey listen We shouldn't take things yes things that used to take six clicks and now one great But don't take something that used to take one and make it six like don't reverse those courses make everything Less clicks anyway next one next pro
Justin Edelstein: I'm just going pro pro pro pro pro and you're just gonna like okay. Yeah so The the lightning experience Selves so the record pages the app pages the home pages The ability. Ability to build them once deploy them on all the devices Soon enough the mobile will just be lightning in a container essentially and the ability to just say, give me a blank slate page. I want it to render like this in these many columns. And I want to drop a bunch of list views and chart components and a couple of custom components, maybe from a third-party app or ones that you've built yourself and create like a launchpad for myself. Pretty cool as an admin to sort of be able to take over and just drop. like whether it be list views or what have you in these different layouts and have them work in the mobile nav and on the desktop nav in the same way.
Justin Edelstein: Really powerful stuff. You cannot do anything like that in classic, not even close. Agreed. Lightning pages. app pages, all that, super powerful. You didn't just mention apps.
Jason Atwood: Well, you're like, well, I would say components, which is the, I think the, you know, if lightning is made of anything. They could have renamed that instead of calling it lightning, which again, we could argue for days. It's called component. Component, because that's what it is. It is component. You know, the con to that is complexity. You can build really, really bad pages in classic. music R.I.P. The worst things you could do were have some bad looking page layouts, some stupid sections, and maybe put all your fields on the right hand side, like top the bottom on the right hand side. You could build some bad stuff, you could maybe take away a related list or not, or maybe you know 50 related lists. But really, you couldn't. You couldn't break it like.
14:36 Jason Atwood: It wasn't something that you could break. Lightning is so complex now with app pages and Lightning pages that you can build really, really, really, really bad UI. You can put things, you can name things that aren't the things that they are. So you can make a tab called Bob and underneath Bob are cases. It's like, oh, that's a great functionality. So, but there's also this. It's also much more closer to building software. And I think there's a set of people, admins out there who are admins and who can do a certain set of business process of fields and how to get things from A to B, but are not software designers and not software UI experts. And so I think there's going to be in the next wave of lightning. It's gonna be a lot of problems where people build really, really bad lightning stuff.
Jason Atwood: And... And we're going to have to shift our roles from being kind of administrators to having much better sense of design and UI. And there's all sorts of concepts around that that I don't think most people are studying. And I don't think Salesforce is helping out because they're not actually giving you the help to do that.
Justin Edelstein: Only if you want to. True. Right? Because you don't have to do any of this. True. And that's the pro is that you can. In classic, you cannot. Right. And you have to know how to write visual force if you want to create these types of pages.
Jason Atwood: But the con to that is it kept people from building bad stuff. as easy, you can easily build worse stuff now.
Justin Edelstein: That's their prerogative. I mean, giving people the options to do things more than less is always a good thing, I think. Great, not always. Too much power,
Jason Atwood: Not enough, good output. All right, how's my con? I was gonna pick little things, but I like this better. You just say something and I'll argue the other side.
Justin Edelstein: I believe navigation is superior. So between global actions being way more readily available. actions being way more readily available. The utility bar is just killer with with whether they be customer standard. The favoriting ability is really killer. I was showing that the other day to client like, here's I'm favoriting this record, this record, this record, this list view, this report. And they're all there for me now under one place where I can go and get to all the things I work on all the time. It's pretty cool. Records as tabs, again, I was with another client client, they do a very specific thing where they work with their fellowship program. They work with the same. Five contacts for about four months at a time while they're on their program and the ability to favorite them and then very easily.
Justin Edelstein: End user I'm going to work on this person today click done contact loaded don't to find them, don't have to go to a list of you called my contacts, done, they're just on the top. It's pretty neat. variable components on a page based on the data on the page, like show me different functionality based on what I'm loading. pretty incredible things that you can build in Lightning. If you have, you know, a decent brain in your head, or even, you know, just a little semblance of what you're doing, you can make some whiz-bang application stuff happen. really impressive. List views as tabs so you can get around the whole I land on a tab and I see my recently viewed stuff which you can't really get around in classic without what? Writing a visual force page.
18:28 Justin Edelstein: A lot of good workarounds for admins on this stuff. I think the navigation is awesome in the Lightning.
Jason Atwood: I mean, you go into lightning, and on your left side is a black bar, and it glared all these, icons in it that you can click on and there's the icon for opportunities. That's not the app for the navigation.
Justin Edelstein: That was what launched. That's what launched, but doesn't any, doesn't, haven't you learned anything about Salesforce over the years? That they make terrible mistakes? They launched it. They got. feedback, they changed it. It is now way better. My con is the missing stuff.
Jason Atwood: Navigation is better in some cases. I agree. There's so much you can do now with favorites and whatever and utility options. Don't forget the actions. They're just killing never hashtag never forget actions.
Justin Edelstein: Well, they're buried in like a chatter feed. I agree.
Jason Atwood: Here's here's some issues. There's a big missing holes from real navigation that was usable, that's not usable in Lightning. And that's back to ListView. Like this is something that two years later, we don't have an answer for. And the answer to go back in your browser window is terrible. That's not how you do it. You know what else is terrible? Oh, it's either go back to ListView because you can go underneath the tab and the drop down and go back to it. That's right. Terrible, three clicks away. Not three, two. And the other one was, go use your browser and back off with your browser. Do you know what's not very good in a browser? Lightning doesn't. You can also use console. You can interrupt me every time? I am.
Justin Edelstein: Oh, I'm just gonna sit here and be grumpy. Good, because you can use the console, right, in Lightning, which you don't have to pay a license fee for, which you used to have to in Classic. Yep, you just get console apps. and then you don't have to worry about back to ListView because you've got your ListView always open.
Jason Atwood: ListViews and going back to there. It's just back to there.
Justin Edelstein: ListViews are absolutely important. It's part of the workflow and then we removed it. What I'm telling you is it's there if you do a console app. You're in a ListView always in a console. I don't wanna be in a console app. Stop. Why? Why not? You love console apps. I like console apps. That's not true. I don't work in a console app. But you like them. I sometimes like them. I don't want to be in a console. Why? You like them. You build them for your clients all the time. Sometimes I do. Depends on the use case. Right. So in this use case where have a whole my big use case is, I have a list of things I need to do and I need to get back to them. Well, think about it for a minute and then build a console app.
Jason Atwood: No, how about this, take the feature that's in, that's in, that is extremely useful. Here's another example and bring it forward to lightning. Here's another example. There's inconsistency in the tab structure. So some tabs allow you to do new. Great, I can go quick down new account, right from the tab. Super awesome, totally met awesome, awesome size. Others, no, it just doesn't exist. They didn't build it that way. Some tabs in like tabs in classic when you're navigating, so just talk navigation issues. being able to click on the click on the on a tab, not two clicks, but one tab like a dashboard and land on the dashboard that was on. Just give me to the dashboard because that's the dashboard I was on last time. I love it. One quick, quick dashboard. Now it's quick list of dashboards.
21:52 Jason Atwood: Find the dashboard. Second, quick get to the dashboard or use the more or down two weeks or use the way better.
Justin Edelstein: Global search that actually searches through the dashboards, type in the name of the dashboard, and there it is. Click, I'm on the dashboard. Well, now you're talking, click, over to my keyboard, start typing things. Search is a great way to navigate. I know it.
Jason Atwood: And the fact that you can from the same place. And separate way, the research is on the same page. And it, get on the same setup. From the same place. Get it up. Then you have three searches on the same page. From the same... Side,
Justin Edelstein: Top, left. That's the same in classic. But that's the same in classic. Thank you, bye. OK, it's bad in classic too. So this is a lightning verse classic. You can't take something that's pirated and say it's bad. I mean, you can, but then it's bad in both places. So then you're just complaining.
Jason Atwood: Keep going. All right, that's my con. Navigation is fine.
Justin Edelstein: It's... I'll keep going. So I think the entirety of this system is more interactive. So you've got visualizations all over the place of charts, reports, even list views to have charts in a list view is pretty sweet. Just general visualization of the data is slicker. It is more appealing to the eye. You're not stuck with just the top three or two, the top row of a dashboard. Hey, want a dashboard with more than three columns? Go for it. Want that whole thing to show up on your homepage? Go for it. You can really get to your data and see it in a much more interesting way in Lightning than you can in Classic.
Jason Atwood: And that's the customer company. Well, it's true. You can.
Justin Edelstein: I mean, can you, in classic, go build a dashboard that has more than three columns? No. Can you change the size of them because all of this is showing a number?
Jason Atwood: It loads every time. And it loads fast every time. And it loads when I'm on a plane. And it loads with the correct data.
Justin Edelstein: Way to change the subject. No. You're saying can I just pop? I'm talking about being interactive with data. And you're talking about loading fast. That was two different things. Two different things. And the dashboards and the reports are correct. Oh no, sometimes they're not.
Jason Atwood: I have examples and put in bugs where the report and the dashboard are incorrect. The data on it is incorrect. I have bugs that I've submitted that are true. There's been data that's incorrect.
Justin Edelstein: So then you flip over to classic and the data is correct. And you flip over to lightning and the data is incorrect. In the dashboard. Yeah. Different thing.
Jason Atwood: Well, it's going to be the next one I get to. But you're saying it's like, it's this panacea. Hey, listen, again, I'm agreeing with everything you say. It's really awesome. The interactivity of data with you on lightning is great. Right? You can do, you can get to stuff and because of the way it's built and this more front-ended, modal, you know, pick list, everything kind of happens within the system as opposed to refreshing the whole page, which is classic, you know, you had to click and it would refresh and click again again, it'll refresh, and everything, it's all happening, you know, independent of each other. Much, much better. But for that, you suffer things, right? You suffer slowness, you suffer incorrectness, you suffer caching,
25:08 Justin Edelstein: You suffer other things. So like, it's running on the client. You suffer things like,
Jason Atwood: I mean, there's other little things I would say, like little features that drive me crazy. My big con this I'm just gonna throw it against this one and I'll use my other two for some other spot is Is the setup screens are broken just setup is broken in lightning. It's broken it's it's every time I go in there to do anything in lightning and Flip in between two different tabs and having things half load because it's loading the classic version from within Fin lighting which doesn't really work that well no matter how they want It's broken. In that we're two and a half years into lightning and still setup screens are not lightningized like it drives me crazy. Come on guys, get, go all the way. Don't leave set up as I know it's not the front face and no one's you know, know doing a fun path but don't leave, leave set up behind.
Justin Edelstein: Two and a half years later, six. Yeah,
Jason Atwood: The side search, the side set up search. it's. Nope. Search. Which. Global search.
Justin Edelstein: Okay. In the setup. See in classic when you load in when you go into setup that side left hand thing is both find and search and that's super confusing. and because it's find you start typing and, H, You can type any feature you're looking for and hit enter. That's. I would say is not as broken as you think it is and I Custom object is intuitive as an object manager.,
Jason Atwood: List them all. Yeah, try to search for any poral objects you have. Jason,
Justin Edelstein: I understand that there are issues with renaming and things of that nature, but you know that. Customize. Okay, seven releases. But what should be the focus? Should we focus on the admin? Or should we focus on end user functionality and allowing the admin to get them to, like get the end user to be more productive? What's better for your company? If you have 3,000. I'll go back to 500 pages of release notes. If you have 3,000 users and a team of five admins. Is it better to, enhance them for those Rive admins that their lives get I'm not arguing with better I'm saying not you definitely start just like they
29:22 Jason Atwood: Started with a sales because sales is the sales cloud. but I'm talking two and a half years later. It's gotten better. is When was Process Builder released?
Justin Edelstein: Maybe more. It's changed.
Jason Atwood: It's barely gotten functional. It is still a pain in the tuk tuk. It's a nice restaurant here in Long Island City. To go in and to try to deal with Process Builder stuff. to see fields, sorry, to see where it is, to get to the one you want, it is still, it is like, what is this lightning one, lightning beta? You can tell, that's when it came out, it was lightning beta. Here we are, years later.
Justin Edelstein: I mean, if you want to go there, then we can talk about all that is lightning- Mm-hmm. On the platform versus what is classic on the platform, and I guess process would be lightning? No. Process builder is- So process builder is noth- so it's the same UI- It's pre-lightning. It's the same UI, it's pre-lightning, same UI in classic as it is in lightning. What do you actually like-
Jason Atwood: The con that is, here's my con, that they have spent way undrafted time doing other little stupid things and they need to come back and do setup and not just leave it like it is because you and I have been around this platform for so long, you know there's still things you go in to do a setup on in Salesforce, right? And it's now, it's the three CRM releases. cases. You have the old CLI, you have the new Vision 1, and then you have the Salesforce 1, the three, ten years of it. There are still set up elements in Lightning, basically in Classic, but that are from like the release that are from 10, 15 years ago that are using old, old, old. And what I don't like is that they leave them that way.
Jason Atwood: Instead of fixing them and bringing them forward, they leave them. And I'm afraid that in five years, they'll still have all these old, old, old set up things will still be in class, you know, and whatever they're doing now, an embedded classic, right? Embedded classic setup. All right, what's your last one?
Justin Edelstein: I've already like said it a few times. Far better looking? Yeah, just, it's more appealing to the eye. And I think at... Like, I think that's a legitimate pro.
32:23 Jason Atwood: Like when you're- If you're gonna make a pro, you can make it, I would say, I'm gonna do a pro. Theming and the UI you can take over that UI and make it look and feel like the company and all that. That is an amazing feature and I think is really helpful for onboarding people, for brand identification. It's great. I love that. And that it inherits down like in our org, it inherits down into custom components and stuff. Amazing, amazing feature. That is pretty cool. But... There's an elephant over there. That I'm not riding. That we have to talk about. It's in the room now. Well, we got to talk about the elephant. The big, slow elephant in the room. You're talking about loading. I'm talking about lightning is still loading. Two and a half years later, maybe three now.
Jason Atwood: Three? It is still slower than classic. It's still a slower UI. And here's the thing that I think we're all gonna have to just get used to, it's never gonna be faster. It's never gonna be as fast. Lightning will never be as fast as classic.
Justin Edelstein: It will never be. And I think that that is the command line argument versus the graphical user interface argument. it. The graphical user interface is never going to be as fast as the command line. And that's why I wanted to sort of say that up front, which is classic is that. Listen, if you're if you've been around the block like us and you've grown up in classic, right, which we have, we've been in two different UIs of classic. Yep. You I think have been in three, different UIs of classic, right? The original, original, original than the one that was that predated this one. And then this one, which added a little more rounded edges to the buttons and stuff, and chatter.
Jason Atwood: Rounded tabs was chatter. And global search.
Justin Edelstein: We're always going to be a little faster in classic. But that's because we kind of know the click paths. And I think that because the screens load faster and we know where things are, we can get things done quicker. But in Lightning, you can. customize it to the Intuitively that feels better, right? Like, oh, I click on something, boom, it loads. That's like, that feels satisfying. That's what it's supposed to feel like. I click on something, it takes a second to load, like a full second, which feels like hours when you're sitting on the internet. But- Don't be on a plane. But you can also argue, like, web apps. apps. used to be faster than web apps are today in general. Like I remember like for the company that we will not name and working on their website and like working on a very specific page on that website that was more of an app.
36:03 Justin Edelstein: So typing in the quote page. But it loaded all these things. It loaded the quote data, the chart data, the news, the research, and all the fun stuff that you need to know when you get a quote. It wouldn't load as fast today, because it would load all sorts of things from all different places, and it would take a little bit longer to load. And again, I'm not like super front-end genius when it comes to like JavaScript and HTML5 and all that stuff, but I know enough to say I believe the classic UI and the Lightning UI, they're obviously running different front-end technologies and the front-end technology that lightning is running on is more future facing or future looking and for now it's going to be slower and it might forever be slower.
Jason Atwood: Yeah I totally agree with you there are productivity parts to it that make some tasks faster enlightening but there are still massive issues with act like for like click to click like not I'm going to load some crazy page but I'm going to get onto a lead. click lead, click lead, and the time differential. And I think it will always be slower, right? I will make the analogy, because another app that I use a ton, I use QuickBooks Online. And QuickBooks Online has gone from, you know, they went to this whole new UI, and the UI has slowed things down. It just has slowed things down. It's slower. It's just the way that these web apps are built these days. They're a little slower.
Justin Edelstein: It's relying more on the client. and to do more of the work than the server. And listen, there's a couple things that will help in the universe. One,
Jason Atwood: Our bandwidth is getting better and better 10 years ago we didn't have, you know, what you have a terabyte down in your house. I have a gigabyte. Oh, you have a gigabyte, not a terabyte. Correct. And then if I had to turn back, then we have browsers that, we browsers that are a better and faster and faster. I mean, all these things, all this is all JavaScript and CSS and what and every browser now is building their own. Own engines to run it faster and faster. So Safari and Firefox and Firefox and Chrome are getting. but. That being said, I still think there's too much reliance on or not enough paying attention to the fact that like things Shouldn't be that noticeable and it is still it is still too slow There's still there's stuff that they need to work on that to make this much much mean again.
Jason Atwood: It's not go from from where it is now to as fast as classic and everyone's just gotta stop because it's never gonna be as fast as classic. It's a different UI. That's why in my marketing world, I probably wouldn't have named it like the fastest thing on the planet. The thing that we say as fast as. Like you might've just named it something else I'd love for them to come out to that idea that has 25,000 votes on it, lightning, fast, whatever that I'm attached to. So I have, I see every post and it's, they get really nasty. I'd love for them to come out and be like, it's not going to be as fast as classic. Not going to be as fast, but be honest. Listen.
39:09 Justin Edelstein: But here's why. Here's why, exactly. Like you land on a page and there's a path. We have to load that path. You can put a path on any page. And like.
Jason Atwood: And make people more productive. Like be transparent, this is their big thing, trust. Salesforce, trust is important. Well, trust is being transparent. So come out and say it, open up the closet, show the big elephant in there and be like, yes, it's going to be, it's never gonna be as fast. But it's gonna have all this other stuff. And I think that's for us, it'd be better to go, okay, thank you, thank you for being honest. It's slower, we know it's slower, we're gonna try to always make it faster, but it's never gonna be as fast as classic. in a second., and just say it.
Justin Edelstein: Say it! Right. I think they can do that, and like, and say it the way that we're saying it, where it's like, yes, like for like, click for click, it's a little slower, but at the same time, when you get to that page, it's because we loaded a whole lot more stuff, and you can do way more things in an easier way. Okay? As opposed to just not on the load, the saving time on the other thing. Not on the load will save you when you're doing the work. Not on the load of the page. Would love that. If they just came out and did that, because that's the truth. It's fact. It's fact, Jack. When we load our, like, we've done some nice stuff on our pages, but when we load them, like, hold on.
Justin Edelstein: Your arm OK?
Jason Atwood: Yes, I was waiting for a page to load. I just want to make sure you don't break your arm like pat yourself on the back. How good are orgas? It's not that great. It's fine. Everything is fine.
Justin Edelstein: For those of you who got that, you're welcome. Yeah, whenever we load one of our pages, we're not just loading the detail and then lazy loading the related lists, because that's what happens in classic. It's like, yeah, load the detail real fast and then, yeah, we'll see some spinners on the related lists. That's fine. We're loading like... tons of data on these pages and you can kind of tell that they're still in the sort of weird old architecture because if you click on one of our pages that has some of those like update like those record lookup update standard components like because we have a couple with like lookups to contacts where you can just inline edit the contact just because it's in a lookup on some field which is pretty pretty sweet. I'm glad it's loading those records.
Justin Edelstein: So if you flip right back to classic and you go look at your recent items, you'll see, whoa, I just loaded that one page, but for records loaded. Yeah, that's what's happening. Right. Yeah. And it's very clear when you jump back to class, you're like, Oh, that page that I clicked on that when I click on it in classic only loads that record it actually loaded like four records.
Jason Atwood: That's the thing they should do. So I'll give you the analogy. So Salesforce, you're listening. Anybody listening. It's member when and 10 a gate. Remember in 10 a gate? You're going to give me puppy eyes. I decide that. What are you talking about? In 10 a gate was apples when they released whatever that iPhone. Oh, yes. I remember. And I remember then they came out and they said, A, there is a problem.
42:17 Justin Edelstein: This is so just for those who aren't this is when they moved the on the iPhone. I think it was the iPhone three or three G. I think it was more high. I know it was early on. I remember it was very early on. And they put the antenna into a band. Yep. That just went around the entire phone or at least the top three quarters of the phone. And when your hand was holding the phone, the fact that your fingers were touching the antenna kind of screwed up the- I think it's when you put a little gap, and if you put your hand over the gap to make them connect. It kind of screwed up the connectivity. Yes. And Apple recognized that, and then they go ahead.
Jason Atwood: So what they came out, they said, A, we know it, right? It's a thing. We messed this up. Here's some bumpers, remember?
Justin Edelstein: Yeah, you had to download their app. up. and they would recognize that you had that phone and then you could say, send me a bumper, and they'd send you a bumper.
Jason Atwood: But then they did, then they showed, which I thought was better, which I think Salesforce should do, is kind of get to this, but they should publish some sort of white paper, slash video, or something, maybe a lot of Astro. Here I am, I'm testing the speed of lightning. I don't know. You I don't know why Mickey Mouse came out, but like get, show all the work that's going on, show the component, like publish a thing that kind of really shows it and shows the work you put behind it and that you thought about this stuff because what it looks like to us is like, again, I'm not the typical user, but when I read the posts that are up there on that idea exchange idea. It's just brutal and it just looks to the typical user like you made it slower Right like show that you did show what we're talking about But like publish it and talk about it and be open transparent about it because it's just the ignoring the issue and kind of being Like well, you know, why do you think it's slow?
Jason Atwood: It's like Why do you what do you think?
Justin Edelstein: What what what is it that is slow? What do you mean?
Jason Atwood: Get in there and really dig in. I think that would be I think that'd be better better off overall All right Well, that's it.
Justin Edelstein: 299 down. 299 down. That's crazy. One to go. One to go. All right.
Jason Atwood: So later this week, we are going to publish our, we're going to record our 300th. But we will not publish it until the week after, just saying, because it's got a lot of things around it. Right. So we have to make right. Because it's a special episode, obviously.
Justin Edelstein: So we're thinking it'll be published the week of the 17th. So not this week. Not this week, but next week. The week of the 17th. week and 17th so you'll have and then by
Jason Atwood: The way that will probably be our last podcast for the year yeah we're gonna end on a high note oh yeah that might be it this was actually i think this was a pretty good podcast objectively other than you getting grumpy with me and like threatening to walk off the podcast like six times that's really that's very normal i mean that is
Justin Edelstein: Just not Maybe we should that's not a special thing that happens all the time when you when you threaten to walk off the show That's some people's favorite part of this show some Like when you become a prima Donna like some people's favorite part of this show is what I decide to just stop talking You're Robert De
Jason Atwood: Niro and you're like if I don't get my M&Ms in my suite. I'm not gonna do this show Do this thing? Okay, your green room your green room. I need my green room only the green M&Ms listen Only five stars and above.
45:27 Justin Edelstein: Five star Annie. Five star Annie for me when it comes to the green room and all things podcasting. But I'm super excited for next week for the 300. This week, we're recording it this week.
Jason Atwood: We're recording it now. Oh, right, duh. Recording it. And this is why he's the best of business folks.
Justin Edelstein: No, but we're doing it next week. That's when it's being published. Nice try, nice try, but no. You couldn't let me have that one? No, because you're wrong. I got to admit it.
Jason Atwood: Oh, my phone's ringing. OK. Yeah, got to go. All right, well, we'll see you. We'll record this week. You'll get the next episode next week, but we're recording it this week. Until then, it's Justin, maybe, and Jason. For the maybe second to last time on the planet. Sort of, kind of, maybe. Saying enjoy those cloudy. days.
Justin Edelstein: You
