Dev Agrawal

Пікірлер

@riongull Күн бұрын

Great presentation, Dev. Thanks. Solid is a very exciting framework.

@JLarky 4 күн бұрын

Did you manage to catch your flight?

@devagr 4 күн бұрын

I did, TSA was pretty quick

@Nobody-eg4bi 19 күн бұрын

Nest.js is not that easy to use, it is more for enterprise than to small projects. I prefer more Fastify for projects on the backend

@ismailhossain964 26 күн бұрын

I thought you eating something

@mehdi-vl5nn 27 күн бұрын

i'm not sure about stateful comment u made tho what do u do - a task broker ?

@Nothank1997 Ай бұрын

Two years later, this really helped me understand that SSR doesn’t mean that nextjs is a backend technology :( ORMs like prisma really got me confused lol

@donnybystrom Ай бұрын

Yes you can. You can also hammer a nail with a drinking glass.

@Guru-mf3ew 2 ай бұрын

I think that good parts from old monolithic architecture and jamstack are combined to make a good ux and that's what users care about and companies want to deliver so in the end users won

@snatvb 2 ай бұрын

wow, this is really cool

@kevenrodriguesmeirelles2241 2 ай бұрын

I love solid, my wish is it to evolve bigger as the react ecosystem

@fananolife 2 ай бұрын

Cool

@salman0ansari 2 ай бұрын

this is so fcking cool and i hate react even more now.

@davidsiewert8649 2 ай бұрын

Would love a more in depth info of that the library does under the hood and that data is transferred. You would not want to write a banking app that transmits the entire balance data of all users and only filter the relevant bits client side. I would like to see how you can control that gets send on the server.

@devagr 2 ай бұрын

Definitely The goal is to minimize the messages sent around as much as possible. One of the benefits of using Solidjs is that we get fine grained reactivity, which means messages are only sent across when needed

@11WicToR11 2 ай бұрын

please tell me we gonna have this in nextjs

@devagr 2 ай бұрын

We might

@muhammadfawwad6782 2 ай бұрын

really, thats sooo soo much amazing

@a.anvarbekov 2 ай бұрын

whaaaat!

@ctpaintball4life 2 ай бұрын

createClientEventLog should be called createClientEventReducer and it’s 2nd argument should be the reducer. createEventProjection is just extra API

@devagr 2 ай бұрын

One is immutable, the other is mutable. There is a difference, we need two apis

@ctpaintball4life 2 ай бұрын

This is so fucking wild. Been waiting for this

@jocdiazm 2 ай бұрын

In my head this is called Solid Party 🥳

@devagr 2 ай бұрын

@@jocdiazm everything really is better with friends

@saikk5710 2 ай бұрын

You could write a global /init API that automatically does user initialisation processes when they are using the app for the first time. With your example, it might take a small portion of time to resolve all those stuff. Additionally, things you mentioned may be some examples, you might have some complex initialisation processes, which will not work out with the /init API concept.

@chrislatorres 2 ай бұрын

Deleting these tables for good is such a good value proposition.

@hosseinnajafi2181 2 ай бұрын

Greate video, thank you 🙏

@clashingtv2527 2 ай бұрын

nice explain

@MengLinMaker 3 ай бұрын

The biggest problem with SSR is sacrificing offline experience. So React query definitely has a future, especially for apps that still needs to work offline.

@nathangwyn6098 3 ай бұрын

Chopsticks to hold your mic.... okay

@KrishnaDasPC 4 ай бұрын

please avoid crappy music

@SachinWakpaijan 4 ай бұрын

You can use both. It doesn't matter

@raveena.sharma 4 ай бұрын

Can we use Django + React + Nextjs for building a KMS with bi-directional linking + advanced searches at the front end while saving data at the backend?

@Nobody-eg4bi 19 күн бұрын

you can use Django, Nextjs, Prisma with Mongodb or Postgres but if performance critical i will go with Fastify than Django.

@raveena.sharma 19 күн бұрын

@@Nobody-eg4bi Thanks

@sourabhsingh4515 4 ай бұрын

Well after the release of bun and hono this suggestion and video is completely useless. Sorry but appreciate your talent to find this problem back at that time.

@devagr 4 ай бұрын

Hono and Nest are not really the same Nest has a much bigger scope than just a "web" framework. It's much more of a modular framework with web as one of the possible entry points. If you think Hono is a full replacement for Nest I recommend looking into Nest a bit more closely

@sourabhsingh4515 4 ай бұрын

@@devagrI was talking about this video not nest js please don't misunderstand me the things you have said in this video all of those things can be done greatly by hono Nest js capabilities are way larger than the use cases you described in this video and to build such a simple application Hono can easily do the work without getting into more complexity like Nest js will require.

@prakhargdev 4 ай бұрын

Your explaination was great man helped me clear all doubts

@kunwarfk 4 ай бұрын

Love your content! But this music makes it really hard to concentrate. You can do great without the music.

@prathamsinghal5261 4 ай бұрын

The background music is quite distracting and annoying.

@FazedSoul 4 ай бұрын

That's why he is wearing headphones. LoL

@hithaishig9670 5 ай бұрын

I just got carried away, watched the entire video and this is the first time I'm commenting on KZbin. Pure perfection, throughout the video! hats off senor 🧢

@sharath-o5b 5 ай бұрын

why are you using those chop sticks

@devagr 5 ай бұрын

couldn't find the fork

@hakanaki 5 ай бұрын

People say NextJs is an MVC framework. What are your thoughts?

@engelshentenawy 5 ай бұрын

Turn off the music bro, it's quit distracting. thanks.

@devilishsoul1601 6 ай бұрын

Still gonna subscribe you bruh

@devilishsoul1601 6 ай бұрын

I swear that fake accent is 🤌🏻🤌🏻😂

@fillipeamg5877 6 ай бұрын

I wish he didn't hold the mic like this

@devagr 6 ай бұрын

keep wishing

@Cameron-hs5ry 6 ай бұрын

I saw the Theo vid on Next and tried it out, the idea of being able to just await fetch inside my components sounded nice since I was new to React and was working to convert my node js CLI project to have a proper UI. Then I learned what stateless actually means when I spent a few hours debugging why a bunch of Classes that get instantiated in Request 1 are undefined when running Request 2.... I just feel like if your requests are anything beyond basic crud operations with a high need for static generation then next will be more trouble than its worth