text stringlengths 0 2.02k |
|---|
[4087.58 --> 4093.90] So if there's a future then for Dino, a place of competition might be with Deploy. |
[4094.04 --> 4103.14] Because if you claim here now that you intend for Dino Deploy to be the best way to run a Dino application, then that might be the way. |
[4103.24 --> 4104.96] If Dino wins like Node has won. |
[4104.96 --> 4113.80] And, you know, we haven't asked you if you plan for, I assume so, but if you plan for Dino to take over what Node is, to replace Node particularly. |
[4114.26 --> 4124.34] But if it becomes as big as Node has become and as usable as Node has become, then, you know, that's the place to compete with you would be on the deploy. |
[4125.56 --> 4126.50] I guess. |
[4126.68 --> 4128.24] I'm not sure what you're asking actually. |
[4128.72 --> 4133.76] Well, to deploy, you know, similar maybe for, you know, there's some examples for WordPress, for example. |
[4133.76 --> 4138.22] Like there's particular hosts that are like amazing at hosting WordPress. |
[4138.98 --> 4147.14] If Dino wins, it becomes very popular to gain market share, to have a commercially viable application or a company or a SaaS product. |
[4147.26 --> 4151.22] You might want to compete with you all to host Dino applications. |
[4152.04 --> 4152.14] Yeah. |
[4152.22 --> 4157.90] I mean, would encourage anybody who wants to also be running a Dino service. |
[4158.08 --> 4158.44] Yeah, sure. |
[4158.58 --> 4160.94] Ultimately, that's good for the ecosystem anyways. |
[4160.94 --> 4168.32] And, you know, Dino, the company, probably pretty good competitor when it comes to running Dino in these different contexts, right? |
[4168.78 --> 4170.94] So I think I would assume you're welcoming competition. |
[4171.28 --> 4171.36] Yeah. |
[4171.48 --> 4176.94] And, you know, by the way, we're investing a lot in kind of this Rust JavaScript infrastructure. |
[4176.94 --> 4187.86] And so, you know, when you go out and see products that are kind of serverless products that execute JavaScript and don't look like extremely node-y. |
[4188.14 --> 4190.28] So, you know, a lot of this stuff is actually node. |
[4190.74 --> 4192.94] But kind of newer server-side JavaScript APIs. |
[4194.16 --> 4194.88] Yeah, look carefully. |
[4195.02 --> 4198.88] It may actually be Dino or one of its kind of lower layers of crates. |
[4199.26 --> 4199.28] Yeah. |
[4199.28 --> 4202.38] We expect that and we encourage that. |
[4202.66 --> 4204.48] Yeah, this helps the ecosystem. |
[4204.84 --> 4208.72] Take me back to Dino Deploy for a second, just like thinking through it as an end user. |
[4209.14 --> 4215.70] And it seems like a lot of these serverless solutions don't have like the database story. |
[4215.90 --> 4221.88] When it comes to my backend, if I'm going to run all my code, my dynamic website at the edge, |
[4221.88 --> 4225.90] but my database isn't co-located with those edge nodes. |
[4226.32 --> 4231.20] It's like in New York City running on a Postgres server or whatever. |
[4231.48 --> 4235.76] It kind of defeats a lot of the advantages of having that locality of that runtime. |
[4235.76 --> 4239.26] Because most backends aren't just doing mere math. |
[4239.74 --> 4243.10] You know, they're like, yeah, there's some data stored in some place and they're going to go hit the database |
[4243.10 --> 4245.64] and they're going to figure it out and they're going to put stuff in, take stuff out. |
[4245.64 --> 4250.72] But is there anything with Dino Deploy that like co-locates a database or makes it so that |
[4250.72 --> 4254.82] my Dino backend has all the things it needs right there with it? |
[4255.54 --> 4255.88] Not yet. |
[4256.02 --> 4260.24] You certainly see Cloudflare going in this direction with durable objects. |
[4261.12 --> 4268.80] So, you know, right now Dino Deploy is kind of this, I would consider kind of the minimal viable product, |
[4269.08 --> 4271.00] which is that it responds to requests. |
[4271.00 --> 4271.40] There you go. |
[4271.42 --> 4273.82] So you can send back a response. |
[4273.82 --> 4275.56] You can make outbound requests. |
[4275.56 --> 4280.76] So, you know, let's say you have a Firebase database hosted by Google somewhere. |
[4281.30 --> 4285.32] You can make outbound requests to that data store for any persistent needs. |
[4285.66 --> 4290.16] We've basically pushed the persistence problem out of our problem space at the moment. |
[4290.66 --> 4292.36] And, you know, there are problems. |
[4292.62 --> 4299.36] Sometimes you just want a little redirect server and there's no need to have persistence in some applications. |
[4299.62 --> 4302.22] Obviously, many applications need persistence. |
[4302.22 --> 4308.90] And this is one of several features that we're looking at in kind of the coming months. |
[4308.90 --> 4309.34] Cool. |
[4310.02 --> 4314.16] So what happened with Node last time around, I referred to it earlier with Michael Rogers' reference, |
[4314.36 --> 4317.24] was that there was a lot of opportunity in the early days. |
[4317.84 --> 4327.92] And a lot of people jumped in and became influential, impactful JavaScript people because they helped out with the early days of Node. |
[4327.92 --> 4333.60] And this is potentially a new opportunity with this new round with Dino, where it's early days. |
[4333.68 --> 4336.16] You have core team. |
[4336.32 --> 4337.82] You have people doing stuff. |
[4338.34 --> 4339.26] There's a standard library. |
[4339.34 --> 4343.16] There's a lot more stuff that Dino has, I think, than that Node had when it first began. |
[4343.26 --> 4347.86] But the question is, if I'm a developer, I'm an open source person, and I'm thinking, you know what? |
[4347.90 --> 4350.46] I'm going to take a bet on Dino as an ecosystem. |
[4350.46 --> 4352.38] And I would love to be impactful. |
[4352.60 --> 4355.96] I would love to help out in ways that are big. |
[4356.38 --> 4357.28] What's the best way? |
[4357.48 --> 4364.84] What's the easy stuff, low-hanging fruit, or the real fertile ground for getting involved and being impactful with your code in the Dino ecosystem? |
[4365.62 --> 4372.40] I think the standard library is, we haven't talked about this that much, but in Node, there is no standard library. |
[4372.56 --> 4375.00] There's a lot of utilities built into Node itself. |
[4375.00 --> 4387.38] But part of the Node dependency problem is that when you just want a small little utility, when you want to left pad your string or whatever, you have to end up pulling in a third-party dependency. |
[4388.14 --> 4393.28] And in Dino, what we're doing is collecting all of the main useful things. |
[4393.48 --> 4399.14] And it's a bit ambiguous which things should be considered part of the standard library and which things shouldn't be. |
[4399.28 --> 4403.42] But in general, if a lot of people need those utilities, we put them in there. |
[4403.42 --> 4405.26] That's a very nice way to contribute. |
[4405.60 --> 4406.50] We have a style guide. |
[4406.64 --> 4407.36] We have tests. |
[4407.84 --> 4410.32] You know, it's something that affects the entire community. |
[4410.58 --> 4417.76] So if people contribute modules to the standard library, and obviously, people should ask first before randomly contributing things. |
[4417.88 --> 4421.88] It would be unfortunate if you did a bunch of work, and then we have to reject it for some reason. |
[4421.90 --> 4422.44] Right, where do you ask? |
[4422.50 --> 4426.26] This is a very useful way to be very useful in the Dino community. |
[4426.56 --> 4427.66] Where do those questions go? |
[4427.74 --> 4428.88] Is it issues on repos? |
[4428.94 --> 4429.90] Is it mailing list? |
[4429.90 --> 4434.60] Yeah, there's a Dino underscore STD repo on GitHub. |
[4435.34 --> 4438.18] And yeah, just open an issue and discuss it. |
[4438.54 --> 4443.66] But yeah, generally, we're very open to adding new libraries in the STD. |
[4444.00 --> 4445.36] Is the STD in Rust also? |
[4445.50 --> 4447.00] Or is that in TypeScript or JavaScript? |
[4447.56 --> 4448.26] That's in TypeScript. |
[4448.60 --> 4451.16] Yeah, these are utilities built on top of Dino. |
[4451.16 --> 4460.22] So obviously, you know, if people know Rust and want to kind of get into the internal system of Dino, there's a whole world there to explore. |
[4460.48 --> 4461.78] But that's a bit deeper. |
[4462.36 --> 4463.32] We have a Discord. |
[4463.68 --> 4464.72] You know, it's very active. |
[4465.10 --> 4468.04] And there's a lot of channels where people are discussing new ideas. |
[4468.42 --> 4473.20] And so I would encourage anybody to jump on there and hit me up with any ideas. |
[4473.20 --> 4480.98] Are there any particular applications out there currently leveraging Dino that you want to call out or that you've been impressed by? |
[4481.96 --> 4482.82] No, actually. |
[4483.96 --> 4487.20] Still early days? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.