106: Sam Selikoff - Single Page Application Architecture

In this episode of Fullstack Radio, I talked to Sam Selakoff about single page application architecture and why you should think about building your client side apps like desktop apps. This is Fullstack Radio episode one zero six. Hey, everyone. Welcome to another episode of the Full Stack Radio podcast. I'm your host, Adam Wadden. And today, I'm joined by my friend, Sam Selakoff. How's it going, Sam? It's going good, man. How are you doing? Good. So the reason I wanna have you on the show again, you were on a couple months back, maybe longer than that. Time goes fast now that I'm an old man. We talked about kind of Ember JS and choosing Ember JS in the in the age of React. But something that I have been getting into conversations with friends about, lately and something I'd love to learn more about and I think you're the perfect person to talk to about it is just this idea of like building stuff for the web from a sort of front end first perspective where people are building these like really rich client side apps and I even see lots of people doing this who don't ever really talk about the back end. So I'm trying to figure out what are they even doing. Are they using Firebase? What does Firebase even let you do? Or are they building back ends? Or are they writing their own authentication? How are they doing session stuff? There's just so many different, things that I think people are doing differently when they're really focused on, like, the front end world versus what someone like myself who's more versed in a more of a full stack back end first sort of rails or Laravel style development workflow, you know, different than how I would do that sort of thing typically. So I want to learn more about how people do this stuff and and what sort of things they're keeping in mind and what technologies and stuff, they're using. So, yeah, I thought it'd be cool to talk about that stuff. Yeah. I think there's there's a ton here and, definitely, you know, with Ember having used it for five or six years now, it's kind of it always kinda went in on that. It kind of saw that vision of the future and kinda just said, we're gonna go whole hog on this from the beginning. And so, you know, your your back end layer is gonna be like a dumb API layer and you're gonna be focused on building like this fat client. So it kinda inverted that idea from before where you do most of the stuff in the back end and and then just sprinkle the JavaScript on the front end. You kinda flip that on its head and so yeah. For about five or six years, I think most of the Ember community has been building JavaScript apps in this way. Yeah. Awesome. So I …