please no

[landsman]

This is a really bad idea for many reasons. Please stop when you can.

[TechyAditya]

What are you talking about? This is the future of low-level CSS programming! Finally I can use tailwind on SQL, this is revolutionary.

[WilfredTinega]

I will be testing this with frappe and erpnext, it will be funny

[R-udren]

It's actually good

[makimask-jx]

Please avoid gate-keeping the future of web development. Billions must query the database

[ptaberg]

Honestly, it's all fun 😁, and I would like to support everything exclusively this way.

However, what are the real drawbacks of the concept? Most people still mindlessly bombard requests directly into the database from server components.

Cache? Performance? How can we address these issues to make them a serious consideration? 😅

[TechyAditya]

Well, giving client the option to interact with sql query is disadvantage itself! I'm coming here from prime's video btw

[rihards-simanovics]

However, what are the real drawbacks of the concept? Most people still mindlessly bombard requests directly into the database from server components.

Primogen video aside, which is how I heard of this, this project seems to be a solution in search of a problem.

Why do we need this, and who is the target audience? Tailwind is there because it allows projects with large teams to keep their CSS clean instead of having !important upon !important overriding some's bad decision in the past, what does this solve? Tailwind also provides extensions which provide hints, are you going to build one too? Queries also largely remain the same, just with some extra tailwind-ines added on top, so again, why?

Just to be clear, it's nice to just fart while pointing your backside to the sky because you can, but why?

[ptaberg]

I happily went to watch ThePrimegen's video, but he made a video not about my version, but about this earlier implementation of the approach.

[rihards-simanovics]

I happily went to watch ThePrimegen's video, but he made a video not about my version, but about this earlier implementation of the approach.

I know, it's just so happened that your project shared the same name, so I checked it out. When I wrote my initial remark about yours specifically, I haven't used what Primogen mentioned in the video, just found this via search.

All the fun and jokes aside, I genuinely want to know the reason I would want to use this because right now, it just looks like a tailwind SQL wrapper component tied to a Prisma.

[Lodimup]

This is the future of webdev.

[ptaberg]

This is the future of webdev.

truth.

[makimask-jx]

This is the future of webdev.

The cat of truth and goodness

[samad-scs]

Alot of security considerations would need to be made to make this revolutionary idea possible tho.

First thing came to my mind is sql injection. I understand the classes will explicitly be allowed server side so it might not be possible to query db by editing in devtools. Still a valid concern on my end.

Another major concern is caching. We can't query to db all the time. Auth based queries which requires users jwt token from client side might prove to be very difficult.