Frameworks, Domains, and Data Efficiency

Speaker 2
I have four inboxes, and I think the smallest number has like 4,000 unreads. Oh,
Speaker 1
my goodness. See, Nick and I actually entirely align on this topic. This might be one of the only topics, that and Safari as your default browser, where we just are in complete agreement. So this is amazing, Nick. You and I, now we're partners in crime. We're friends forever. Yes. Well, we want to get to know Amy. She was also on a JS Party episode called Should Web Development Need a Build Step? Maybe you guys recall that one.
Speaker 3
I do. K-Paul does not. But
Speaker 2
I'm already seeing right now that we are on the same team on tabs, probably email inbox, all sorts of things. So it's destined. Yes.
Speaker 3
We're like the same person. Yeah,
Speaker 1
Maybe this time cable will remember you. All right. We are going to get to know Amy a little bit here by playing a little game of 20 questions. However, due to budgetary constraints, we could only come up with 10 questions today. And so it's actually going to be 10 questions because also 20 questions, that's just a lot, you know? So we're going to do 10 and we're going to to do it in a round. We've all written our own questions down. When it's our turn, we're going to read our questions exactly as written. Amy will then respond. Are there any questions about how this is going to work? What
Speaker 2
if I can't parse your writing, Jared? Well,
Speaker 1
you wrote it on yourself earlier, and now you're going to read back what you wrote after I send it to you.
Speaker 4
Okay. Jared, can you remind me where I wrote down my questions? You're
Speaker 1
going to have them in your Slack DMs with me. That's where you always write all your really private thoughts. Am
Speaker 3
I responding as written?
Speaker 1
Yes. We'll also give you the answers. You can read those back to us as well. I will go first. Question number one for Amy Dutton. You have to pick a web framework. You can't pick Redwood, by the way. Amy, a core contributor to Redwood.js. You can't use Redwood.js. So take that one off the table. What framework do you choose?
Speaker 3
Oh, man. Does it have to be JavaScript? Anything you want. No, it doesn't have
Speaker 4
to be JavaScript. It can be TypeScript. This is your answer. Nice. Oh,
Speaker 3
man. If it's TypeScript, JavaScript, then I would pick Remix. I love their data loader pattern. I like having a very distinct place to load actions, define form actions, and then display the content. Nested pages is wonderful. They're doing some stuff right now with their router, which I'm really excited about because of React Router 7. If I did pick non-JavaScript, I would say Laravel. I've kind of been, I've just heard several people say, we want the Laravel framework for JavaScript. So I've been trying to figure out, okay, what does that mean? What does Laravel have that we don't feel like we have in the JavaScript ecosystem? So I've been pretty impressed with what they have. And I think that if we really want that, we could have it. But the question is, do we really want it? Because we also love our composability. Can
Speaker 1
you give a quick diff? Like, what is over there that's not over here? Well,
Speaker 3
some things Redwood now has, but they have background jobs and cron jobs, which Redwood does have. They have file storage built in. They have auth built in. They also have some pretty cool build tools with their CLI and then Herd lets you get an environment up and running pretty quickly. So it's not like you even have to install PHP or MySQL on your machine. You just run their app and you have your local environment working. Awesome.
Speaker 1
All right. Question number two comes from K-Ball.
Speaker 2
All right. Checking where I wrote this down. Would you please please please share a spicy take with us good
Speaker 1
question take
Speaker 3
yeah
Speaker 1
you got any spicy takes i
Speaker 3
have tons of spicy takes it just depends on your level of mild to medium hotness oh
Speaker 1
let's get super spicy i
Speaker 2
was gonna say there was only one spicy written here, but there were three pleases. So I think we're looking for spicy. Oh,
Speaker 3
man. I think, okay, this is going to be spicy. Maybe not. WordPress is on the way out. It powers 30% of the internet right now, which is ridiculous. But I just think that Matt is making some poor decisions that might drive it into the ground. Do
Speaker 4
you think it's going to be replaced with something that's a fork, like Amy Press? I
Speaker 3
have thought about that. Like any good developer, I have thought, I could build that. I should build that. Let me buy a domain for that.
Speaker 1
Oh, yeah. You're a domain collector, aren't you, Amy? Yeah,
Speaker 3
I bought some the other day.
Speaker 1
Some? Like a plurality of domains? Yeah,
Speaker 3
I bought like four or five. Wow.
Speaker 2
Who among us has not? I
Speaker 3
mean, that's the first thing. The problem is I think of a good, decent domain name, and then I thought, well, now I need to get all the permutations of that. Oh,
Speaker 1
it's expensive.
Speaker 3
Yeah.
Speaker 1
So how many domains do you own at the moment?
Speaker 3
Well, my Notion document is not up to date. This I like to keep suspenseful, get people guess. Like I've never.
Speaker 2
It's like browser tabs, right? Like who really counts those things? So the correct answer is too many.
Speaker 1
Just like browser tabs, too many.
Speaker 3
There's probably close to 170. Oh,
Speaker 1
wow. Nick, how many do you have? Oh,
Speaker 4
I thought I had a lot and I have like 30.
Speaker 3
I've
Speaker 4
been on a dad kick.
Speaker 3
Ooh. We did cover this one in the thousand tab episode. Yeah, we did. But any guesses to the most expensive domain name that I own? I
Speaker 1
think I know this one, so I'm going to defer to the other guys. $2,000.
Speaker 4
$2,000.
Speaker 1
It's $70
Speaker 3
for renewal, I believe, but it's.fm. So I do have compressed.fm, and I am using it, so that makes me at least feel a little bit better about life.
Speaker 1
There we go. We have a lot of those FMs hanging around. So
Speaker 3
expensive.
Speaker 1
All right, we'll go to question number three now. Nick, this question is yours. And check your DMs. You have to read that verbatim
Speaker 4
because
Speaker 1
you wrote it verbatim. What's
Speaker 4
the most overrated technology right now? And why is it TypeScript?
Speaker 1
What? I say under duress.
Speaker 2
Jared, you're really, really utilizing this format here. I
Speaker 1
don't know what you're talking about. Nick wrote that down earlier.
Speaker 2
I can't wait to find out what else I've written down.
Speaker 3
Overrated technology. That's a good question. Ooh, I'm not sure. It's definitely not TypeScript. Yes.
Speaker 6
I
Speaker 3
do love TypeScript. I don't understand. Maybe I should ask this. Why do you guys hate on TypeScript so much?
Speaker 1
We don't. Oh, it's just me. It's
Speaker 2
just Jared. It's literally just Jared. And I think the answer is he hates on it because Nick loves it.
Speaker 1
That's right. Here's the problem. Podcasts where everybody agrees all the time are just not very interesting.
Speaker 4
And so
Speaker 1
we need a dramatic foil. And Nick is my dramatic foil. So whatever he says, I just take the opposite stance, except in box zero, in which we're incredibly aligned.
Speaker 3
GraphQL would be another one where I feel like people hate it, but I love it.
Speaker 1
So taking a different angle at this question, why do you love GraphQL? This is not a count as a question, by
Speaker 2
the way. Because,
Speaker 3
so this is like inflation, right? You have 10 questions and inflate
Speaker 4
it. Sculpe creep is what it is. He's taking
Speaker 2
the questions up to 11. I got it. I got it. Hey,
Speaker 1
K-ball, good one.
Speaker 3
I just love that there's not overfetching of data. It's like, this is what I need, and so then it gives me exactly what I need back. And I just feel like it's easier to work with. Whereas if you get a REST object back, you've got to traverse it, you've got to parse it with GraphQL, I get something that looks kind of like JSON, and I can just use it. It's perfect.
Speaker 1
So from an end user perspective, from a front-er perspective, but not from an implementer perspective. Well,
Speaker 3
I don't know if I'm supposed to talk about Redwood, but Redwood makes it pretty easy to do all that stuff and implement, because it has generators and things like that. So I would say my one complaint with GraphQL is you feel like sometimes you're having to rewrite the same thing multiple times, because it's like, oh, you've got to write the resolver and query and then the mutation and all these other pieces where Redwood will generate all that duplicate-ish code for you.
Speaker 2
Probably not a problem in Redwood because you're doing TypeScript the whole way. But another nice thing about GraphQL is it allows you to be auto-generating typing across a language interface, for example. Yeah,
Speaker 1
it really speaks to the advantages of going all in on a technology and really leveraging it for what it's good at. And I freely admit that that's one of the nice things about TypeScript is that.

Kind of a big deal (JS Party #344)

Changelog Master Feed

Remember Everything You Learn from Podcasts