TRANSCRIPT 🔗
WEBVTT
00:00:00.800 --> 00:00:04.480
Hello everyone and welcome to another episode of Code and the Coding Coders Who Code It.
00:00:04.559 --> 00:00:07.839
I'm your host, Drew Bragg, and I'm joined today by Delaney G.
00:00:08.080 --> 00:00:11.679
Delaney, I'm gonna let you pronounce your last name since I keep screwing it up.
00:00:11.839 --> 00:00:16.559
And also give us a brief introduction of who you are in case folks don't know who you are.
00:00:16.879 --> 00:00:18.960
Sure, my last name is Gillilin.
00:00:19.359 --> 00:00:21.359
It is phonetic, but it is hard to say.
00:00:21.440 --> 00:00:29.280
So, yeah, my background is I've kind of been in and out of the web space for since the original dot com rush.
00:00:29.440 --> 00:00:35.280
And for me, it was more of an interesting platform because it's the one sandbox that everyone can kind of agree on.
00:00:35.439 --> 00:00:47.359
So I've done a lot of interesting stuff around gambling, video games, military applications, all using the web more as a platform and a sandbox than in the way that it's normally intended to be used.
00:00:47.439 --> 00:00:52.159
So I've kind of used and abused GLSL and all kinds of crazy stuff to do some interesting projects.
00:00:52.399 --> 00:01:15.760
But in doing all that, I kind of came to a moment where I'm like, this is too hard, this is crazy, this is the wrong thing, and started with first principles, ended up with this project that's now called Datastar and some other projects around it to basically try to fix the web, not just take it back to the early 2000s, but actually use the modern web with the simplicity that we missed out on from those days.
00:01:16.000 --> 00:01:18.239
So that's kind of what I'm now known for.
00:01:18.319 --> 00:01:21.280
Unfortunately, I ironically hate JavaScript.
00:01:21.359 --> 00:01:25.599
So the idea of being known as a JavaScript framework author makes me really sad.
00:01:26.000 --> 00:01:28.799
But sometimes you have to have someone that hates something to make it better.
00:01:28.959 --> 00:01:34.640
So you hate it, so you want to do less of it, and you figured out a way to make yourself have to do less of it.
00:01:34.879 --> 00:01:35.599
I guess that.
00:01:35.760 --> 00:01:35.920
Yeah.
00:01:36.560 --> 00:01:40.319
So the way this is gonna work for anyone new to the show is I'm gonna ask Delaney three questions.
00:01:40.400 --> 00:01:46.640
I'm gonna ask him what he's working on, kind of blockers he has, and what's something cool, new, or interesting that he wants to share with all of us.
00:01:46.799 --> 00:01:50.079
It can be something he recently read, discovered, learned, built.
00:01:50.159 --> 00:01:54.400
It doesn't have to be coding related, but this is code and the code encoders who code it.
00:01:54.480 --> 00:01:55.760
So it absolutely can be.
00:01:56.000 --> 00:01:58.239
So let's get this party started.
00:01:58.719 --> 00:02:02.959
In pre, I was expecting you to say, I'm working on Data Star.
00:02:03.280 --> 00:02:05.760
But according to you, Datastar is done.
00:02:06.079 --> 00:02:10.719
So before we dive into Data Star, what are you working on?
00:02:11.039 --> 00:02:15.360
You know, I'm just trying to do a quick little in and out project, 20 minutes in and out.
00:02:15.520 --> 00:02:18.240
I'm just trying to fix the web completely.
00:02:18.639 --> 00:02:20.879
So yeah, I have some attempts at that.
00:02:20.960 --> 00:02:25.199
So basically, I think HTML for the most part is a really good declarative syntax.
00:02:25.280 --> 00:02:26.960
So that's kind of good enough.
00:02:27.120 --> 00:02:27.759
That's fine.
00:02:28.560 --> 00:02:33.840
JavaScript has been a bane for everybody, and so I fixed that with Datastar.
00:02:34.159 --> 00:02:42.960
And I have one other project which is basically I understand all the reasons why Tailwind exists and why it was built, but it doesn't match the modern web.
00:02:43.120 --> 00:02:50.800
So I built a thing called Stellar, which all the problems that you have with Tailwind are now solved with Stellar, which has just come out.
00:02:50.960 --> 00:02:53.599
So basically, I'm just trying to solve the web first.
00:02:54.000 --> 00:03:01.759
The irony of all this is that I built all these things because I was starting to build my own database and said, man, I would really like to have an embedded UI that looks really nice, that works everywhere.
00:03:01.919 --> 00:03:04.159
Hey, the web would probably be the best way to do this.
00:03:04.400 --> 00:03:09.199
So the irony is I've now pretty much solved the web so I can go back to building my database.
00:03:09.520 --> 00:03:11.759
So it's like a three-year journey in and out.
00:03:12.080 --> 00:03:14.240
Yeah, it's super easy to just solve the web.
00:03:14.400 --> 00:03:14.639
Yeah.
00:03:14.879 --> 00:03:15.919
Can't be that hard, right?
00:03:16.319 --> 00:03:18.240
I mean, the thing is that we're pretty close.
00:03:18.400 --> 00:03:27.840
That's the people I don't think people realize because there's so much hatred for the NPM node module black hole and like the sysyphis and task of getting something built nowadays.
00:03:28.000 --> 00:03:31.520
But yeah, the actual platform is pretty solid.
00:03:31.680 --> 00:03:33.919
There's a lot of things that are really great about the platform.
00:03:34.080 --> 00:03:41.120
We just have done this crazy layering on top that's made it very hard for people to see how much has been solved in the meantime.
00:03:41.439 --> 00:03:41.840
Sure.
00:03:42.400 --> 00:03:44.159
Yeah, we can actually get back to that.
00:03:44.400 --> 00:03:44.719
Yeah.
00:03:45.120 --> 00:03:48.240
The first web pages I ever wrote, I was like, this is so cool.
00:03:48.479 --> 00:03:51.919
And then I learned React, and at first I was like, this is so cool.
00:03:52.000 --> 00:03:56.000
And then I started maintaining like React spas, and I'm like, this is no longer cool.
00:03:56.159 --> 00:03:56.400
Yeah.
00:03:56.560 -->
Load full transcript
00:04:06.080
This feels way harder than the stuff I used to do for not much benefit, which the reactivity part of it is super cool.
00:04:06.240 --> 00:04:17.199
Like we have some React at work, very small amount because it's designed to solve a very small problem we have of a high user interaction part of our app.
00:04:17.680 --> 00:04:33.199
But it sounds like, at least from reading through the Datastar guides, and for anybody who doesn't know, I learned about Datastar when I had a recent episode go out where we were talking about live components and it was very reactive view components.
00:04:33.360 --> 00:04:36.480
And someone was like, This is really cool, but datastar already solved this.
00:04:36.560 --> 00:04:37.680
Why don't you talk to Delaney?
00:04:37.759 --> 00:04:39.279
And I was like, I don't know Delaney at all.
00:04:39.439 --> 00:04:40.639
Now I know Delaney.
00:04:40.800 --> 00:04:47.920
And after looking up some Datastar stuff, it sort of sounds like, why would you use React when Datastar exists?
00:04:48.160 --> 00:04:49.360
It's a really good question.
00:04:49.439 --> 00:04:53.759
And the thing is that this isn't born out of like me being a contrarian.
00:04:53.839 --> 00:05:06.399
The irony is I've put out, like I used to have top secret clearance and I worked on a bunch of military stuff, and I would use the web because it was very hard to get a binary to go through all the processes of being signed off on.
00:05:06.480 --> 00:05:07.600
Like there's a lot to do there.
00:05:07.680 --> 00:05:12.560
Whereas making a web app basically allows you to get things sandboxed in a very good way.
00:05:12.639 --> 00:05:20.560
So to me, it was a deployment platform, and I was doing really low-level stuff, but I was basically pushing against Vue and React install it.
00:05:20.639 --> 00:05:24.079
And I basically got into the weeds of like, okay, this isn't good enough.
00:05:24.240 --> 00:05:25.519
How do we fix this?
00:05:25.680 --> 00:05:27.759
And I started like trying to fix it.
00:05:27.839 --> 00:05:32.160
And what I ended up doing is basically the equivalent of Phoenix Live View.
00:05:32.319 --> 00:05:33.680
Because I was doing a bunch of spa stuff.
00:05:33.759 --> 00:05:36.639
Like I know the internals deeply of View and React and all that.
00:05:36.720 --> 00:05:39.040
Like I got into the weeds trying to say, okay, how do I fix it?
00:05:39.199 --> 00:05:49.360
And I basically made a Go version of that protocol where it's basically doing the equivalent of diffing on the back end and sending down the diffs, then you update that and then you get a live over WebSockets.
00:05:49.519 --> 00:05:55.040
And the irony is I spent a year and a half on that, making a really low-level binary protocol.
00:05:55.360 --> 00:06:01.199
And I looked at some stuff from like an HTMX example, and it was faster and better than the thing I did.
00:06:01.439 --> 00:06:09.920
So the irony is that I will throw shade at the spa community completely
because I was part of it and it said, hey, I'm trying to do it this way, and it's just terrible.
00:06:10.079 --> 00:06:20.079
And the weird thing is for people that don't know Datastar, we are even like people compare React or something and Hotwire in size, like oh, hotwire is so much smaller and stimulus.
00:06:20.240 --> 00:06:22.319
Data star is five times smaller than hotwire.
00:06:22.800 --> 00:06:23.360
It's tiny.
00:06:23.839 --> 00:06:29.360
It's 11K, it is the world's fastest signals library, it's the world's fastest morphing strategy.
00:06:29.519 --> 00:06:34.879
It does all this in 11K, and it is dead simple to do.
00:06:34.959 --> 00:06:36.560
And it's also language agnostic.
00:06:36.720 --> 00:06:47.120
So the thing is, what you can do is what you learn from, hopefully, we'll get into is that as a Rubyist, you can be using the same style of mental model as you would in C or any other language.
00:06:47.279 --> 00:06:53.279
So you can actually have a community of people that are actually talking about the web again, not talking about this framework of the week.
00:06:53.439 --> 00:06:57.600
So the weird thing is we're a back-end agnostic backend framework for the most part.
00:06:57.839 --> 00:07:03.759
But we still have when it comes to reactivity on your page, we are literally the fastest thing there is in the world of JavaScript.
00:07:04.000 --> 00:07:10.720
So we're in this weird dichotomy that we believe most of your state lives in the back end, but the stuff that you do in the front end, we are by far the best in class.
00:07:10.959 --> 00:07:12.480
Nothing competes right now.
00:07:12.800 --> 00:07:14.399
Yeah, it does seem that way.
00:07:14.639 --> 00:07:19.040
I haven't fingers to keyboard played with it, but I've seen a few videos now.
00:07:19.199 --> 00:07:27.279
I've gone through the guide a handful of times, like at various levels, and the dead simple part is 100% accurate.
00:07:27.759 --> 00:07:32.399
I think it was really smart to just use the data dash attribute.
00:07:32.639 --> 00:07:40.639
The one thing that I guess threw me off or prevented me from just being like, oh, HTMX clicks is like it's HX-whatever.
00:07:40.720 --> 00:07:42.959
And I'm like, okay, whole new set of things to learn.
00:07:43.120 --> 00:07:48.160
But like data-anything just feels like it belongs in my HTML anyway.
00:07:48.399 --> 00:07:52.480
Well, here's the thing that I've gotten into fights with Carson, who's the guy behind HTML.
00:07:52.639 --> 00:07:54.959
I love what they're doing there, but like it doesn't go far enough in my opinion.
00:07:55.040 --> 00:07:56.480
Like it doesn't solve the whole problem.
00:07:56.560 --> 00:07:59.519
It's a library, not a framework, first of all, and that's fine.
00:07:59.680 --> 00:08:01.680
But it also doesn't actually solve the problem.
00:08:01.839 --> 00:08:07.759
Here's a perfect example of I follow the specs of HTML specifically.
00:08:07.839 --> 00:08:21.120
And the reason why is there's already, for people that don't know, there's data-star attributes are part of the spec that says you can put any string in there that you want, and it becomes an insertion mode key value store that you can do whatever you want with on that element.
00:08:21.600 --> 00:08:34.240
The reason why that's important is because you put a spot into it, that means that the back end, the actual like turbofan and the optimizers and all that stuff, they know that that data set exists and they do all the right calculations on that.
00:08:34.320 --> 00:08:41.120
So instead of trying to deal with unknown attributes and do all kinds of crazy stuff, you're actually letting people optimize for the optimized case.
00:08:41.279 --> 00:08:47.360
So the thing is that in Datastar, we actively tell you we don't wrap things and try to hide things.
00:08:47.519 --> 00:08:50.720
Most people come in and go, oh man, I didn't know this existed in HTML.
00:08:50.799 --> 00:08:52.399
Oh, I didn't know this existed in CSS.
00:08:52.720 --> 00:08:54.159
We are not trying to hide things from you.
00:08:54.240 --> 00:08:59.279
All we're trying to do is get to a declarative, reactive expression, and that's it.
00:08:59.440 --> 00:09:01.919
Because the thing is, those don't exist in JavaScript.
00:09:02.000 --> 00:09:10.000
And what I mean by that is like when you set up a Excel spreadsheet and you're doing formulas, you're setting up a reactive relationship between things, right?
00:09:10.080 --> 00:09:16.080
When you say like this plus this is the sum of these two other cells, that kind of thing, you're setting up relationships.
00:09:16.240 --> 00:09:21.200
The thing that's built into the browser doesn't have that concept of like, oh, this thing's gonna drive this thing, this is drive thing.
00:09:21.360 --> 00:09:28.480
So all we do is data star, and the reason why it's so small is we just say, how do we turn this into a reactive expression?
00:09:28.720 --> 00:09:30.320
And then everything else is a plugin.
00:09:30.639 --> 00:09:31.279
Literally everything else.
00:09:31.360 --> 00:09:33.919
So the core of data star is actually about three kilobytes.
00:09:34.240 --> 00:09:35.840
So everything's a plugin after that.
00:09:35.919 --> 00:09:47.919
So you get things like data class, data adder, data this, but it's really a paradigm shift in the way that most spaws and stuff, or even hotwire, all that, they're trying to wrap things and try to like make their own little ecosystem.
00:09:48.080 --> 00:09:51.759
Data star is just like saying, what are the things that are missing to make this declarative?
00:09:52.080 --> 00:09:53.679
And then everything else gets out of the way.
00:09:53.759 --> 00:09:54.080
That's it.
00:09:54.480 --> 00:09:56.080
It gives you a very simple concept.
00:09:56.399 --> 00:10:12.720
Yeah, and the idea of signals is pretty interesting to me, where it's like that's the thing that when this value changes, there's like a cascading effect of like, if
you're listening to this value, everything's gonna get run, whether it's a full-blown expression or it's just a display.
00:10:13.039 --> 00:10:15.440
And that makes a lot of sense.
00:10:15.679 --> 00:10:20.720
That feels slightly reacty, but I like that those signals.
00:10:21.200 --> 00:10:26.320
Well, I guess talk a little bit about the signals and how you want them to be used properly.
00:10:26.559 --> 00:10:29.039
Because I have all kinds of goofy ways I could use them.
00:10:29.279 --> 00:10:37.600
Well, the thing is that most people coming from a spa background, which is most people coming from the web nowadays, they want to use signals everywhere, like all the signals all the time.
00:10:37.840 --> 00:10:47.840
And there's examples, most examples in Datastar, unless you have like inputs that where you're actually binding to someone's input that they're allowed to change, there's very few signals on a page.
00:10:47.919 --> 00:10:55.120
That's the irony, is that even though Datastar has the world's fastest signals approach, we say you should only have a handful of them on the page at any one time.
00:10:55.519 --> 00:10:59.600
So it's one of those weird things of like we can handle 10,000 signals on a page, no problem.
00:10:59.840 --> 00:11:04.559
But why are you putting 2,000 things on a page as opposed to just the things that people can interact with?
00:11:04.720 --> 00:11:10.799
So there's a big move towards what's called isomorphic rendering, which basically means your back end looks like your front end.
00:11:10.879 --> 00:11:12.639
And I think that's complete hogwash.
00:11:12.720 --> 00:11:13.519
It doesn't make any sense.
00:11:13.679 --> 00:11:16.799
The thing is that state needs to live where state lives.
00:11:16.960 --> 00:11:18.639
Most of your state lives in your back end.
00:11:18.720 --> 00:11:26.159
When you do validation, like if you're doing client-side validation and then you send it to the server and you don't trust it anyway, and then you have another set of validation here, you're just doubling your work.
00:11:26.320 --> 00:11:28.720
You're not really getting anywhere if it's fast enough to do.
00:11:28.960 --> 00:11:31.200
So my thing is state needs to live where it lives.
00:11:31.279 --> 00:11:42.080
So there's things where if someone has a mouse movement, that should be tied to a signal, because then you can drive other things on the page that are instantaneously that the mouse control is owned by the client, right?
00:11:42.399 --> 00:11:47.360
But the click, like the logic of what is allowed and not allowed, belongs on the server.
00:11:47.519 --> 00:11:51.519
So people tend to put state in the wrong place, and that's why you see tons of JSON getting sent down.
00:11:51.600 --> 00:11:54.320
You see all this polling, you see all this stuff, is because they're putting state in the wrong place.
00:11:54.399 --> 00:12:00.399
So they're having to recreate the entire world of state in the client, and that is just
a recipe for disaster.
00:12:00.559 --> 00:12:02.799
One of the beautiful things about the web is hypermedia.
00:12:02.879 --> 00:12:09.600
And the idea of hypermedia is you show what you display declaratively what you want the person to see and what they're allowed to do next.
00:12:10.000 --> 00:12:10.559
That's it.
00:12:10.720 --> 00:12:19.039
They don't have any logic on a H like in pure HTML, there is no logic saying why this is a bank transfer, why this is paying your taxes.
00:12:19.200 --> 00:12:20.240
There's no logic of that.
00:12:20.320 --> 00:12:23.200
There's just here's the view, and here's what you can do next.
00:12:23.440 --> 00:12:23.679
Yeah.
00:12:23.840 --> 00:12:28.799
Once you really embrace that, things get so much simpler because most of the state lives where it's supposed to live.
00:12:28.879 --> 00:12:29.200
That's it.
00:12:29.519 --> 00:12:30.639
It's a pretty simple concept.
00:12:30.799 --> 00:12:32.240
We're not doing anything magical.
00:12:32.320 --> 00:12:33.360
That's why we're so small.
00:12:33.679 --> 00:12:33.919
Right.
00:12:34.000 --> 00:12:41.919
So, I mean, it sounds like a simple concept, but it's not always been it's simple in theory, not always simple in practice.
00:12:42.240 --> 00:12:44.480
Maybe it is if you're using Datastar.
00:12:44.799 --> 00:12:44.960
Yeah.
00:12:45.039 --> 00:12:48.399
Well, and the thing is that there's a clear delineation of why this happened.
00:12:48.639 --> 00:12:50.320
We had Ajax back in the day.
00:12:50.480 --> 00:12:59.200
Like the thing that happened is basically server tech at the time, like if you look at Apache, it was basically creating a new thread or Glassfish or any of these.
00:12:59.279 --> 00:13:01.440
You were basically creating a new thread for every request.
00:13:01.679 --> 00:13:04.399
Well, that doesn't scale to thousands of people and it didn't work.
00:13:04.480 --> 00:13:07.440
Like it worked fine when you had one or two core machines, right?
00:13:07.519 --> 00:13:13.840
Like this idea was okay because you're gonna do sharing anyway, but it doesn't match the web of today.
00:13:14.000 --> 00:13:19.279
So the problem is that spas were trying to say we want more interactivity on the browser.
00:13:19.519 --> 00:13:20.720
We need to make Google Maps.
00:13:20.799 --> 00:13:25.759
We can't do all that logic on the server because the per thread thing doesn't work when you scale up.
00:13:26.080 --> 00:13:27.519
All that's been solved since then.
00:13:27.679 --> 00:13:32.559
So the mental model that people have of why spas exist was to solve a problem that's already been solved.
00:13:32.799 --> 00:13:38.960
So they made this complicated thing, and it's basically a boiling frog thing of it just got worse and got worse and got worse and got worse.
00:13:39.200 --> 00:13:44.960
And no one kind of sat back, me included, to be clear, Datastar could have existed more than a decade ago.
00:13:45.120 --> 00:13:54.879
There's literally no reason why it
didn't exist 10 years ago, other than everyone just was kind of being the frog and going, well, this is just I guess Vercel is now like one more NPM module, and we got this.
00:13:55.039 --> 00:13:56.559
It just got worse and worse.
00:13:56.720 --> 00:13:57.919
And I'm part of that problem.
00:13:58.080 --> 00:13:59.200
So, like, go fix it.
00:13:59.279 --> 00:14:00.000
So we fixed it.
00:14:00.399 --> 00:14:00.720
Sure.
00:14:00.879 --> 00:14:01.440
Sure.
00:14:01.840 --> 00:14:04.559
The one big difference, I think.
00:14:04.720 --> 00:14:09.200
So being a Ruby on Rails developer, I'm using Hotwire a lot.
00:14:09.360 --> 00:14:18.799
One of the ways that we do the real-time updating or the I click this button and everyone else sees the result of that button click is via WebSockets.
00:14:18.960 --> 00:14:28.000
But in Datastar, you guys are using SSE, which is server send events, yes, which is not a new protocol, but it was very new to me.
00:14:28.159 --> 00:14:29.919
I've been doing this for a while now.
00:14:30.080 --> 00:14:33.120
Why is that like I'm just learning about this protocol?
00:14:33.279 --> 00:14:33.600
Uh, yeah.
00:14:33.840 --> 00:14:35.120
It's been around for a hot minute.
00:14:35.360 --> 00:14:37.120
I fell into this trap too for years.
00:14:37.279 --> 00:14:47.039
So I was doing a bunch of military stuff where I was sending direct GPU information about radar sites and doing millions of blips per second kind of stuff, like really low-level stuff.
00:14:47.279 --> 00:14:52.879
And the thing that I thought was like WebSockets is the future of WebSockets solves all problems because I just get my socket.
00:14:53.039 --> 00:14:53.840
I can do whatever I want.
00:14:53.919 --> 00:14:55.840
You basically get the equivalent of a TCP socket.
00:14:56.000 --> 00:14:57.519
Once it does the handshake, you get it.
00:14:57.679 --> 00:14:58.960
Now I can do anything I want.
00:14:59.200 --> 00:15:01.679
The greatest part about WebSockets is you can do anything you want.
00:15:01.840 --> 00:15:04.000
The bad part is you can do whatever you want.
00:15:04.159 --> 00:15:10.720
And the reason why that's bad is all of a sudden you can't do cookies because once you upgrade, you can't change out cookies.
00:15:10.960 --> 00:15:12.960
You now have to write your own compression stuff.
00:15:13.120 --> 00:15:14.960
And then when you write a compression, guess what?
00:15:15.039 --> 00:15:16.159
You're doing it in JavaScript.
00:15:16.240 --> 00:15:18.559
You don't have access to the actual C stuff.
00:15:18.799 --> 00:15:20.480
It's basically its own island.
00:15:20.639 --> 00:15:23.279
And now you have your own equivalent of cords to deal with.
00:15:23.360 --> 00:15:25.360
Like you have all these things, sticky sessions.
00:15:25.519 --> 00:15:28.879
When you break off, you have to do auto try to reestablish.
00:15:29.200 --> 00:15:31.279
And so what if the server switches and all this?
00:15:31.519 --> 00:15:35.759
Like you're basically
eschewing the entire HTTP stack once you get that upgrade handle.
00:15:35.919 --> 00:15:37.759
Like once you get a socket, you're on your own.
00:15:38.320 --> 00:15:42.720
What data store does is people think SSE is a new protocol.
00:15:42.879 --> 00:15:43.440
It's not.
00:15:43.600 --> 00:15:46.000
It is literally just a different response type.
00:15:46.159 --> 00:15:50.879
So instead of text slash HTML, you're saying text slash event dash stream.
00:15:51.039 --> 00:15:55.120
And then what happens is there's this like data colon and then your data.
00:15:55.279 --> 00:16:00.399
There's a couple of extra things, and you do two new lines, and that just basically means flush to the end.
00:16:00.480 --> 00:16:01.840
So it's just a text format.
00:16:02.000 --> 00:16:02.720
That's all it is.
00:16:02.879 --> 00:16:03.120
Yeah.
00:16:03.279 --> 00:16:04.799
So here's the things that are really neat about that.
00:16:04.960 --> 00:16:06.799
First of all, it's a normal fetch.
00:16:06.960 --> 00:16:08.159
There's nothing special about it.
00:16:08.240 --> 00:16:10.000
So you just get normal fetch semantics.
00:16:10.159 --> 00:16:13.360
That means all your proxies, all your stuff, it's just normal web traffic.
00:16:13.440 --> 00:16:14.559
There's nothing special about it.
00:16:14.639 --> 00:16:16.320
There's no kind of weird reverse proxies.
00:16:16.399 --> 00:16:17.440
You have to do nothing of it.
00:16:17.600 --> 00:16:18.639
It does not exist.
00:16:19.039 --> 00:16:22.799
The other thing is has built into it the idea of auto-reconnect.
00:16:22.879 --> 00:16:27.200
So if you get lost, you can actually say, I want to reconnect, and this was the last message I did see.
00:16:27.360 --> 00:16:29.600
So that can is just built natively into it.
00:16:29.759 --> 00:16:35.440
The other thing that's interesting is that the one thing I thought was really dumb at first was like, oh, this is just for text.
00:16:35.600 --> 00:16:37.039
That's not really that useful.
00:16:37.519 --> 00:16:45.200
But one thing that's come around in the last 15 years is that you have streaming compression libraries are now native to the browser.
00:16:45.360 --> 00:16:59.039
Like Brottly and Z standard, not only do they compress per message, but they actually compress in a stream, which means if you start doing a table and you get table like TR, TD, TD, TD, TD, that all becomes like single bits on the wire.
00:16:59.200 --> 00:17:06.960
So the irony is that the text format, because they already know about all the stuff in the dictionaries and stuff, like they actually become smaller than sending the binary version.
00:17:07.200 --> 00:17:15.519
So you have this text format that's dead simple to write that compresses to tiny amounts, and it also is just normal HTTP.
00:17:15.680 --> 00:17:30.240
So you get all the benefits of just a regular web thing, but you also can send anything down, which means we can send down signals and we can send down new patches of elements and we can morph them in very similar to how Hotwire does it, but we actually work with the Hotwire team to make that faster better.
00:17:30.319 --> 00:17:35.039
So ironically, if you're using Ideomorph from Hotwire, Micah is the guy behind that.
00:17:35.200 --> 00:17:37.119
We have the fastest version of that as well.
00:17:37.279 --> 00:17:40.400
So ours is faster than the one that you see in Hotwire by quite a bit.
00:17:40.720 --> 00:17:46.400
Yeah, that's a fairly new addition to Hotwire and Turbo that I think it was Turbo 8.
00:17:46.640 --> 00:17:46.880
Yeah.
00:17:46.960 --> 00:17:49.839
Well, then here's the problem if you're coming from a Hotwire perspective.
00:17:49.920 --> 00:17:56.319
There is the like the standard WebSocket morph stuff that's now doing redirects and links, and now you're having to go and pull again.
00:17:56.400 --> 00:17:59.200
So you're doing this request reply, request reply for every message.
00:17:59.359 --> 00:18:01.359
That basically you do the redirect stuff, right?
00:18:01.519 --> 00:18:04.559
You do the 304s, is how you morph in new stuff.
00:18:04.880 --> 00:18:16.480
But the data star way, you only send data when the server wants to you basically keep that connection open once you start, which means you've now just half your RTG time and you can make responses that are independent of requests.
00:18:16.720 --> 00:18:21.920
So by default, data star is actually completely collaborative by its very nature.
00:18:22.160 --> 00:18:36.000
If you want to go, I don't know, because it's mostly audio for you, we can go and play a game of a billion checkboxes, have exactly the same state, real time live, and play like a game, and there's no extra code.
00:18:36.079 --> 00:18:39.039
It's like a few hundred lines of code to build the entire thing.
00:18:39.119 --> 00:18:47.119
So data star by its very nature is collaborative first, whereas the problem with stuff obviously in a hard wire is that you have this all this basically request reply and relinking stuff.
00:18:47.200 --> 00:18:52.480
You have the frame stuff, you have the streams, you have this kind of HX boost style thing by default.
00:18:52.640 --> 00:18:56.319
Like there's all these things, and it's not all of it's not using fibers and the async stuff.
00:18:56.559 --> 00:19:07.599
Whereas the data star way is basically async and fibers first, and it's simpler because there's not a you use streams for this situation, but then you use the 304, the link stuff for this morph strategy.
00:19:07.680 --> 00:19:10.559
No, it's all dysmorph all the time, all over streams.
00:19:11.039 --> 00:19:17.119
In some ways, it's simpler because we just built for the hardcore case first, and then everything else is simple from there.
00:19:17.359 --> 00:19:17.839
Right.
00:19:18.079 --> 00:19:25.680
I think the hardest pitch for Data Star to Ruby on Rails developers is not even just datastar is better than Hotwire.
00:19:25.839 --> 00:19:41.839
Hotwire is what Rails
ship with, and anyone who's been doing Rails for a reasonable amount of time and has had to maintain a Rails application knows the closer you stick to what Rails gives you out of the box, the easier your upgrade experience is.
00:19:42.720 --> 00:19:45.599
So what's the plan for that?
00:19:45.920 --> 00:19:53.359
So my idea is datastar itself, the core concept, like unless the web browser actively changes what's supported, datastar is done.
00:19:53.519 --> 00:19:53.839
It's done.
00:19:54.240 --> 00:20:01.599
So your upgrade path is you can upgrade to whatever you want because you won't be subject to all the turbo and stimulus changes that are happening.
00:20:01.839 --> 00:20:04.720
You just you're just opting out of that, like you just don't need that anymore.
00:20:04.960 --> 00:20:09.039
That is part of Rails that you don't have to be beholden to.
00:20:09.440 --> 00:20:17.680
You're not waiting until someone makes a change there because it's an unnecessary thing, because not only is it bigger, it's slower, and it doesn't do as much.
00:20:17.839 --> 00:20:26.400
So the irony is that, for example, Datastar is smaller than HTMX or Alpine, and it does everything that both of us do combined.
00:20:26.640 --> 00:20:29.839
So it's one of those things of like, there's a reason why we're so much smaller.
00:20:30.000 --> 00:20:34.880
It's not a like, yes, it's kind of nice to boast that like, hey, we're small and we're you know we're faster and all that.
00:20:34.960 --> 00:20:38.480
But the idea is that it's so simple that there's not that much to change.
00:20:38.559 --> 00:20:41.039
There's not these great upgrade paths, it's done.
00:20:41.279 --> 00:20:46.720
And also, one thing to be clear is that data star internally is built on a plugin system like a game ECS.
00:20:46.960 --> 00:20:54.559
So if we completely foobard something in there, you could literally pop that out and put something else in, and nothing about data star changes.
00:20:54.640 --> 00:20:56.880
It's all built on plugins, the entire stack is.
00:20:57.039 --> 00:21:01.599
So we can be wrong, and you don't have to change anything about your code because it's all declarative.
00:21:01.759 --> 00:21:11.440
Like, for example, when you do SQLite, when you say create index or like query plan, you're not having to think about all the B tree underneath or like how they're doing their thing.
00:21:11.519 --> 00:21:14.000
You're just saying create me an index in the best way that you know possible.
00:21:14.079 --> 00:21:15.279
Like it's all declarative, right?
00:21:15.680 --> 00:21:21.279
Datastar is much more declarative in its nature, so that if we make huge updates, your code doesn't change.
00:21:21.599 --> 00:21:22.240
Right, right.
00:21:22.400 --> 00:21:27.599
So if anything, it's much, much simpler and it's actually better than the hotwire path.
00:21:27.680 --> 00:21:34.480
Like, I really do think if DHH looked at really gave Datastar a try, he would agree that it's better
than Hotwire.
00:21:34.720 --> 00:21:38.720
Hotwire came out of a necessity at the time that does not exist anymore.
00:21:39.839 --> 00:21:40.160
Okay.
00:21:41.039 --> 00:21:54.000
I would love to see him actually try it because like it would be an interesting conversation because I really do think it solves the core ideals of Ruby of being simple and elegant and all the things that are intended by the language.
00:21:54.480 --> 00:21:56.480
It does that to a deep degree.
00:21:56.880 --> 00:21:57.039
Right.
00:21:57.279 --> 00:21:59.279
It just happens to be in JavaScript, unfortunately.
00:21:59.519 --> 00:21:59.759
Yeah.
00:22:00.319 --> 00:22:10.799
Such as let well, I mean Turbo is in JavaScript, stimulus is in JavaScript because we have we have helpers that allow us to not feel like it's in JavaScript.
00:22:11.279 --> 00:22:16.319
The SDK that you guys have for Ruby for Datastar is pretty basic.
00:22:16.559 --> 00:22:21.759
You're not getting the same kind of helpers you get out of all the Rails helpers with Turbo.
00:22:21.839 --> 00:22:39.759
You get a bunch of helpers out of the box, ways of writing it on the server side that doesn't feel like you're writing anything other than your standard Rails and Ruby, which almost made it feel like the idea was okay, fine, Rails has hot wire, but Hanami doesn't, or Sinatra doesn't.
00:22:39.839 --> 00:22:44.400
They can, because Hotwire is also a back-end agnostic deal.
00:22:44.880 --> 00:23:05.599
But was that intentional where it was like, okay, we'll keep this SDK super simple that way if you're doing Sinatra or Hanami or whatever the new next Ruby framework is, you're just good to go and we'll let you figure out the integration stuff, or is there a plan for, yeah, we'll do the Rails stuff, and then maybe if Hanami gets big enough, we'll do the Hanami stuff?
00:23:05.759 --> 00:23:06.960
Yeah, no, it's a good question.
00:23:07.039 --> 00:23:12.000
So the one thing that's interesting, we have SDKs for about 14 or 15 languages at this point.
00:23:12.160 --> 00:23:13.680
Yeah, there's a there's a lot.
00:23:13.920 --> 00:23:17.759
Well, the reason why is because I don't know if you know, but the SDK is basically three functions.
00:23:17.839 --> 00:23:18.880
You implement these three functions.
00:23:19.920 --> 00:23:20.559
And you're done.
00:23:20.720 --> 00:23:26.880
There's guidance, and the thing is it's that doesn't sound like a lot, but at the same time, it's guiding you in a way of setting up compression correctly, doing all the right things.
00:23:26.960 --> 00:23:31.680
Like there's an ADR, those three functions have a big old ADR to say here's why and what you're doing.
00:23:31.920 --> 00:23:36.480
But the thing is that, like, for example, in Go, everything's built around a standard lib.
00:23:36.559 --> 00:23:38.000
Like there's an HTT server and all that.
00:23:38.079 --> 00:23:48.480
There's any language that has this stuff, but for the TypeScript community, we have the TypeScript SDK, but we also have people that have done ones for Hano or for Express, those kinds of things.
00:23:48.559 --> 00:23:53.920
So it's not just a back-end agnostic framework, it's backend and framework agnostic.
00:23:54.079 --> 00:23:57.440
So the thing is that our Ruby community isn't that big right now.
00:23:57.599 --> 00:24:00.400
The only reason why is because it's not built in.
00:24:00.559 --> 00:24:13.920
But I do think as people use it as rail authors, one thing, a curse and a blessing of Ruby is that you can monkey patch to your heart's content, which means if you want those helpers, you're a couple lines away from saying, hey, I'm gonna build an SDK on top of this.
00:24:14.000 --> 00:24:19.759
Like you can build the monkey patching that you want to see on the objects on your controllers as you choose.
00:24:19.920 --> 00:24:37.680
We just haven't seen that in the closure space, there's a proliferation of different people doing different and in Python, those two languages have so much expressiveness in their languages that we've seen a huge uptake in the different kinds of projects built on top of Data Star as more of a framework on top of it.
00:24:37.920 --> 00:24:42.079
And I see that Ruby would be the exact same, you just got to get someone in there.
00:24:42.160 --> 00:24:53.359
Because I think for me, a Sinatra style thing with helpers seems like the right would be kind of more in line with the data ethos than the entire Rails, do everything, embrace the magic kind of thing.
00:24:53.519 --> 00:24:57.039
So, but there's nothing about data star itself that's it's completely agnostic to that.
00:24:57.200 --> 00:25:00.160
So I would like to see that's one of the reasons for like coming and talking to you.
00:25:00.480 --> 00:25:04.400
Like, there's literally no reason why the Ruby community for Datastar isn't bigger than it is.
00:25:04.559 --> 00:25:04.720
Right.
00:25:05.039 --> 00:25:08.559
There's no technical reason, it's a social problem, not a technical one.
00:26:29.790 --> 00:26:38.029
Datastar is a really is surprising that DHH hasn't played around with it because he's all about that conceptual compression.
00:26:38.350 --> 00:26:40.509
He says it all the freaking time.
00:26:40.830 --> 00:26:45.310
It is a manifestation of that, even if we disagree on specific details, sure.
00:26:45.550 --> 00:26:48.509
In fact, if anything, I would love for him to see it and tell me why it's wrong.
00:26:48.670 --> 00:26:52.670
Because that would actually be more insightful.
00:26:52.830 --> 00:26:57.070
Like, for example, when you talked about the TypeScript stuff, I will say that this is actually kind of funny.
00:26:57.150 --> 00:27:02.029
Like when the data star stuff first dropped like three years ago, it was like, here's all the features, here's all the things.
00:27:02.190 --> 00:27:03.390
DH would hate it.
00:27:03.470 --> 00:27:06.750
Because it was right when you're saying TypeScript is completely useless,
TypeScript's bad.
00:27:06.910 --> 00:27:09.870
That was on the cons and on the pros, is that DHH would hate it.
00:27:10.110 --> 00:27:17.150
So it was the plus and minus of like, but the thing is what he was saying, he clarified later that TypeScript doesn't show any value for us, right?
00:27:17.230 --> 00:27:18.509
It's too complicated for us.
00:27:18.590 --> 00:27:19.310
And I get that.
00:27:19.390 --> 00:27:23.070
So it'd be interesting to see what he sees in what Datastar is.
00:27:23.230 --> 00:27:26.269
Tell me why this isn't the best thing to happen to the web in a long time.
00:27:26.350 --> 00:27:34.029
Because I know it sounds like I'm hyping it, but it's just like now that it's done, I don't want to go on podcasts, I don't want to do a bunch of talks and stuff about it.
00:27:34.110 --> 00:27:35.230
I just want to get back to what I'm doing.
00:27:35.310 --> 00:27:37.710
Hopefully, someone else kind of takes that mantle going forward.
00:27:37.870 --> 00:27:39.870
Uh, like I know we talked about doing this for a while.
00:27:39.950 --> 00:27:45.470
So, like, this is talk season right now, and I'm not doing a talk on it anywhere because it's like figure it out for yourself.
00:27:45.550 --> 00:27:47.310
It's already the fastest, best thing.
00:27:47.390 --> 00:27:48.990
So if you're interested, great.
00:27:49.070 --> 00:27:50.350
If not, okay, cool.
00:27:50.509 --> 00:27:52.350
I'll go back to doing normal stuff.
00:27:52.830 --> 00:27:58.430
Something that generally comes along with that conceptual compression, though, is mental model shift.
00:27:58.750 --> 00:28:09.470
Where you're used to doing it this way, but if you just change your mental model a little bit, everything gets simpler because you're now able to function within side of this conceptual compression.
00:28:09.630 --> 00:28:13.390
Like, what does that look like for datastar?
00:28:13.630 --> 00:28:21.950
What are the big areas where it's like, this is probably how you're used to doing it, whether it's traditional HTTP stuff or it's spa stuff.
00:28:22.110 --> 00:28:22.590
Yeah.
00:28:22.910 --> 00:28:28.190
You might have to tweak your approach to get the best value by doing X, Y, or Z.
00:28:28.509 --> 00:28:29.150
That's a great question.
00:28:29.310 --> 00:28:36.509
So we actually have on the website, because we kept running into this issue, we actually have the Tau of Datastar, which actually goes through what we think are the best ways.
00:28:36.670 --> 00:28:44.670
There's nothing about Datastar that says you have to build this way, but if you do, your world gets better, is the CQRS style, like command query responsibility segregation.
00:28:44.830 --> 00:29:01.230
And the idea of that is that when you're building things in Datastar, normally with most things, you'll do a request, it'll get a change, like a morph kind of thing, and then send it back as the way people, even if you're doing hotwire or if you're in spas, you send a request, you get back JSON,
and then you turn it into the dev.
00:29:01.630 --> 00:29:12.269
So the Datastar mental model for people that really hit things hard is your commands are your intent of like you clicked a button, you did a thing, you said, hey, this person moved a mouse.
00:29:12.350 --> 00:29:15.870
I'm gonna send a command to the back end saying, I would like to make this change.
00:29:16.029 --> 00:29:21.310
Not I made this change, it's basically saying, here's a stream of different things that I'm trying to affect the page in.
00:29:21.470 --> 00:29:23.150
And then that is completely separate.
00:29:23.230 --> 00:29:31.630
So you're doing that in your back end, you're handling that request, and then instead of sending a response, you send basically a 200 saying, yep, got it, it's good.
00:29:31.870 --> 00:29:38.590
And then on a separate event bus type thing, you basically let other people know that this is a change that happened.
00:29:38.750 --> 00:29:45.390
And then on another channel, you basically say, when you start up that page, you basically say, Hey, give me updates for this page that I'm looking at.
00:29:45.630 --> 00:29:47.230
And so that's an open connection.
00:29:47.310 --> 00:29:51.950
And then whenever something gets affected, you send down basically a revised version of the view.
00:29:52.110 --> 00:29:52.350
Yeah.
00:29:52.509 --> 00:29:59.070
So by separating those things out, what happens magically out of that is that all of a sudden, like let's say you're doing a to-do, right?
00:29:59.150 --> 00:30:01.150
And you're adding and removing stuff from a to-do.
00:30:01.550 --> 00:30:07.070
You're sending those commands off, it's updating, seeing if it's valid, all that stuff, and then it's updating a key value store.
00:30:07.150 --> 00:30:11.470
Well, some other person could be listening to that key value store and then basically updating.
00:30:11.710 --> 00:30:21.950
Now it doesn't matter if you change it from one page or someone else changed it, or it came from a back-end process, everyone's looking at that same view at the same time and get the exact same state.
00:30:22.029 --> 00:30:24.350
So you cannot get out of sync with each other.
00:30:24.670 --> 00:30:31.790
And now all of a sudden, you can do stuff like there's an example that we use all the time of like a game of life that's played in real time.
00:30:31.870 --> 00:30:32.830
Uh, you probably saw it, right?
00:30:32.910 --> 00:30:33.790
Like, yeah, yeah, yeah.
00:30:33.950 --> 00:30:35.470
So it's a real-time game.
00:30:35.630 --> 00:30:37.150
To be clear, that's a rendering demo.
00:30:37.230 --> 00:30:46.430
So it's actually sending 2,500 individual divs every single frame, and it's updating that live, and it can work on a 3G phone.
00:30:46.590 --> 00:30:47.790
So it's fast.
00:30:48.029 --> 00:30:48.990
Yeah, and that's the thing.
00:30:49.310 --> 00:30:50.430
It's actually not that fast.
00:30:50.590 --> 00:30:54.269
It's a rendering demo showing how even if you do things wrong, it still is fast.
00:30:54.590 --> 00:30:55.710
Well, it feels fast.
00:30:56.029 --> 00:30:56.910
That's kind of the point, right?
00:30:56.990 --> 00:30:58.350
Is that we can do some crazy things.
00:30:58.430 --> 00:31:05.470
So the other thing that's interesting is that data star is built as a progressive performance, not progressive enhancement, but progressive informance.
00:31:05.550 --> 00:31:09.710
So, what I mean by that is that normally people can just send down the entire page.
00:31:09.790 --> 00:31:13.790
They just you send the whole page because of the compression, it's actually like just the diffs between it.
00:31:13.870 --> 00:31:16.350
So you send your big fat morphs down.
00:31:16.830 --> 00:31:26.910
But you can, if you all of a sudden got into an issue, you can basically only target one part of the page and just update that because everything technically is out of bounds all the time, kind of like the HX boosts a little bit.
00:31:27.390 --> 00:31:34.269
It means that you can target select stuff, but most of the time you have a mental model of just sitting down, here's the state I want the thing to be in.
00:31:34.430 --> 00:31:39.150
So the irony is I built it to be the super performant thing that you only target certain things, blah, blah, blah.
00:31:39.230 --> 00:31:42.590
But we found that it's so fast that you could just send the whole page down.
00:31:42.670 --> 00:31:50.350
So ironically, it feels a lot like JSX in that you know how you just are declaring what you want the page to look like and it does all the V DOM stuff.
00:31:50.590 --> 00:31:53.550
Well, our V DOM is like broadly compression.
00:31:53.790 --> 00:31:56.110
So we don't have to logically think about any of this stuff.
00:31:56.190 --> 00:31:59.390
You just send down the page as you want it, and you get the thing.
00:31:59.470 --> 00:32:02.990
So that's a weird mental shift for people because they're so used to like you can't do that.
00:32:03.070 --> 00:32:08.029
You can't send down a whole new page, but we have things of like the game of life, the 2500 divs.
00:32:08.190 --> 00:32:14.430
We have now have production apps that are now doing the equivalent of full Excel, like the equivalent of Excel in the browser.
00:32:58.710 --> 00:33:03.350
We have companies that are doing that, and it's faster by orders of magnitude than the spaway.
00:33:03.510 --> 00:33:10.390
Because people said, Oh, this is great for back-end processes, but it can't work for a map or for Excel spreadsheets.
00:33:10.630 --> 00:33:20.710
Well, what our one of our biggest success stories is literally a spreadsheet app, and then like on our website now, we have an open map 3D view as one of our examples that we just throw in.
00:33:20.790 --> 00:33:26.390
Because we are the fastest version of client-side state, but the whole point is you should have very little of that.
00:33:26.630 --> 00:33:31.030
So that's kind of the thing is that we are just the fastest way to
do this stuff.
00:33:31.110 --> 00:33:33.110
And the irony is that it's less code.
00:33:33.270 --> 00:33:38.230
I don't know Ruby enough to make this guarantee, but I can make this guarantee in almost every other language that I do know.
00:33:38.470 --> 00:33:44.070
If you tried your hotwire and stimulus stuff and you tried it in Datastar, it is gonna be less code and it's gonna be faster.
00:33:44.230 --> 00:33:47.190
I have yet to been proven wrong in any language so far.
00:33:47.510 --> 00:33:48.390
I'd believe it.
00:33:48.550 --> 00:33:48.790
Yeah.
00:33:49.030 --> 00:33:59.670
Just going through the guides, just seeing some of the examples, not actually writing the code though, but like I definitely could see it being less code.
00:33:59.910 --> 00:34:00.470
Yeah.
00:34:00.790 --> 00:34:07.430
Whether it's going to click the same way that like maybe Hotwire does because Hotwire is built in is a TBD.
00:34:07.590 --> 00:34:11.829
Once I play with it more, I'll be able to speak better to that.
00:34:11.990 --> 00:34:18.950
But it does seem like damn, instead of having to write a whole stimulus controller, like I'm inlining a lot of this stuff.
00:34:19.110 --> 00:34:19.590
Yep.
00:34:19.909 --> 00:34:24.230
Well, we have a different vibe than like we have a Discord server that's very active.
00:34:24.309 --> 00:34:35.510
And the irony is that we have, I think, around 4400 stars on GitHub, but we have 2200 people on our Discord, which means I don't care how many people use Datastar, but my thing is that ratio is crazy.
00:34:35.670 --> 00:34:40.309
Yeah, people that are starring one click are now also in the Discord.
00:34:40.470 --> 00:34:47.829
So the thing is that you have a community where like Hotwire, I will tell you, I tried to get hotwire running in Go, and it's an utter nightmare.
00:34:47.990 --> 00:34:49.269
Like it does not work very well.
00:34:49.510 --> 00:34:53.990
I didn't want to go off and build all this stuff, but you know, I ended up doing it because Hotwire did not work in Go.
00:34:54.470 --> 00:34:56.710
It is built for Ruby, in especially Rails.
00:34:56.789 --> 00:34:58.150
It's built in this ecosystem.
00:34:58.309 --> 00:35:02.630
The way Datastar is built, everyone in every language can talk to each other.
00:35:02.950 --> 00:35:15.190
Like you're talking about compression, but the idea that I can have a conversation in Zig that is able to talk to a Rubyist about like what's the best way to define these helper functions and all that, there's something magical about that.
00:35:15.349 --> 00:35:32.869
That you grow as a community by being able to see the beauty in each language, as opposed to right now where everyone's living these little tribes of like your Hotwire people do not talk to other people outside their domain because it's just so much tribal knowledge learned.
00:35:32.950 --> 00:35:35.670
Whereas the Datastar Way is just using what's already in the browser.
00:35:35.829 --> 00:35:38.630
So if anything, everyone learns to use the browser better.
00:35:38.950 --> 00:35:57.670
Yeah, Hotwire definitely was supposed to be or has the capability of being like back-end agnostic, but obviously being bundled in Rails gives Rubyists a big advantage over it because all of the helpers, it's just so easy to get running on Rails.
00:35:58.630 --> 00:36:01.750
Luckily, it does work in others.
00:36:01.990 --> 00:36:11.269
I haven't met anyone who tried it in Go, but I've met plenty of Python people who have tried it in their various frameworks and are using it to success.
00:36:11.829 --> 00:36:14.949
But yes, datastar is so much simpler.
00:36:15.190 --> 00:36:17.349
It really is crazy simple.
00:36:17.989 --> 00:36:20.949
My thing is in the Go SDK, there's a bunch of helpers built in.
00:36:21.029 --> 00:36:25.190
Like there's speculation rules where it automatically like dumps speculation rules into your page for you.
00:36:25.349 --> 00:36:32.230
It does some nice redirects, it executes scripts, it does all the like there's things in the Go one even that are helpers that aren't in the Ruby one.
00:36:32.389 --> 00:36:38.070
But again, you have to get Ruby us in there to really like starting to fight it out on like what they want to see.
00:36:38.230 --> 00:36:44.550
And that's the thing is that one thing I do see at the Ruby community is people that are just like, hey, I just want to get my stuff done.
00:36:44.789 --> 00:36:46.630
It's not like Linux distro hopping.
00:36:46.710 --> 00:36:49.429
You're like, yeah, this is good enough for me, it's good enough for what I'm doing.
00:36:49.590 --> 00:36:52.150
If it wasn't, I wouldn't be using Ruby and Rails, right?
00:36:52.309 --> 00:37:07.909
Like if I need something more hardcore, so it's almost pragmatic to a fault in that they're not seeing there's no reason to upgrade, but as soon as you try, I like that's the thing is I want to have a conversation now that you're kind of interested in it, have a conversation after you've actually built something with it.
00:37:08.150 --> 00:37:10.949
I'm not good at selling it because I'm like, if you don't want it, then don't use it.
00:37:11.029 --> 00:37:22.070
But like it's so much it's weird to me that now look back at if I go to like the web dev on Reddit and I see the things that people are complaining about, it all seems like this crazy, weird.
00:37:22.309 --> 00:37:27.110
Like, we are kind of the small little cult that looks at the outside world going, y'all are crazy.
00:37:27.429 --> 00:37:28.469
What is going on here?
00:37:29.110 --> 00:37:36.710
It seems so ridiculous how many hoops people jump through just to not use the web as it's intended.
00:37:36.949 --> 00:37:39.590
So this is the thing that's really hard for people.
00:37:39.909 --> 00:37:53.750
Like you're talking about the thing that feels different about Datastar, and it's embracing the fact that your job as a web developer is to get strings to the browser as fast as possible.
00:37:54.230 --> 00:38:00.230
You are the fastest thing you can do in the thank you for oversimplifying my job, but yes, you're a hundred percent correct.
00:38:00.469 --> 00:38:05.909
The sooner you get it into a string format that you can hand to the C and C side, the faster it is.
00:38:06.070 --> 00:38:07.269
Because it still has to do that work.
00:38:07.429 --> 00:38:14.710
If you send VDOM or JSON and it still has to do the work of turning into a string that gets parsed, that's still what has to happen.
00:38:14.869 --> 00:38:20.309
So by realizing that what's my job is to pass butter, like your job is to pass strings.
00:38:20.550 --> 00:38:21.509
That is your job.
00:38:21.670 --> 00:38:26.150
And as soon as people embrace that, a lot of the things that you see people do seems crazy.
00:38:26.309 --> 00:38:35.909
Because what they're doing is they're basically rebuilding the entire back end state in local state and keeping this weird cache of like what state is, and then still turning into strings.
00:38:36.070 --> 00:38:42.630
It's like someone having a VM to then try to write a bytecode in to not deal with their VM.
00:38:43.349 --> 00:38:45.029
It's turtles all the way down.
00:38:45.110 --> 00:38:49.349
It's like, but we already have DOM parser is built into the thing.
00:38:49.429 --> 00:38:51.190
As soon as you hand it, you get back a DOM object.
00:38:51.269 --> 00:38:54.230
That's the it can handle millions of DOM nodes a second.
00:38:54.389 --> 00:38:54.630
Yeah.
00:38:55.029 --> 00:38:58.389
Why not just send strings to the browser and let it do its job?
00:38:59.029 --> 00:39:00.389
Your job is to send strings.
00:39:00.630 --> 00:39:02.070
People do not like that fact.
00:39:02.309 --> 00:39:03.670
I don't know, it's weird.
00:39:03.829 --> 00:39:04.309
Yeah.
00:39:04.710 --> 00:39:17.590
The one thing that I'm very interested when I start trying, when I start playing with it in earnest, is gonna be I really like stimulus for the convention of like, this is how I organize my JavaScript.
00:39:17.670 --> 00:39:25.349
I have to write some JavaScript, not a lot, it's sprinkles, but I can write a little bit of JavaScript and I can attach it to whatever element I want.
00:39:25.670 --> 00:39:28.630
And there's a basically like a convention to do it.
00:39:28.710 --> 00:39:30.789
I don't have to think too much about it.
00:39:31.110 --> 00:39:34.070
But Datastar doesn't seem to really have that.
00:39:34.309 --> 00:39:37.670
It has all of the attributes, you can do everything in those attributes.
00:39:37.989 --> 00:39:43.269
It almost feels a little like I'm teetering on the edge of going back into jQuery soup.
00:39:43.590 --> 00:39:45.269
I understand exactly what you're thinking.
00:39:45.429 --> 00:39:50.710
The weird thing is like jQuery was so right and yet so it was right for the wrong reasons.
00:39:51.029 --> 00:39:58.070
It was these sprinklings of things, but the problem is it at the time the backing couldn't do enough
stuff.
00:39:58.230 --> 00:40:13.029
So I will say I will highly, highly, highly recommend going through the guide, going through the stuff, then coming onto the Discord and going in the data-Ruby channel and show us a production issue you're actually running into.
00:40:13.190 --> 00:40:16.469
Because most of the time when people I know exactly the feeling you're feeling, I get it.
00:40:16.630 --> 00:40:17.429
Like we get it all the time.
00:40:17.509 --> 00:40:19.590
And the thing is, you're like, it can't be this simple.
00:40:19.750 --> 00:40:24.389
There's a super complex thing, you're dumbing it down because you want to like hype your framework.
00:40:24.469 --> 00:40:25.029
I get it.
00:40:25.269 --> 00:40:49.190
It sounds like I'm telling you show us a production issue that's actually an issue, and we'll and it you all of a sudden you'll start deleting code and going, Oh, because the thing is once you get the cycle to the server where it's not like request reply, request reply, but it's just sending commands, acting and having a separate stream for doing the actual updating and rendering, so many of those problems that you're used to running into just go away.
00:40:49.349 --> 00:40:50.630
Like they just go away.
00:40:50.789 --> 00:40:54.789
And what's an example that you're thinking of right now that you're like, this can't work?
00:40:54.949 --> 00:40:56.789
I need more organization than this.
00:40:57.190 --> 00:41:00.789
I don't think I have anything where I'm like, oh, you know what?
00:41:00.869 --> 00:41:09.029
I don't think it'll work for this case because I'm just thinking, as I'm like looking at it, I'm like, yeah, it has to be more how we can do this.
00:41:09.269 --> 00:41:13.590
But it almost is the same way from when I went from jQuery to stimulus.
00:41:13.750 --> 00:41:23.509
I mean, there was some React and Vue.js in between that, but even when I first looked at stimulus, I was like, uh, you know, there's something I'm missing.
00:41:23.590 --> 00:41:29.590
And then it was like, well, no, it's just a really nice way of organizing your JavaScript so you don't get back into that jQuery soup.
00:41:29.750 --> 00:41:30.469
And I like that.
00:41:30.550 --> 00:41:34.630
I like that there's a kind of a defined, there's guardrails.
00:41:34.789 --> 00:41:38.469
I can still get it, I can still make it really fucking messy if I wanted to.
00:41:38.630 --> 00:41:45.029
And I have seen some messy stimulus controllers, but at least there's some guardrails.
00:41:45.590 --> 00:41:52.389
Data starter almost feels like a slightly sharper knife, where it's like, if you really want to, you can make this hard to grok.
00:41:53.110 --> 00:41:57.590
The thing is that I this excites me because it's like, cool, show receipts.
00:41:57.829 --> 00:42:12.550
Like, I I like I'm looking forward to seeing what because the thing is, I really do think that the signal and the reactive approach, the irony is that even though like I tend to like lower-level languages, I really do think Datastar is the best version of FRP functional reactive programming on the web.
00:42:12.869 --> 00:42:22.230
It takes the ideals and says, once you have reactive signals, it says when this thing changes, this thing updates, and these things affect these things, a lot of that structure that you had to put in place goes away.
00:42:22.469 --> 00:42:40.550
And then because all these signals and all this stuff, all these expressions were set up in your back end of choice, means that you use Ruby to define Ruby stuff and that the contents of a the equivalent of stimulus for you is stuff that you define in Ruby using Ruby constructs to then generate that text, because it's just text, just strings.
00:42:40.869 --> 00:42:43.670
Now all of a sudden, most of your logic is in Ruby.
00:42:43.750 --> 00:42:53.349
So you're in the language of your choice using the tools of your choice, which means most of that structure that you're looking for was already in your it's like saying templates can't be that simple.
00:42:53.509 --> 00:42:54.469
They have to have more logic.
00:42:54.550 --> 00:43:00.230
And it's like, yeah, yeah, the logic of how you define your view controllers or whatever is in your Ruby language.
00:43:00.389 --> 00:43:01.670
That's where all your work is.
00:43:01.909 --> 00:43:09.989
So that's the beauty, is that all that work doesn't magically go away, but that structure that you need actually lives in the language of your choice.
00:43:10.150 --> 00:43:10.309
Yeah.
00:43:10.469 --> 00:43:11.909
It doesn't exist even in the JavaScript.
00:43:12.070 --> 00:43:14.230
The JavaScript side is just the final declarative thing.
00:43:14.309 --> 00:43:19.670
It's just like saying SQL can't be, you can't just say from foo equals bar.
00:43:19.989 --> 00:43:21.190
You have to have generated that somehow.
00:43:21.269 --> 00:43:26.230
Well, yeah, you generate in the language of your choice, whether that's an RM or just concatenating strings.
00:43:26.469 --> 00:43:27.670
Yes, that's all it is.
00:43:27.750 --> 00:43:33.269
So all I'm saying with Datastar is you can have that same kind of like create your SQLite query however you want.
00:43:33.429 --> 00:43:34.789
That is logically simple.
00:43:34.949 --> 00:43:37.269
It's easy to vet, it's easy to test.
00:43:37.509 --> 00:43:41.029
Data star has now solved the web by making it more declarative.
00:43:41.269 --> 00:43:45.190
So it's just a set of strings, not a huge set of JavaScript.
00:43:45.349 --> 00:43:49.590
So I basically issued your problem by like, I reject your reality and substitute my own.
00:43:49.829 --> 00:43:51.190
You just don't need to do that anymore.
00:43:51.429 --> 00:43:51.989
Yeah, yeah.
00:43:52.150 --> 00:43:53.909
I'm very interested to give it a try.
00:43:53.989 --> 00:44:07.909
It always is like I can read a guide numerous times and come up with all of these thoughts, but it's once I start actually building something with it
that I'm like, oh, I like this, or okay, this is a pain point.
00:44:08.230 --> 00:44:13.269
Then I go to your Discord and go, this is a pain I'm having, and someone will be like, that's because your mental model's wrong.
00:44:13.829 --> 00:44:16.230
And I say go to the Discord sooner than you think.
00:44:16.389 --> 00:44:20.550
Because each language has different semantics on like why and how you would build things.
00:44:20.630 --> 00:44:25.989
Like the helpers that you're looking for, you might say, Hey guys, do you have ideas of like what's a good version of this helper?
00:44:26.070 --> 00:44:31.829
And Isamon, which is the guy that does the Ruby SCK, he'd be like, Oh yeah, yeah, we can just add those.
00:44:32.070 --> 00:44:32.469
Like, cool.
00:44:32.550 --> 00:44:36.150
Like we can just have a separate module for Rails that does like basically wraps up.
00:44:36.469 --> 00:44:41.829
But the thing is, the reason why most of that stuff doesn't exist is because once you get into it, you may go, I don't need any of this.
00:44:41.989 --> 00:44:42.389
Right, right.
00:44:42.630 --> 00:44:42.789
Yeah.
00:44:43.110 --> 00:44:51.429
That's the part that I'm actually more interested in the next conversation of having like, okay, that you've had all the guardrails off, you've had the knife the way it is.
00:44:51.590 --> 00:44:54.630
It's like having a Suba on a lightsaber.
00:44:54.789 --> 00:44:57.909
There's no guardrail on a lightsaber, like either you know how to use it or you die.
00:44:57.989 --> 00:45:06.710
Like it's kind of that thing of like maybe you don't need as much of a guardrail as you think you do because everything's so simple, it's a mood issue.
00:45:06.789 --> 00:45:12.869
So I'm more curious to see where that goes for you and tell us what we're missing.
00:45:13.029 --> 00:45:20.389
Because we're very much we're reactive to the community in that, like we don't build stuff just to say, hey, let's wrap this thing and wrap this thing.
00:45:20.469 --> 00:45:23.590
It's like what are the things that you need and let's explore that.
00:45:23.829 --> 00:45:25.509
Yeah, and do you actually need them?
00:45:25.829 --> 00:45:31.989
And the thing is, most people come in saying, Oh, I want this, I want that, and then they actually build something and go, Oh, never mind.
00:45:32.150 --> 00:45:36.389
It's a daily thing on our Discord, is like, oh, right, you must unlearn what you have learned.
00:45:36.630 --> 00:45:37.269
Yeah.
00:45:37.750 --> 00:45:45.029
Related to Datastar, but very different from the technical stuff we've been talking about that I did want to touch on because I'm curious about it.
00:45:45.349 --> 00:45:52.309
I don't run any money making projects or have businesses or anything, but I'm always curious.
00:45:52.550 --> 00:45:58.710
So, some of Data Star has that pro version as a way of like funding development, etc.
00:45:58.949 --> 00:46:00.869
Like, how do you decide what's free?
00:46:00.949 --> 00:46:02.630
How do you decide what's pro?
00:46:03.029 --> 00:46:05.590
Okay, so there's kind of gone through a couple different Different iterations.
00:46:05.670 --> 00:46:08.949
The first thing we did is we were basically getting to the 1.0.
00:46:09.110 --> 00:46:14.230
We're now like there, we're just like literally we were actually deciding if the next RC is literally just 1.0.
00:46:14.389 --> 00:46:16.309
In my mind, that's it could have been a bug fix.
00:46:16.469 --> 00:46:17.989
Most of the stuff could have been a bug fix.
00:46:18.070 --> 00:46:27.829
So we a while back when we were making signaled library faster and all this stuff, for a while there, when I first came out with data star, it literally was here's three plugins, here's how you write your own plugin.
00:46:28.230 --> 00:46:29.110
Good luck, everybody.
00:46:29.269 --> 00:46:34.789
Because I basically like if you use data on data signals and data in knit.
00:46:35.029 --> 00:46:40.710
I think those are the only like I basically had a couple of ones that I used, and I'm like, this is good enough for me if anybody needs plugins.
00:46:40.949 --> 00:46:43.750
But what happened is people started coming in and saying, Hey, how do you write this plugin?
00:46:43.909 --> 00:46:44.630
How do you write this plugin?
00:46:44.949 --> 00:46:50.309
And it was just so easy for me to write them that I was like, oh, let me do an example first for you before you start writing plugins.
00:46:50.389 --> 00:46:55.429
Like, let me make sure the plugin system worked correctly before I start telling people just write whatever plugin you want.
00:46:55.590 --> 00:46:59.190
So over time, over the years, we ended up with a ton of plugins.
00:46:59.269 --> 00:47:02.949
But what I found is a lot of the plugins people should not be using.
00:47:03.110 --> 00:47:08.710
So the irony is like when we did the whole revamped, we basically forked our own project and like redid everything.
00:47:08.789 --> 00:47:11.509
And I said, these are the plugins that people actually need.
00:47:11.670 --> 00:47:15.349
And the rest of these you shouldn't use and their support burden.
00:47:15.590 --> 00:47:25.989
So what we did is we actually rewrote like when we were rewriting them, we actually put them in pro because we're like, if you're gonna be a support burden, we want you to actually pay into the project.
00:47:26.309 --> 00:47:27.190
Yeah, that's fair.
00:47:27.429 --> 00:47:30.469
So a perfect example one that people got really mad at people get mad at this.
00:47:30.550 --> 00:47:33.429
The irony is the old plugins are 100% there.
00:47:33.590 --> 00:47:36.309
Not only that, is the people have made community versions of this stuff.
00:47:36.389 --> 00:47:42.630
In fact, there's literally a project called Data Spa, which I highly disagree with, but again, go for it.
00:47:42.710 --> 00:47:43.590
Do your thing, have fun.
00:47:44.789 --> 00:47:45.829
But we don't have to support it.
00:47:45.989 --> 00:47:49.829
So we're
in a weird spot right now where some plugins I think you should not be using, which are in pro.
00:47:49.909 --> 00:47:57.750
But there are things like, for example, I have a data animate that rivals, if not, is better than anime.js out of the box that makes it all declarative.
00:47:57.909 --> 00:47:58.710
That's really exciting.
00:47:58.869 --> 00:48:01.909
The problem is that plugin is so big, it's almost as big as all of Datastar, right?
00:48:01.989 --> 00:48:03.590
Like it does all the animation stuff.
00:48:03.750 --> 00:48:05.509
So it's like a green sock or something like that.
00:48:05.670 --> 00:48:10.949
So it's plugins that are too big or that are out of scope or are things that I don't think you should use.
00:48:11.190 --> 00:48:12.949
For example, that is data persist.
00:48:13.269 --> 00:48:17.269
People want to use data persist all the time to basically save it off to local storage, right?
00:48:17.750 --> 00:48:20.550
The problem is now you have a cache on your cache.
00:48:20.710 --> 00:48:23.750
Now you're trying to save state locally that actually should have gone to the server.
00:48:23.829 --> 00:48:26.389
And people are like, well, what if it's just for a light or dark theme?
00:48:26.630 --> 00:48:32.789
Most of the time, you want to send that light or dark theme because you might change the images that you're using, you might change subtle details.
00:48:33.110 --> 00:48:37.269
It's not just a light or dark of tailwind CSS if you do things correctly, right?
00:48:37.349 --> 00:48:45.429
So and there's also things like data replace URL, where basically people want to mess with the use signals to drive the URL.
00:48:45.670 --> 00:48:45.989
Sure.
00:48:46.150 --> 00:48:48.309
And people are like, well, yeah, why is that a pro thing?
00:48:48.389 --> 00:48:52.710
That's but the problem is what happens when you are updating at 144 frames per second.
00:48:52.869 --> 00:48:54.630
Now your history is completely blown out.
00:48:54.869 --> 00:48:58.710
Almost always when you're doing that stuff, you're using it wrong.
00:48:58.869 --> 00:49:02.230
You're doing something that's going against hypermedia, it's doing a spa-like thing.
00:49:02.389 --> 00:49:08.070
So a lot of the stuff is either too big or complicated, or stuff that actively goes against the tau of Datastar.
00:49:08.389 --> 00:49:09.829
So sure, that's part of it.
00:49:09.989 --> 00:49:19.590
But the other thing is now we also have things that are pro features, like we have it at full inspector, because in the browser, SSE is kind of hard to like it, doesn't always work, the debug panel.
00:49:19.670 --> 00:49:24.150
So we have a full inspector that does all that kind of stuff, does all the tracking of your signals on the page.
00:49:24.389 --> 00:49:28.949
When you hover over it, it highlights where it's used on the page, all the events that are coming in, all the SSE.
00:49:29.110 --> 00:49:30.230
It's a pro tool.
00:49:30.389 --> 00:49:35.269
And then I have
the stellar thing that I just did, which I think is a tailwind killer, and all this stuff is part of a lifetime license.
00:49:35.429 --> 00:49:36.869
So you help the project.
00:49:37.110 --> 00:49:39.110
Some people bought the license and don't use any of the pro features.
00:49:39.190 --> 00:49:41.989
They're just like, I want to help the project because it is under a 501c3.
00:49:42.389 --> 00:49:43.989
It's set up in that way.
00:49:44.070 --> 00:49:45.029
It is a nonprofit.
00:49:45.190 --> 00:49:57.989
So me and Ben, the other guy that runs the thing, we didn't want to be in a situation like Tailwind was where if data store is successful, we want to have some money coming in that is equal to the success that we have.
00:49:58.150 --> 00:50:02.789
Whereas with Tailwind, all they're doing is competing against everybody else doing Shad CMs and the boots.
00:50:03.269 --> 00:50:06.469
Anything they do isn't really helping grow the community.
00:50:06.630 --> 00:50:16.309
So we have more of the kind of like a game engine or Pico 8 style thing of like, if you do pro features, it's like buying the game and then all the mods are available for free forever.
00:50:16.469 --> 00:50:24.469
But you have this core engine that is paid so that if it does become a super big thing, then the project could become self-sustaining, possibly.
00:50:24.710 --> 00:50:33.989
It's more of an experiment of like you use Stellar for a day, which we haven't talked about, or used any of the pro features for a day, you've now paid for the license for the rest of your life.
00:50:34.230 --> 00:50:38.550
So people say it's expensive for a JavaScript framework, but it also has a tailwind killer.
00:50:38.710 --> 00:50:43.670
It'll have a whole framework library, a UI library coming soon that's also agnostic to language.
00:50:43.750 --> 00:50:47.750
So now everyone can be using the same components agnostic of language.
00:50:47.909 --> 00:50:49.509
These are all good things, in my opinion.
00:50:49.670 --> 00:50:53.429
So yeah, it's more about sustainability if it gets too big.
00:50:53.670 --> 00:50:53.829
Okay.
00:50:54.070 --> 00:50:56.469
But if it's not big, it doesn't make that much of a difference.
00:50:56.630 --> 00:51:01.670
We actually added it up over the year that we have far less than a minimum wage doing it.
00:51:01.909 --> 00:51:05.670
So in fact, I haven't taken a single dime out of it.
00:51:05.989 --> 00:51:10.150
It's there so that we can pay for like going to conferences or running the website or stuff like that.
00:51:10.389 --> 00:51:13.590
If you're gonna be a burden, you should be no, that makes sense.
00:51:13.750 --> 00:51:14.789
That totally makes sense.
00:51:14.949 --> 00:51:15.590
Yeah, yeah.
00:51:15.829 --> 00:51:16.469
Yeah.
00:51:16.789 --> 00:51:18.070
It's always interesting to me.
00:51:18.150 --> 00:51:21.909
It's like, cool, we have an open source project and we have to make money on it.
00:51:22.070 --> 00:51:23.269
How the hell do you do that?
00:51:23.429 --> 00:51:24.710
Like, how do you decide what to do?
00:51:24.789 --> 00:51:26.230
And I don't think you do.
00:51:26.550 --> 00:51:29.670
Problem is that there's really two ways, because I work at Scenadia uh during the day.
00:51:29.829 --> 00:51:36.070
Like my day job is working on Nats, which is an open source project for real-time distributed messaging and stuff like that.
00:51:36.150 --> 00:51:46.550
And it's open source, and I know all the media, like it is building a company that's not VC based, that's doing open source, I think is basically impossible.
00:51:46.789 --> 00:51:55.670
So my thing is more I want it to be that if it is seen as a net good for the world, that it can help pay for being able to actually go to a conference.
00:51:55.750 --> 00:51:56.789
Like, that's all I want out of it.
00:51:56.869 --> 00:52:02.150
Like it's a more of a pay-forward thing, and also part of the thing, too, is I just wanted someone to prove me wrong.
00:52:02.309 --> 00:52:12.469
I'm not a great speaker, but I did a UtahJS conference like a couple of years ago, where I basically said, I think Datastar is really good, and like someone proved me wrong.
00:52:12.630 --> 00:52:18.469
And since then, no one has, if anything, it's gotten I'm I'm much more confident than I was during that talk.
00:52:18.550 --> 00:52:24.630
And I was like doing real-time stuff at 140 frames per second, like real-time 3D stuff in the browser, and it was fine, and it worked fine.
00:52:24.869 --> 00:52:37.429
The thing is that if it is seen as an I do want to need to explore, but also there's a good chance that like if it at all became successful in the way that like Tailwind is just the default, I would probably give most of the stuff away.
00:52:37.509 --> 00:52:42.309
Like, once it's like, oh no, this is paid for the development of the thing, then just give it away from there.
00:52:42.630 --> 00:52:44.949
I want to be able to support other developers and other things.
00:52:45.029 --> 00:52:49.750
So the 501c3 really is set up to do that, it's there to help developers in the long run.
00:52:49.829 --> 00:52:53.349
We just don't have enough to really make that a possibility yet.
00:52:53.590 --> 00:52:54.150
All right.
00:52:54.789 --> 00:52:59.269
Super dangerous, loaded question, but I feel like I have to ask it at this point.
00:52:59.349 --> 00:53:00.550
Like, there's no way around it.
00:53:01.190 --> 00:53:04.869
AI, how do you use it and how does it work with Data Star?
00:53:05.750 --> 00:53:06.469
Poorly.
00:53:06.789 --> 00:53:12.789
And what I what's been really interesting is Datastar is tiny, right?
00:53:12.949 --> 00:53:21.429
It is so small that it'll fit in any context window, even the nano ones, even the like the tiny, tiny windows of context.
00:53:21.750 --> 00:53:22.789
It's so small.
00:53:22.949 --> 00:53:31.269
And yet when you try to build something with it, most things like the codexes and the clods and the Geminis,
they basically say, Cool, I'm gonna start making a React app.
00:53:31.670 --> 00:53:44.230
The thing is, they're so overfit to the data that they've been trained on that you can make them work with the data star thing, but we actively don't try to hit the like data star is so simple.
00:53:44.309 --> 00:53:50.949
And the thing is, this is the thing that I think you'll run into, is that you're gonna get to start doing stuff on a page and you're gonna literally say, That's it.
00:53:51.190 --> 00:53:55.190
And the problem is it's so surgical in where you use it on most pages.
00:53:55.829 --> 00:54:07.429
A data star site is whatever your framework of their it's a Sinatra site that happens to have some data star on it, like it completely gets out of the way in a way that uh is not the norm.
00:54:07.750 --> 00:54:09.829
So the LLMs don't help you.
00:54:10.309 --> 00:54:13.989
You don't need LLM to help make you a website that does data star.
00:54:14.389 --> 00:54:15.269
It's a non-issue.
00:54:15.509 --> 00:54:20.469
So the thing is, I think the LLMs in general are faster.
00:54:20.550 --> 00:54:23.029
Like I'm a pretty fast typer and it types faster than I can.
00:54:23.110 --> 00:54:29.829
When I say, hey, make this change in 20 places and do this thing with that, like change these text cases to this thing, it's great at that job.
00:54:29.909 --> 00:54:33.349
It's a good aggregator of information, not has no intelligence.
00:54:33.509 --> 00:54:35.989
So if it sees patterns, it'll do those patterns.
00:54:36.150 --> 00:54:40.949
The problem is most of the web is sloppy Next.js garbage.
00:54:41.190 --> 00:54:43.110
And so it goes to the median.
00:54:43.269 --> 00:54:47.110
Like when you're talking about a bell curve, it's never gonna make you something innovative or interesting.
00:54:47.190 --> 00:54:48.630
It's gonna give you the middle of the bell curve.
00:54:48.710 --> 00:54:50.550
But that's where most projects go to die.
00:54:50.869 --> 00:54:52.309
There's nothing interesting going on there.
00:54:52.389 --> 00:54:53.110
Now it depends.
00:54:53.190 --> 00:54:56.710
If your job is to basically make websites for plumbers, right?
00:54:56.869 --> 00:55:01.190
Or for like local businesses or like an accounting firm, those jobs are dead.
00:55:01.269 --> 00:55:04.550
So the thing is, all you're doing is like going towards the median.
00:55:04.869 --> 00:55:07.269
People are gonna realize they can get that for themselves.
00:55:07.509 --> 00:55:08.789
Those kind of things are dead.
00:55:08.869 --> 00:55:11.909
So I always try to work on the outlier things that are interesting.
00:55:12.070 --> 00:55:16.150
So for me, it's a tool, but I think it also is the death nail of the junior programmer.
00:55:16.309 --> 00:55:22.150
Like you don't have that time to really explore and learn how to be wrong and get an opinion of things.
00:55:22.389 --> 00:55:24.150
I don't know what to do for younger people.
00:55:24.309 --> 00:55:24.550
Yeah.
00:55:25.750 --> 00:55:33.829
But again, it's a transformative tool, and yet most of the time, the way it's being used is complete slot.
00:55:34.230 --> 00:55:36.710
What's interesting is I only use it for things I already know.
00:55:36.869 --> 00:55:43.989
I have this specific thing I need to change in this way, this pointer needs to change to this, I need to make this area and allocator, check all the usages of this, like that kind of stuff.
00:55:44.070 --> 00:55:46.150
I like I know what I need to do, I just do it faster.
00:55:46.309 --> 00:55:50.469
But when people use it to explore things they don't know, I think that's crazy.
00:55:50.630 --> 00:55:52.309
Like it's never right, ever.
00:55:53.429 --> 00:55:58.389
So, and the thing is if it's right, it's right in the for the wrong reasons, and that's more dangerous.
00:55:58.550 --> 00:56:02.389
So I think it really does make you more of the developer you already are.
00:56:02.710 --> 00:56:10.389
To me, I say it's a scalar on your vector, which it's just like whatever direction and pointing you are, it just amplifies whatever that is.
00:56:10.630 --> 00:56:12.469
So if you're a lazy developer, you're gonna be lazier.
00:56:12.550 --> 00:56:17.349
If you're like really hardcore and you want to work on three different projects, you're gonna work on three different projects and you're gonna be able to go faster.
00:56:17.509 --> 00:56:18.710
So I don't know.
00:56:18.949 --> 00:56:21.190
I think people have collectively lost their minds.
00:56:21.429 --> 00:56:23.829
But what else is new?
00:56:24.150 --> 00:56:31.349
But I think it's one of those things of like there's something beautiful in it, but the beauty is also the horror itself.
00:56:31.429 --> 00:56:38.710
It's like it's almost impossible to do anything in life without taking someone else down just because of our global economy.
00:56:38.869 --> 00:56:43.349
It's built off the backs of somebody somewhere, somehow, even if you don't feel it directly.
00:56:43.670 --> 00:56:47.829
But you have to be aware of that, you have to be cognizant that there's a cost to this.
00:56:48.309 --> 00:56:59.349
And I don't know what's gonna happen in the next five years, given that it's so heavily subsidized right now, and the debt servicing on these companies is gonna destroy it well before technical breakthrough.
00:56:59.590 --> 00:57:05.269
So to me, I use it, but also at the same time, if it went away tomorrow, I wouldn't it wouldn't bother me at all.
00:57:05.429 --> 00:57:08.150
So I don't know what average developer means anymore.
00:57:08.309 --> 00:57:13.029
Especially lead code is dead, but I also thought lead code was a complete waste of time anyway.
00:57:13.349 --> 00:57:14.710
Can't disagree with you there.
00:57:14.789 --> 00:57:17.190
So but the thing is that like lead code now goes away.
00:57:17.349 --> 00:57:19.429
So what defines a good developer?
00:57:19.750 --> 00:57:22.230
It's the projects they actually put their
effort into.
00:57:22.389 --> 00:57:22.789
I don't know.
00:57:22.869 --> 00:57:25.590
Like it's not even a race to the bottom, it's a race towards the middle.
00:57:25.670 --> 00:57:26.630
And that's the interesting thing.
00:57:26.949 --> 00:57:33.750
It's not the complete garbage because it wouldn't get popular enough to get into the training data, and it's not the stuff like Datastar, it just doesn't care about.
00:57:33.829 --> 00:57:35.029
It cares about getting the mean.
00:57:35.110 --> 00:57:38.550
So it's a race to the middle means that there's gonna be bigger jobs.
00:57:38.710 --> 00:57:44.949
I'm from the middle of nowhere, Wyoming, and trying to get a single book on was incredibly hard to do, right?
00:57:45.029 --> 00:57:48.150
Like I had to order out for months to get a book on QBates, you know, that kind of thing.
00:57:48.309 --> 00:58:00.550
So at the time there was a desert of knowledge where I just did not have access to anything going on, and it feels like now we're in such a flood of information that it's basically the same as a desert.
00:58:00.710 --> 00:58:02.710
The ocean is a desert from the top surface.
00:58:02.789 --> 00:58:06.469
Like when you're on a rowboat and when you're in the middle of the desert, it's the same feeling.
00:58:06.550 --> 00:58:10.150
Like there's nothing around you, you have no access to water, there's nothing there.
00:58:10.230 --> 00:58:13.509
So the weird thing is we're flooded with information, but it still feels like a desert.
00:58:14.550 --> 00:58:16.550
It's really hard to drink from a fire hose.
00:58:16.710 --> 00:58:17.029
Yeah.
00:58:17.269 --> 00:58:19.989
Well, and also the thing is that everything you learn right now is useless.
00:58:20.070 --> 00:58:22.869
Like even the MCP stuff, all of a sudden it's oh no, not that.
00:58:22.949 --> 00:58:24.389
It's skills, it's this, it's that.
00:58:24.550 --> 00:58:28.070
You might as well just hold back and keep building stuff in the meantime.
00:58:28.230 --> 00:58:31.269
Find a use for it if you can, but don't let it keep you up at a night.
00:58:31.429 --> 00:58:40.309
I think it's the FOMO stuff that's VCs are built around the idea of looking for high amounts of volatility.
00:58:40.550 --> 00:58:44.309
Venture funds and all that are built around volatility, not around innovation.
00:58:44.550 --> 00:58:56.630
So you have to know who's pulling the strings of again, we're talking about it, so they succeeded, but there's the one CEO that said not being a developer is now a virtue in this new world.
00:58:56.869 --> 00:59:04.230
Like the replica, like, but we're talking about it because it's built to build in FOMO and aggression.
00:59:04.469 --> 00:59:06.869
It is intended to do that.
00:59:07.110 --> 00:59:07.909
That's the intent.
00:59:07.989 --> 00:59:13.429
So, like, do you feed into that or you just take a more stoic approach of like embrace that this is what they're trying to do?
00:59:13.670 --> 00:59:14.230
I don't know.
00:59:14.389 --> 00:59:22.309
I don't know what the right answer is, but I just feels like it's impossible to get away from it, so gotta ask.
00:59:22.630 --> 00:59:23.909
I also don't know.
00:59:24.150 --> 00:59:28.070
I'm kind of crowdsourcing how everyone else is using it.
00:59:28.230 --> 00:59:29.989
What do they think of it?
00:59:30.230 --> 00:59:34.469
Yeah, I've found some really useful ways to use it in my day job.
00:59:34.630 --> 00:59:36.949
I've been exploring a ton with it.
00:59:37.269 --> 00:59:41.509
Like my usage has gone up exponentially in the past couple of months.
00:59:41.670 --> 00:59:55.269
It's still not doing a lot of code writing for me, it's doing a lot of like validating my thoughts or showing me why something I think might work, might not work, or things like that.
00:59:55.509 --> 00:59:59.909
I'll tell you right now, I have some stuff going on in the background that's happening right now while we're talking.
01:00:00.150 --> 01:00:04.469
One of them, for example, is I've been really digging into Odin a lot.
01:00:04.550 --> 01:00:09.029
I think Odin's a beautiful language, it's basically C fixed for me, which is wonderful.
01:00:09.349 --> 01:00:13.590
And the thing is that there's some things that kind of suck in that space.
01:00:13.670 --> 01:00:21.670
Like, for example, they don't have a good HTTP server story, but there are C projects like H2O, which are have a great story.
01:00:21.829 --> 01:00:25.269
So writing bindings between those things is just a row process.
01:00:25.429 --> 01:00:30.550
So I have it going off and doing a complete binding generation of that, and it's great at that.
01:00:30.710 --> 01:00:38.230
Another thing, I think NixOS is this like is way better than Docker at being able to make exactly binary reproducible versions of things.
01:00:38.389 --> 01:00:40.389
Like NixOS is a really interesting project.
01:00:40.550 --> 01:00:45.509
But the thing is, the configurations tend to be a bit of a nightmare depending on Wayland and all this other stuff.
01:00:45.670 --> 01:00:53.429
But giving that to an LLM and saying, hey, I want to be in this state, and it is a reproducible state, and if it ever gets something wrong, I can rip it out and pull it back in.
01:00:53.590 --> 01:00:57.190
And that kind of thing, it can write configs faster than I can.
01:00:57.429 --> 01:00:57.989
That's amazing.
01:00:58.150 --> 01:01:02.949
So it's taking on projects I wouldn't normally do because I wouldn't say, give me all the H2 bindings.
01:01:03.110 --> 01:01:08.150
Like I just would try to figure out Swig or some other project to try to make that happen because I just wouldn't tackle it.
01:01:08.309 --> 01:01:12.789
Whereas now I can tackle it because it's all rote stuff that either works or doesn't work.
01:01:12.949 --> 01:01:16.630
There's no opinions in there, it's just work.
01:01:17.349 --> 01:01:17.750
Right.
01:01:17.989 --> 01:01:20.710
That part it's beautiful at, and I see value in it.
01:01:20.789 --> 01:01:34.389
But the thing is, people are using it to like define my neighbor, is using it to sell their house because they think this other thing's gonna happen and this thing, and like their logic makes literally no sense, but they got it from ChatGPT, and they're literally selling their house and moving because of it.
01:01:34.550 --> 01:01:36.710
I don't know what to do with that kind of information, right?
01:01:37.190 --> 01:01:38.949
That is a kind of psychosis.
01:01:39.429 --> 01:01:44.630
There's gonna be winners and losers in that thing, or I'm just wrong, but then the whole world burns if I'm wrong.
01:01:44.710 --> 01:01:45.590
So I don't know.
01:01:45.750 --> 01:01:47.429
Either way, I have to be okay with it.
01:01:47.670 --> 01:01:50.789
And it's sort of like when JavaScript frameworks got big, right?
01:01:50.869 --> 01:01:55.909
There was a new one or a new thing to learn every other day, every week.
01:01:56.230 --> 01:01:58.789
Feels a lot like that too, just like you said.
01:01:59.190 --> 01:02:08.550
I think there's a good chance of the boiling frog again of people don't realize how much they have lost the ability to actually be cognizant and understand what code is doing.
01:02:08.710 --> 01:02:12.389
Good things are gonna come out of it because it's like you're gonna see the people that are actually really interested in coding.
01:02:12.550 --> 01:02:20.309
Because coding has kind of become a somewhat of a status thing of like coders get paid well and they get to work remotely and all this stuff.
01:02:20.469 --> 01:02:23.989
Like the people that actually want to do the work are gonna be the ones that stick around.
01:02:24.150 --> 01:02:28.230
So it's gonna be a great filter, but I think that that in the long run is a good thing.
01:02:28.389 --> 01:02:33.110
The VC funding stuff has to the actual financials don't make any sense.
01:02:33.349 --> 01:02:39.029
So my only hope is that local model generation figures out its own thing.
01:02:39.110 --> 01:02:48.150
Because I would love to have things that are trained specifically on my code base or the Linux kernel, or like here's how SQLite does things, and like that kind of local training for your own models.
01:02:48.389 --> 01:02:52.710
I think that long term going forward, people are like, hey, here's my model of how I do things, and here's my thing.
01:02:52.789 --> 01:02:53.670
Hey, let's collaborate.
01:02:53.750 --> 01:03:04.949
Like, there's a beautiful future in that, but the VC backed giant models that are burning water sources and rainforests, I think that is an untenable thing.
01:03:05.269 --> 01:03:09.509
So yeah, there might be some good that comes out of it, but not in the next five years.
01:03:09.750 --> 01:03:11.590
Yeah, we'll find out.
01:03:11.989 --> 01:03:16.789
The next question, because I know we've covered so much in our what are you working on?
01:03:17.190 --> 01:03:18.789
What kind of blockers do you have?
01:03:18.949 --> 01:03:23.110
But since Datastar is done, don't really have blockers there.
01:03:23.509 --> 01:03:25.349
What do you have as a blocker?
01:03:25.909 --> 01:03:30.309
So my blockers right now are I want to be done.
01:03:30.469 --> 01:03:35.429
And the thing is, to me, programming is always a tool for extending your abilities.
01:03:35.670 --> 01:03:41.909
And my thing is again, it seems like a weird boast until you start actually playing with it, but the web, the JavaScript is done.
01:03:42.070 --> 01:03:46.630
All the things that you are concerned about are non-issues, and I can't explain that until you try it.
01:03:46.869 --> 01:03:48.389
So that part's done.
01:03:48.630 --> 01:03:51.110
The web just being a non-issue is pretty cool.
01:03:51.429 --> 01:03:55.349
CSS now, to me, with the stellar stuff, is basically done.
01:03:55.590 --> 01:04:00.869
I have the stellar UI stuff to do, and then I'm going back to working on my database when I have time.
01:04:01.110 --> 01:04:09.110
I think that's the thing that's really what I got interested in in the first place is like, how do I solve data at large petabyte scales?
01:04:09.269 --> 01:04:11.509
And that's the project problem that I'm going back to.
01:04:11.590 --> 01:04:17.029
So my blocker is that I want to help everybody else so I can get back to the thing that I was doing originally.
01:04:17.190 --> 01:04:24.869
But I think it's a net good because I become such a better developer dealing with other people's intents and like telling people no.
01:04:25.029 --> 01:04:26.789
I've gotten much better at that.
01:04:26.949 --> 01:04:34.789
And so my blocker is literally getting back to the thing that I wanted to do, my original intent.
01:04:35.029 --> 01:04:37.750
But also the problem has changed in my head over time.
01:04:37.989 --> 01:04:41.029
So kind of like the LLM to make you more what you want to be.
01:04:41.190 --> 01:04:46.070
The database I would have written before data starting, the data, the one I wrote after it is a very different database.
01:04:46.389 --> 01:04:47.429
Am I missing one more thing?
01:04:47.590 --> 01:04:52.309
My blocker is am I on the right road mentally to move forward?
01:04:52.389 --> 01:04:53.190
Because that's a big project.
01:04:53.269 --> 01:04:54.469
I mean, obviously, that's a huge project.
01:04:54.550 --> 01:04:59.110
And the question is, do I have the right mental model and do I need more time thinking about it?
01:04:59.269 --> 01:05:03.509
So that's probably my only blocker for things moving forward because everything else is kind of rote.
01:05:03.670 --> 01:05:13.829
Like we are gonna be doing Stellar UI, which is the set of components, and that's just knocking through all the things that are available in Daisy UI or Shadsian or like that's just work.
01:05:14.070 --> 01:05:15.909
That's not a blocker, that's just stuff to do.
01:05:16.230 --> 01:05:27.349
So if you would have talked to me a year ago, I would have had a huge list of
blockers, but I'm in this excited point where not only am I not blocked, but I think most of the web is not blocked.
01:05:27.670 --> 01:05:33.190
If they really gave it a try, I think most people would go, that's it, and I can just get back to work.
01:05:33.349 --> 01:05:35.190
There could be a huge impact.
01:05:35.429 --> 01:05:36.869
I just don't know how to make that impact.
01:05:36.949 --> 01:05:41.989
I'm not like a big speaker, I'm not a I don't have any clout in the Twitter verse or anything like that.
01:05:42.230 --> 01:05:46.230
I really do think if it's not Datastar, it's something that looks very, very similar to Data Star.
01:05:46.469 --> 01:05:48.230
If someone could make a better version of it, I would love it.
01:05:48.309 --> 01:05:49.029
That'd be great.
01:05:49.269 --> 01:05:54.550
But just like the way React felt so good compared to how you did things before, right?
01:05:54.630 --> 01:05:56.630
Like you felt like, oh, I could make Google Maps.
01:05:56.710 --> 01:06:01.110
Like you had that feeling when you tried it, like, okay, I get that why this is different.
01:06:01.349 --> 01:06:07.989
This is such a paranoid, this is even more of a shift than that was to get back to I can't believe how simple this can be.
01:06:08.150 --> 01:06:09.509
What have we been doing?
01:06:09.909 --> 01:06:13.909
I just hope that that opens up the doors to the next person that makes something even better than that.
01:06:14.070 --> 01:06:15.029
I'm looking forward to that.
01:06:15.110 --> 01:06:17.509
So, but yeah, I guess I do have one blocker.
01:06:17.590 --> 01:06:22.550
The blocker is I don't know how to reach people without sounding like I'm selling something.
01:06:22.789 --> 01:06:26.630
Like, sure, I don't want to do the conference talks.
01:06:26.789 --> 01:06:30.469
I already feel like I've put enough into the open source community.
01:06:30.869 --> 01:06:33.110
How do people like you not know already know about datastar?
01:06:33.429 --> 01:06:38.309
I'm gonna be actually talking to Richard Felman, who's the guy behind Rock, and he's done a bunch of things around Elm.
01:06:38.550 --> 01:06:41.349
And he was like, I just heard about Datastar from this other podcast I did.
01:06:41.429 --> 01:06:46.949
And I was like, how can you, of all people, like he's like one of the the Elm in Action is like a really great book?
01:06:47.029 --> 01:06:51.269
And like Datastar is like a condensed version of Elm, but without having any language behind it.
01:06:51.349 --> 01:06:53.829
Like, you don't even need the language because you have the concepts.
01:06:54.150 --> 01:06:55.269
And he didn't know about it.
01:06:55.349 --> 01:06:57.670
And if anyone should know about it, it would be him.
01:06:57.909 --> 01:07:01.349
How do you reach people without but also not care?
01:07:01.509 --> 01:07:02.949
I'm at the point where I don't care.
01:07:03.110 --> 01:07:06.630
I'm not doing it out of any kind of self-glory or anything.
01:07:06.710
--> 01:07:08.230
I just want to see the web be a better place.
01:07:08.389 --> 01:07:09.110
What do you do?
01:07:09.349 --> 01:07:10.469
Yeah, I got nothing for you.
01:07:10.630 --> 01:07:11.029
Sorry.
01:07:11.190 --> 01:07:12.710
That's no, that's a real blocker.
01:07:13.029 --> 01:07:13.989
That's a real blocker, right?
01:07:14.230 --> 01:07:15.349
That is a real one, yeah.
01:07:15.590 --> 01:07:22.230
I'm reeling from discovering it because someone else listened to a podcast episode of mine and was like, why not datastar?
01:07:22.309 --> 01:07:23.909
And I'm like, the fuck is datastar?
01:07:24.230 --> 01:07:25.509
Like, that's why not data star.
01:07:25.829 --> 01:07:27.349
I didn't even know it was a thing.
01:07:27.670 --> 01:07:29.829
And now I'm like, oh, I've really got to play with this thing.
01:07:29.989 --> 01:07:36.789
But the thing is funny is that I'm gonna play devil's advocate, but we have all these SDKs, we have full written guides, we have multiple talks.
01:07:37.110 --> 01:07:41.989
One of the talks is from David Nolan and his group or that team.
01:07:42.150 --> 01:07:54.949
To me, David Nolan's the guy who's partially to blame for React being popular because he made a version in ClojuScript that said, Hey, if you do shoot component update and you do things using the closure constructs, you can actually make React really fast.
01:07:55.110 --> 01:07:57.110
And then all of a sudden, everyone's like, Well, React's really fast.
01:07:57.190 --> 01:07:58.389
It's like, no, no, no, no, no, no.
01:07:58.550 --> 01:08:01.429
If you do these specific things, it can be pretty fast.
01:08:01.670 --> 01:08:05.190
The thing is that people just hop onto these weird Trained.
01:08:05.269 --> 01:08:09.750
So we have all the SKs, we have guides, we have a bunch of talks, we have success stories.
01:08:10.309 --> 01:08:11.349
What else can you do?
01:08:11.590 --> 01:08:13.909
Yeah, it's just discoverability at that point.
01:08:14.150 --> 01:08:22.949
You're just talking about not wanting to go and do conference talks, not wanting to be on a lot of podcasts, but like, how else do people find out about the new tech?
01:08:23.029 --> 01:08:25.590
How else do people find these things?
01:08:26.229 --> 01:08:36.710
Early in my career, I learned so much about thinking about code and thinking about how I'm building something from listening to podcasts with other people talking about that kind of stuff.
01:08:36.869 --> 01:08:41.670
And now that I run a podcast, I learn a lot from the people that come on and I ask them a ton of questions.
01:08:41.750 --> 01:08:44.389
And it's like, but I still struggle to find a guest.
01:08:44.469 --> 01:08:46.069
I'm like, I don't know who's doing something cool.
01:08:46.229 --> 01:08:48.309
Like, who wants to come on the show?
01:08:48.550 --> 01:08:49.349
I don't know.
01:08:49.509 --> 01:08:51.349
I know like six people.
01:08:52.710 --> 01:08:54.389
I'm happy to come on to this.
01:08:54.469 -->
01:08:58.550
I would like to see this as a journey into getting back to the web.
01:08:58.789 --> 01:09:06.070
I want to have more of the conversation of not just what I've been up to, but I want to see does this make an impact now that you know about it?
01:09:06.390 --> 01:09:13.190
Is it just a discoverability of the first step, or is it that it's different enough that people are like, eh, I'm good.
01:09:13.989 --> 01:09:24.390
We've had quite a few success stories of people taking our stuff and being orders of magnitude faster or less code, or I can send you a bunch of these of being faster, but we've never had anybody that says, I'm going back.
01:09:25.029 --> 01:09:37.909
So it would be interesting to see, like, for example, from your perspective, of you try the day star way, you come to the Discord, like talk through your ideas, and then say, No, Hotwir's right for me.
01:09:38.070 --> 01:09:44.150
That to me is more exciting because it's not about us being popular, it's more about what are we missing?
01:09:44.310 --> 01:09:51.670
Because it feels like we must be missing something because OpenClaw has 240 or 260,000 stars and it's complete garbage.
01:09:51.829 --> 01:09:55.989
Everyone knows it's garbage, and yet it's more popular than the Linux kernel.
01:09:56.150 --> 01:10:01.909
What are we doing as developers that this is you just need to get a bunch of bots to star your repo?
01:10:02.470 --> 01:10:03.510
Yeah, I'm just not gonna.
01:10:03.909 --> 01:10:04.390
There you go.
01:10:04.630 --> 01:10:05.590
I'm just too dumb.
01:10:05.750 --> 01:10:12.230
That's the problem, is like you know, there's different kinds of intelligence, and that's a kind of like marketing intelligence is I'm not good at so.
01:10:12.310 --> 01:10:20.710
But what we do need is people like you to say, no, really, we can be better than this, or not, or to say, no, it's good enough.
01:10:20.869 --> 01:10:23.750
So I'm in a weird spot where I like the size of our community.
01:10:23.909 --> 01:10:29.350
I can talk to everybody, I know everybody, but also there's so many people that are left to the wayside that don't know about it.
01:10:29.510 --> 01:10:30.630
It's a weird thing.
01:10:30.710 --> 01:10:40.069
I had a thing at work, like we have a bunch of projects that are now using Datastar, and it's so much faster, so much better for doing real-time stuff and do even doing normal crud stuff.
01:10:40.149 --> 01:10:41.350
Like, it's just better in every way.
01:10:41.510 --> 01:10:46.470
I work here, and it took me years of convincing people to like, hey, why don't we do this instead of React?
01:10:46.550 --> 01:10:46.949
Why don't we do that?
01:10:47.029 --> 01:10:49.029
Well, well, maybe for the next project, oh, maybe for this one.
01:10:49.189 --> 01:10:52.149
And now we have multiple things that are all in flight using it.
01:10:52.310 --> 01:10:56.869
The code is simpler, everything's simpler, it's faster, and we can work in the language of choice.
01:10:57.109 --> 01:11:02.550
So I've been actually looking forward to you either falling in love with it or completely denouncing it.
01:11:02.710 --> 01:11:03.909
Either of those sounds good to me.
01:11:04.069 --> 01:11:05.269
I'm good with either one.
01:11:05.430 --> 01:11:06.310
There's no ego there.
01:11:06.390 --> 01:11:11.750
It's like, please tell me I'm wrong here, and that hot wire and stimulus really is the way forward for Ruby.
01:11:11.909 --> 01:11:16.149
I would love to hear that because I like what Micah is on one of the people behind Hotwire.
01:11:16.310 --> 01:11:20.310
And he's done great work in there, but also I just think it's fundamentally flawed.
01:11:20.390 --> 01:11:23.590
Like the WebSocket thing sounds good, but when you get into the details, it's not good.
01:11:23.829 --> 01:11:31.189
There's all these things that are specifics that do matter that the average developer doesn't have to care about, but the person developing the framework does have to care about.
01:11:31.350 --> 01:11:36.069
So but yeah, I think it's just a death from a thousand cuts in the hot wire and stimulus.
01:11:36.229 --> 01:11:40.789
Can't wait to see what you can do when you take that away.
01:11:41.029 --> 01:11:41.510
Yeah.
01:11:41.750 --> 01:11:57.909
I'm very interested to get into the weeds of it and actually feel it either remove a pain point or add a pain point, or how it shifts my mental model when I'm thinking about I'm in the planning stages, I'm got this white board in front of me.
01:11:58.069 --> 01:11:59.909
I've got to go do the thing.
01:12:00.310 --> 01:12:02.229
Is datastar helping with that?
01:12:02.390 --> 01:12:03.670
Is it hurting with that?
01:12:03.989 --> 01:12:09.430
Do I need such a mental model shift that almost becomes not worth it?
01:12:09.670 --> 01:12:14.630
Sort of like learning Vim, where it's like, yeah, you'll eventually get faster, but it's gonna hurt.
01:12:14.949 --> 01:12:22.630
It's actually kind of like the Vim Emacs world, it's kind of Emacs is its own operating system, right?
01:12:22.789 --> 01:12:23.590
It literally is.
01:12:23.670 --> 01:12:25.989
It has its like own stack, basically.
01:12:26.149 --> 01:12:30.869
But so much stuff is built in that you kind of don't have to care unless you really want to get into the weeds.
01:12:31.350 --> 01:12:34.710
Data star kind of feels like that, that it's such a weird, like it's not the norm.
01:12:34.869 --> 01:12:38.229
Everything's just built in and you just kind of get things done and you just go about your business.
01:12:38.390 --> 01:12:43.510
It doesn't have the learning curve that you're used to, other than if you've never done CQRS or any of that stuff.
01:12:43.670 --> 01:12:49.109
But again, you don't have to do that to do Datastar, but if you embrace it, you'll see how much simpler your life can be.
01:12:49.269 --> 01:12:53.430
So the Tau definitely explains it out, but please join.
01:12:53.670 --> 01:12:56.470
Go on that journey
because I think that it would be really valuable.
01:12:56.630 --> 01:13:00.710
And you might even bring on people, other Rubyists that are using data star.
01:13:01.029 --> 01:13:02.229
We have the guy who does the SDK.
01:13:02.390 --> 01:13:11.590
There are Rubyists in the community, and it would be interesting to see why they came there as opposed to using like we already have people that came to Datastar from Ruby.
01:13:11.909 --> 01:13:13.109
Why did they do that?
01:13:13.269 --> 01:13:17.029
Like they'll probably have more deeper technical reasons than I do.
01:13:17.269 --> 01:13:22.949
My thing is like I just looked at Hotwire and looked at the details and went, this is doing too much and it's not doing enough at the same time.
01:13:23.269 --> 01:13:24.550
Which is what I felt with HTMX.
01:13:24.630 --> 01:13:25.909
HTMX is so much more complicated.
01:13:26.149 --> 01:13:30.229
Perfect example of this, because if people have done any kind of HTMX stuff, there's HXget.
01:13:30.789 --> 01:13:34.710
It goes, you give it a URL, it basically goes to that website, gives you back a thing.
01:13:34.869 --> 01:13:37.350
The problem is that that is easy.
01:13:37.510 --> 01:13:40.550
You just do HXget, you get your thing, and it updates that part of the page.
01:13:40.630 --> 01:13:40.949
Great.
01:13:41.109 --> 01:13:43.670
The problem is that's actually it's easy, but it's not simple.
01:13:43.829 --> 01:13:47.670
Because what it does is tying HXget to a click event.
01:13:47.829 --> 01:13:49.510
And it's like, but what if I don't want to be a click?
01:13:49.590 --> 01:13:50.310
What if I want to be a mouse?
01:13:50.630 --> 01:13:51.590
Oh, then you need this extra tag.
01:13:51.670 --> 01:14:01.029
Well, then you need this extra tag, and it becomes tag soup by you actually controlling it, whereas the data star way is much more composable, but you have to learn what those different pieces of those Legos are.
01:14:01.189 --> 01:14:03.670
So people are like, oh, it's not as simple.
01:14:03.829 --> 01:14:06.390
It's like, no, it's simpler, it's just not as easy.
01:14:06.550 --> 01:14:08.789
But the thing is, it's more extendable in a way.
01:14:09.029 --> 01:14:13.670
So the question to you is more do you like that?
01:14:13.750 --> 01:14:18.869
The thing is, even if you are have Legos, you can always write a monkey patch helper that like writes that Lego for you, right?
01:14:18.949 --> 01:14:26.710
Like if you find patterns that you're using, you build up the constructs that you need, not being only allowed to do things like HTMC.
01:14:26.949 --> 01:14:33.269
The other thing I will say that's very different from people that have tried HTMX or tried the hypermedia first approach in the past.
01:14:33.750 --> 01:14:41.350
I think one of the things that I completely disagree with on the HTMX side is that everything's basically request replier polling based, and you end up with a thousand routes.
01:14:41.510 --> 01:14:44.390
Like you end
up with so many routes for every little bit of the page.
01:14:44.550 --> 01:14:48.149
In the data store way, you usually end up with one connected stream and that's it.
01:14:48.229 --> 01:14:51.670
And you just send commands and posts like you normally would, and that's it.
01:14:51.909 --> 01:14:54.229
So it's just simpler because you don't need all that stuff.
01:14:54.310 --> 01:14:58.789
If you do the CQRS style and you keep connected, all that stuff goes away.
01:14:59.029 --> 01:15:02.949
So it's just simpler in every way, but yeah, it is a different mental model.
01:15:03.029 --> 01:15:05.269
But I would say join the Discord before you get into trouble.
01:15:05.510 --> 01:15:07.029
Join it and talk to the people.
01:15:07.269 --> 01:15:10.069
They will guide you in a way that there's time to go through the pain, right?
01:15:10.149 --> 01:15:15.750
Like doing the homework by hand makes sense, but you're already a professional developer, you already know Ruby, you don't already know this stuff.
01:15:15.829 --> 01:15:19.670
So don't go through the pain of saying, How would you do it in Datastar?
01:15:19.909 --> 01:15:23.430
At least start there and then like then have the conversation, is what I would say.
01:15:23.750 --> 01:15:24.069
Okay.
01:15:24.550 --> 01:15:25.109
Noted.
01:15:25.350 --> 01:15:25.670
All right.
01:15:25.750 --> 01:15:27.109
So last question.
01:15:27.829 --> 01:15:31.109
What's something cool, new, or interesting that you want to share?
01:15:31.350 --> 01:15:34.550
And I feel like you've mentioned it a few times already.
01:15:34.630 --> 01:15:37.029
If you want to go that route, you're tailwind killer.
01:15:37.109 --> 01:15:37.989
But it doesn't have to be that.
01:15:38.069 --> 01:15:45.989
It can be, I've had people talk about endangered hobbies and cloud brightening and books that I'm now addicted to.
01:15:46.229 --> 01:15:47.189
Sky's the limit.
01:15:47.269 --> 01:15:50.630
You pick, but you can tell us whatever you're kind of pumped about.
01:15:50.949 --> 01:15:55.350
I think I will talk about the two projects that I think are really are the rest of the answer to self and the web.
01:15:55.510 --> 01:16:03.430
But I will say I have just got my hands on a 1937 Atlas lathe that I'm in the middle of rebuilding in my shop.
01:16:03.989 --> 01:16:04.869
And that's really cool.
01:16:04.949 --> 01:16:06.229
It's cool to work on older equipment.
01:16:06.310 --> 01:16:10.310
I'm basically updating it to use like modern servo mortars and stuff like that.
01:16:10.550 --> 01:16:13.109
In the thread making, they only used to have inches, right?
01:16:13.189 --> 01:16:14.149
Because it's an older model.
01:16:14.470 --> 01:16:20.710
But I redoing it so that it has an electric gearbox so that it actually can do metric and power feeding and all that.
01:16:20.789 --> 01:16:24.229
So it's always good as developers to also build things with your hands, I think.
01:16:24.550 --> 01:16:25.989
Like it does give you a different outlook.
01:16:26.149 --> 01:16:29.590
So I'll say in my personal life, that's one of the things I'm working on now.
01:16:29.670 --> 01:16:34.069
But the things to solve the web, I basically have data star, which is done.
01:16:34.149 --> 01:16:39.510
But in Pro, there is two projects that I think are really changing the game in an interesting way.
01:16:39.670 --> 01:16:48.789
One of the things that I think is really like that's built into the browsers that people don't know that much about, or it's just a freaking hassle to work with, is Web Components.
01:16:49.029 --> 01:16:58.310
Web Components are a great idea of encapsulating state for JavaScript, but the interface that you do in them in them is just not fun.
01:16:58.470 --> 01:17:00.949
And the thing is, ironically, it's a bunch of JavaScript.
01:17:01.109 --> 01:17:06.069
You'd think something that's built for the web to make it a declarative element would be declarative.
01:17:06.229 --> 01:17:07.029
That's not how it works.
01:17:07.109 --> 01:17:10.710
It's just a bunch of classes, and like you have to export classes that extend HTML.
01:17:10.789 --> 01:17:13.109
Like the way you do it is, I think, a bit of a nightmare.
01:17:13.269 --> 01:17:19.510
So I have this project called Rocket that's inside of Pro that basically turned web components into declarative syntax.
01:17:19.670 --> 01:17:28.149
So you write things using Datastar like things, and then it does all the local scoping, does all the right things, automatically imports modules, does all the right things.
01:17:28.229 --> 01:17:29.269
You can go look at the website.
01:17:29.430 --> 01:17:35.829
But I think that that's a really exciting project because it's basically, and what's interesting, it is a single plugin in Datastar.
01:17:36.149 --> 01:17:42.789
So in one plugin in Datastar, which ironically is about the size of Datastar, it's around nine, 10 kilobytes alone.
01:17:43.269 --> 01:17:46.550
It's completely making web components declarative.
01:17:46.710 --> 01:17:50.390
And for most web components, that makes it super nice, it's super convenient.
01:17:50.550 --> 01:17:55.109
And also what's interesting is your components now just become literally template elements.
01:17:55.350 --> 01:17:59.189
Template element with data dash, rocket dash, and then the name of it, stuff like that.
01:17:59.269 --> 01:18:05.829
And you set up your props, it has an entire concept of I don't know if you know Zod, like all the validation on schema validation.
01:18:05.909 --> 01:18:08.229
Like there's TypeScript stuff for doing validation.
01:18:08.310 --> 01:18:09.989
That does this property have the right value?
01:18:10.149 --> 01:18:11.269
Is it min max?
01:18:11.350 --> 01:18:12.869
That kind of JSON schema stuff.
01:18:12.949 --> 01:18:13.829
So that's built in.
01:18:13.989 --> 01:18:16.789
It does auto imports of async modules.
01:18:16.869 --> 01:18:20.710
It does all this stuff out of the box that makes it so
nice to write declarative stuff.
01:18:20.869 --> 01:18:24.149
Like the thing that you're saying, well, I have this really complicated thing that's really hard.
01:18:24.390 --> 01:18:30.390
eCharts is this amazing JavaScript framework for doing charting, but it is really complicated setup.
01:18:30.550 --> 01:18:36.149
The Rocket component is like 200 lines, and normally it's like a thousand lines to get started.
01:18:36.229 --> 01:18:41.670
So like you have 200 lines, you get that done, and you just drop that on any page in any language, and it just works.
01:18:41.909 --> 01:18:45.189
So it simplifies the things that you have to interact with.
01:18:45.269 --> 01:18:51.989
It doesn't try to replace a 3js 3D model, but you can get a globe working in 3JS in like 20 lines.
01:18:52.149 --> 01:18:54.869
You can get a copy-paste button with zero lines of JavaScript.
01:18:55.029 --> 01:19:00.470
There's all these things that all of a sudden become you're using the knowledge that you learn on Datastar to then extend to doing web components.
01:19:00.550 --> 01:19:02.149
So I think that's a really neat project.
01:19:02.310 --> 01:19:05.430
And the other project I did is basically a thing called Stellar.
01:19:05.670 --> 01:19:21.989
What Stellar does is Tailwind was a great project for when it came out, in that it basically was saying SaaS and less have all these components and stuff, but really you end up making these utility classes, and over time you just add more and more.
01:19:22.229 --> 01:19:26.470
The way Tailwind was built makes sense at the time because CSS couldn't do very much, right?
01:19:26.630 --> 01:19:29.430
Like 10 years ago or even eight years ago when it came out.
01:19:29.670 --> 01:19:34.630
So uh the problem is that you end up with a class soup and it has to iterate through those homes.
01:19:34.789 --> 01:19:39.430
And then when you're actually sending data, half your data that you're sending down is actually classes.
01:19:39.590 --> 01:19:42.710
Like if you look at most projects, it's just class soup everywhere.
01:19:43.029 --> 01:19:48.550
So there's this interesting project for Adam Argyle from Google at the time was doing open props.
01:19:48.630 --> 01:19:56.149
And open props was like, I think the real value of Tailwind is the idea of the design system, but the interface you do with it is terrible.
01:19:56.390 --> 01:20:03.829
So what open props was doing is basically saying, here's a design system, all the things that Tailwind gives you, but it's using CSS variables.
01:20:04.149 --> 01:20:10.310
And the thing is, a lot of times, all the things it did with all the nesting and stuff, you can now do CSS nesting natively.
01:20:10.390 --> 01:20:14.069
You can do where clauses, you can do these mixes, like there's all these things that are built into the browser now.
01:20:14.149 --> 01:20:21.029
So the Adam Arngard was doing was saying, hey, you can just use CSS with this nice design system in your CSS and call it a
day.
01:20:21.189 --> 01:20:24.310
The problem is it's his design system.
01:20:24.550 --> 01:20:32.229
So as soon as you want to do anything interactive or say, hey, I need he has width one through 10, but what if I need 11 or 12?
01:20:32.310 --> 01:20:33.189
Now I'm hand rolling it.
01:20:33.269 --> 01:20:36.069
Now I'm like, it's a good starting place, but now you're starting to do stuff by hand.
01:20:36.390 --> 01:20:41.350
I come from a parametric background where doing CAD and CAM where everything's constraint based.
01:20:41.430 --> 01:20:44.710
So if you change this one variable and it's a multiplication, like on the relationships, right?
01:20:44.789 --> 01:20:55.029
It's all about so Stellar CSS is taking the idea of open props times a thousand and basically making every single thing in the entire project parametric in its nature.
01:20:55.189 --> 01:21:06.229
So you say, This is my size when it's a min, this is my max, this is the way that the multipliers work, and you just play around with the editor and it's live updating the UI elements on the fly.
01:21:06.390 --> 01:21:12.069
So we have a video that came out that I can send you a link to, but the idea is that you're basically making it completely dynamic.
01:21:12.149 --> 01:21:20.390
As you make so it'd be the equivalent of like in Tailwind, if you're changing your config, imagine if it was real-time updating your website live as you were changing your editor.
01:21:20.869 --> 01:21:34.229
Like, so it's not only like you make a couple tweaks saying, hey, I want steps one through 20, and I want them to be on this kind of shift and this kind of hue colors thing, and it automatically updated your site live because again, it's all data star under the hood.
01:21:34.390 --> 01:21:36.310
So it can live update your page.
01:21:36.550 --> 01:21:49.189
Now all of a sudden, because it's collaborative first, means that you could share that site with someone else and actually be with a client playing with the CSS live, editing your updates, and now sharing and being on the same page across everything.
01:21:49.350 --> 01:21:53.989
So it's basically collaborative design elements on the fly.
01:21:54.310 --> 01:21:54.710
Nice.
01:21:55.269 --> 01:21:57.750
It's a really interesting project, and it's one of those things.
01:21:57.829 --> 01:22:00.229
I'll send you a link so you can look at the video and then we can have our discussion.
01:22:00.310 --> 01:22:04.710
I feel like it's one of those things it's almost better to come from you trying to explain it to an audience than me.
01:22:04.869 --> 01:22:05.670
I'm too deep in it.
01:22:05.750 --> 01:22:06.390
It's hard for me to explain.
01:22:06.630 --> 01:22:07.350
Yeah, yeah, yeah, yeah, yeah.
01:22:07.430 --> 01:22:07.750
I get that.
01:22:07.989 --> 01:22:18.470
I'm doing a bad job at explaining it, but it's really, really neat in that even if you did all of the like in its default position, I think it creates like 1200 variables for you.
01:22:18.550 --> 01:22:19.909
Like it does all kinds of crazy stuff.
01:22:20.069 --> 01:22:24.470
But the thing is it ends up being like 12k, and it's a one-time cost ever.
01:22:25.029 --> 01:22:30.229
And now those are available to your site and it's cached and it's easily available, and you can always trim it down from there.
01:22:30.550 --> 01:22:45.750
But there's something beautiful about like, here's my design system, and now I'm using CSS as CSS was intended with all the container queries and all, because a lot of things with the container queries in Tailwind, it gets so confusing, and it to me it's almost like a write-only thing where you write it out, you're like, cool, this works.
01:22:45.829 --> 01:22:48.710
And if you make a change, you almost start over and you start writing it again.
01:22:49.029 --> 01:22:54.069
Whereas this style, you're actually using CSS as intended with its nesting and its semantic styles and stuff.
01:22:54.149 --> 01:22:55.909
So there's almost nothing that gets sent on the page.
01:22:56.069 --> 01:23:00.390
You know how if you do Tailwind typography, you get nice styles out of the box.
01:23:00.710 --> 01:23:05.269
You're like, cool, I get my nice thing, and I just do semantic stuff like markdown or something in in there.
01:23:05.510 --> 01:23:08.069
Imagine if your entire website worked that way.
01:23:08.390 --> 01:23:10.310
So that's what I'm moving towards.
01:23:10.470 --> 01:23:12.069
We just did the first initial release.
01:23:12.149 --> 01:23:14.470
I'm about to do 0.02.
01:23:14.869 --> 01:23:16.789
It probably will come out today or tomorrow.
01:23:16.869 --> 01:23:21.029
But yeah, I'm I'm excited about that, and I'm excited for you to try it and see what you think.
01:23:21.350 --> 01:23:23.269
Yeah, I'm excited to give it a try too.
01:23:23.350 --> 01:23:24.869
And and especially Data Star.
01:23:25.189 --> 01:23:29.189
It is one of the things that we're like Well, it seems like it could be.
01:23:29.670 --> 01:23:37.109
In some ways, it feels very different, in some ways it's like, oh yeah, it's like going back and building your very simple website that can actually do shit.
01:23:37.590 --> 01:23:41.750
Imagine doing shit, but also being real-time collaborative out of the box.
01:23:41.909 --> 01:23:52.149
One of the things that was really like we had someone from the HTMX community come in and he does a lot of stuff with HTMX, and his hello world in Datastar was building Google Wave.
01:23:52.390 --> 01:23:53.829
That was his hello world.
01:23:54.310 --> 01:23:55.510
He just built it from screen.
01:23:55.750 --> 01:24:02.229
Like he's like, oh, I'm just gonna keep going with this because he's basically building a chat app is maybe 15-20 minutes.
01:24:02.550 --> 01:24:03.029
Wow.
01:24:03.350 --> 01:24:05.909
A hello world is a full reactive chat app.
01:24:06.069 --> 01:24:09.750
The hey equivalent stuff, like you could do something like that in minutes.
01:24:09.989 -->
01:24:14.550
So the question is like, if that's a hello world, what does like an actual product look like?
01:24:14.789 --> 01:24:17.269
I can't wait for you to join the community and like start.
01:24:17.670 --> 01:24:22.550
Someone needs to tell me I'm wrong because it's no way that I can be right for this long.
01:24:22.949 --> 01:24:24.470
That feels weird in tech, right?
01:24:24.550 --> 01:24:31.430
Like to be like someone proved me wrong, bro, and like no JavaScript framework author will wants to compete with it, kind of thing.
01:24:31.750 --> 01:24:32.710
It's a weird thing.
01:24:33.029 --> 01:24:34.390
Yeah, challenge accepted.
01:24:34.470 --> 01:24:35.909
I will definitely be putting it.
01:24:36.069 --> 01:24:36.470
What's your project?
01:24:36.789 --> 01:24:38.949
What are you gonna what are you what are you gonna what are you gonna build?
01:24:39.269 --> 01:24:43.590
To get my feet wet, I'm gonna do a to-do app because that's what everyone does.
01:24:43.829 --> 01:24:52.630
But there's a few painful parts of our app at work that lean on React because they are very reactive.
01:24:52.789 --> 01:25:13.350
It's extremely the client does stuff and they need to see immediate feedback and that round trip that you need for doing it the hot wire way, isn't the level of fidelity isn't quite there, but React solves that for us with the way that we have it, but no one likes working on it because it's fucking React.
01:25:13.670 --> 01:25:19.430
And I just kind of have this feeling that Datastar will be an excellent replacement for it.
01:25:19.510 --> 01:25:21.029
So I might take that.
01:25:21.269 --> 01:25:23.350
Do you already have an event bus kind of for your system?
01:25:23.430 --> 01:25:25.109
Like, is that already built in?
01:25:25.590 --> 01:25:27.909
Sort of, sort of, okay, sort of, yeah.
01:25:28.149 --> 01:25:32.149
The thing is, we have literally a to-do MVC as part of our built-in stuff.
01:25:32.229 --> 01:25:41.750
I'm happy to send you that code or work through it with you of like explaining because it's in Go, but the ideas of like the actual update and like how it works is very different than most to-do apps.
01:25:41.829 --> 01:25:47.109
Like when you have time, let's go through it and I can show you the Go code and show you how it works on the site.
01:25:47.269 --> 01:25:56.710
And like let's have a conversation about it because I think you might go, oh, because it's in Go, which is not the most terse language, it's like a hundred lines of code.
01:25:56.869 --> 01:25:57.109
Okay.
01:25:57.510 --> 01:26:00.630
So the entire to-do, like the to-do MVC is a hundred lines-ish.
01:26:00.869 --> 01:26:01.829
It's called in Go.
01:26:02.069 --> 01:26:13.989
It's just simpler because once you look at it, because basically, for a to-do app, you basically have in that version, you get the main page, you get kind of the skeleton of the page that also has the rendered contents of the to-do app.
01:26:14.390 --> 01:26:20.310
And then in there it's a data init and then an at get, which basically says to a slash update.
01:26:20.390 --> 01:26:22.949
So it goes to that same endpoint and gets the slash updates.
01:26:23.109 --> 01:26:24.550
So now you have a direct connection.
01:26:24.710 --> 01:26:28.550
So everything else is just a command to like do this, do that, do this.
01:26:29.109 --> 01:26:35.510
That one connection is the only thing that stays open, and then as it updates the changes, it then sent back directly.
01:26:35.670 --> 01:26:39.590
So it doesn't matter if you change it from there or from the event bus or from disk.
01:26:39.829 --> 01:26:43.029
If you make a change to the disk automatically, like all this stuff happens natively.
01:26:43.189 --> 01:26:51.350
So I might need to show you that because I think it might you might be able to be a Rosetta Stone of Delaney's crazy pointing, like for people that are listening.
01:26:51.430 --> 01:26:53.430
I'm just pointing into the sky.
01:26:53.829 --> 01:27:00.310
It's that always sunny in Philadelphia meme where the one character Charlie's like pointing at the board and like he looks completely crazy.
01:27:01.989 --> 01:27:03.989
But he's making sense, yeah.
01:27:04.229 --> 01:27:06.149
And then what's funny is like who is this person?
01:27:06.229 --> 01:27:08.869
Like, they've all been looking for their mail the whole time.
01:27:09.109 --> 01:27:12.149
Like, there is no conspiracy, everyone's been waiting on their mail.
01:27:12.310 --> 01:27:21.269
So that's what it's gonna kind of feel like is that I'm gonna do all this pointing, and you're gonna go like, okay, so I just have to set up an event stream and subscribe to one thing in one place.
01:27:21.430 --> 01:27:22.310
That's it, yeah.
01:27:22.550 --> 01:27:23.590
Yeah, yeah.
01:27:23.829 --> 01:27:26.630
There's no conspiracy here, there's no grand conspiracy.
01:27:26.869 --> 01:27:30.149
Mac was right, that's a hundred percent the thing.
01:27:30.470 --> 01:27:31.430
Okay, yeah.
01:27:31.590 --> 01:27:37.590
So, yeah, we'll probably should do that offline, but I think you're gonna be shocked.
01:27:37.750 --> 01:27:51.590
I know actually, what would be really interesting is I would love to take the to-do one that we have on the website, because it's go, is a verbose language, and say, can we get this under X amount of lines in the Ruby style or the Rails style?
01:27:51.670 --> 01:27:55.510
Like, how small is a to-do NBC in Datastar?
01:27:56.069 --> 01:28:00.149
Because I think you could play some code golf there and be kind of shocked at how small it can be.
01:28:00.470 --> 01:28:00.789
Okay.
01:28:00.949 --> 01:28:03.670
Yeah, I like code golf, especially in Ruby.
01:28:03.829 --> 01:28:04.229
Awesome.
01:28:04.310 --> 01:28:09.189
Yeah, well, I mean, hey, thanks for coming on the show and talking about Datastar and like going through everything.
01:28:09.269 --> 01:28:10.869
It's pretty exciting project.
01:28:11.029 --> 01:28:21.989
I'm
really pumped to check it out and actually play with it because I think that will be the big difference between like, wow, conceptually this sounds awesome, but what does it actually feel like?
01:28:22.149 --> 01:28:24.630
That's the part I'm very much looking forward to now.
01:28:24.869 --> 01:28:30.069
Well, and I'm looking forward to seeing where there's no reason why we aren't bigger in the Ruby community.
01:28:30.149 --> 01:28:32.390
There's literally like no technical reason why we aren't.
01:28:32.550 --> 01:28:39.750
So I can't wait for you to show us what we're missing, or like you become a cultist and now you're spreading the good word.
01:28:39.989 --> 01:28:45.029
Or we'll get you your white shirt and the black tie and a book of data stuff.
01:28:45.430 --> 01:28:48.390
I've listened I already am a cultist for Dungeon Crawler Carl.
01:28:48.470 --> 01:28:49.510
I don't know if I can take on a couple of things.
01:28:49.670 --> 01:28:49.989
You too?
01:28:50.229 --> 01:28:50.949
Okay, dude.
01:28:51.350 --> 01:28:53.909
The thing I haven't read the new one's coming out pretty soon.
01:28:54.069 --> 01:28:57.909
It's kind of going off the rails a little bit, but I have to say it's so good.
01:28:58.229 --> 01:28:59.989
Have you done The Wandering Inn?
01:29:00.310 --> 01:29:00.630
No.
01:29:01.189 --> 01:29:04.229
You are a Dungeon Crawler fan, but you don't know about The Wandering Inn.
01:29:04.390 --> 01:29:04.630
No.
01:29:04.869 --> 01:29:16.550
The Wandering Inn is the longest book series ever written, and it's by some young gal, and it has more words, I think, than Stephen King and the Oh, Terry Pratchett?
01:29:16.789 --> 01:29:17.510
Uh, Flatlighter?
01:29:17.670 --> 01:29:17.909
Yeah, yeah.
01:29:18.229 --> 01:29:21.829
She's written more than Terry Pratchett and Stephen King, and she's like now in her 30s.
01:29:21.909 --> 01:29:22.390
It's amazing.
01:29:22.630 --> 01:29:22.949
Oh shit.
01:29:23.109 --> 01:29:28.710
It's like the audiobooks are way behind, and it's on book like 17, and each book is like 60 hours.
01:29:29.269 --> 01:29:36.630
The first book, so I will say, you know how for Dungeon Carl Carl, the first one, it's good, but it's a slow burn, and then it gets it starts going.
01:29:36.869 --> 01:29:37.189
Sure.
01:29:37.430 --> 01:29:41.510
Read the first book of Wandering In, and then tell me you don't love it.
01:29:41.750 --> 01:29:43.269
You gotta do the full whole book.
01:29:43.750 --> 01:29:46.869
At first, you're like, they drop the girl in like an RPG world kind of thing.
01:29:47.269 --> 01:29:48.069
Sure, it loves me.
01:29:48.149 --> 01:29:48.229
Yeah.
01:29:48.550 --> 01:29:48.710
Yeah.
01:29:48.869 --> 01:29:53.510
But the thing is, by the end of the book, if you're not like, oh, okay, this is not the book I thought it was.
01:29:53.750 --> 01:29:54.949
Let me know because yeah.
01:29:55.109 --> 01:29:57.430
If you like Carl, you you should like that.
01:29:57.829 --> 01:29:59.430
I love me, Dungeon Crawler Carl.
01:29:59.590 --> 01:30:03.350
Everyone at work is sick of me talking about Dungeon Crawler Carl.
01:30:03.510 --> 01:30:03.750
Yeah.
01:30:04.149 --> 01:30:04.550
My wife.
01:30:05.029 --> 01:30:07.750
Is sick of me talking about Dungeon Crawler Carl.
01:30:07.989 --> 01:30:10.390
See, that's where we just I just don't tell anybody about it.
01:30:10.550 --> 01:30:16.949
Um Team Donuts, so donut holes or Princess Posse?
01:30:17.750 --> 01:30:19.510
Depends on which talk show I'm on.
01:30:19.989 --> 01:30:21.590
Okay, fair, fair.
01:30:21.989 --> 01:30:22.550
Very nice.
01:30:23.029 --> 01:30:24.869
Try to play the audience, so okay.
01:30:25.029 --> 01:30:25.670
Alright, good.
01:30:26.149 --> 01:30:27.029
I do like the fish people.
01:30:27.109 --> 01:30:27.909
I forget what they called.
01:30:28.390 --> 01:30:29.109
The quietine.
01:30:29.189 --> 01:30:29.829
Yeah, cuitine.
01:30:29.909 --> 01:30:30.229
That's it.
01:30:30.310 --> 01:30:30.390
Yeah.
01:30:30.630 --> 01:30:32.069
I thought the whole thing was kind of interesting.
01:30:32.149 --> 01:30:34.470
So I don't know where it's gonna go from here, though.
01:30:34.550 --> 01:30:35.510
It's every one of them.
01:30:36.069 --> 01:30:38.630
It gets more and more chaotic, and I love it.
01:30:38.869 --> 01:30:43.829
Yeah, I feel like they need like a respite of some kind because it's gotten a little kooky.
01:30:44.630 --> 01:30:50.310
I mean, it's it's ramping up because I mean Matt Dinneman, the author, has said he wants to do 10 books.
01:30:50.550 --> 01:30:52.069
Eight is about to happen.
01:30:52.229 --> 01:30:52.390
Yeah.
01:30:52.470 --> 01:31:00.789
So he's running out of space to finish which have you read his the one he did before he did Dungeon Curl Card?
01:31:00.869 --> 01:31:03.510
The kaiju uh Battlefield Surgeon, yeah.
01:31:03.590 --> 01:31:05.029
Yeah, that was it.
01:31:05.109 --> 01:31:05.989
It's not finished.
01:31:06.069 --> 01:31:08.710
I'm wrapping up Operation Bounce House's newest book.
01:31:09.029 --> 01:31:11.750
So yeah, that book is a rough read.
01:31:11.989 --> 01:31:13.590
It's better by the end.
01:31:13.829 --> 01:31:16.310
So it's another one of those kind of like wandering in.
01:31:16.470 --> 01:31:22.789
Like if you don't get to the end and go, Battlefield Surgeon is a tough read, but at the same time, like you get to the end and go, okay, that was a well-written book.
01:31:22.869 --> 01:31:24.390
I feel like that's the way Wandering Inn is.
01:31:24.470 --> 01:31:28.710
By the time you get to the first book, if you're not like, okay, this has a voice.
01:31:28.949 --> 01:31:29.269
Nice.
01:31:29.430 --> 01:31:30.789
Um, so yeah, highly recommend.
01:31:31.029 --> 01:31:31.350
It's funny.
01:31:31.430 --> 01:31:33.350
We'll talk more about this for the next two hours or two.
01:31:33.590 --> 01:31:36.630
Yeah, just don't get me started on what I just did.
01:31:36.789 --> 01:31:37.909
Yeah, oh boy.
01:31:38.149 --> 01:31:44.069
Okay, we're gonna cut it off here then, because otherwise, this will become my longest episode ever.
01:31:44.550 --> 01:31:47.029
Again, seriously, thank you for coming on and talking about it.
01:31:47.430 --> 01:31:48.630
Excited for giving it a try.
01:31:48.710 --> 01:31:55.430
And once I do play with it, can totally have you back on and have a completely different context for the conversation.
01:31:55.670 --> 01:32:01.829
And if anybody listening is interested in trying, I'll have links to the Discord and links to the guides.
01:32:02.550 --> 01:32:07.909
So you've got a good ingress into exploring this brave new world of Data Star.
01:32:08.550 --> 01:32:10.710
And Delaney, thanks for coming on.
01:32:10.869 --> 01:32:11.670
Hey, thank you.
01:32:11.829 --> 01:32:12.710
This is a blast.
01:32:12.869 --> 01:32:14.949
I can't wait to see either that I'm right or wrong.
01:32:15.109 --> 01:32:15.989
Either way is gonna be great.
01:32:16.069 --> 01:32:17.350
So I'm gonna be great.
01:32:17.750 --> 01:32:20.069
Either way, I want to come on and tell me how bad it is.
01:32:20.310 --> 01:32:21.829
That would be almost more fun.
01:32:21.989 --> 01:32:23.269
So almost.
01:32:23.430 --> 01:32:24.229
We'll find out.
01:32:25.109 --> 01:32:25.909
All right, everyone.
01:32:26.069 --> 01:32:28.390
Yeah, I'll see you all in the next episode.
01:32:28.550 --> 01:32:29.430
All right, bye.