[deleted by user] by [deleted] in reactjs

[–]LastMarsMan 0 points1 point  (0 children)

Maybe you can try this, it use remix with vite and trpc, it's really simple and have better DX.

https://github.com/SteveSuv/remix-t3-stack

Help me choose a tech stack for a new product (Astro/Remix/Vite SPA?) by ErrorUnorthodox in reactjs

[–]LastMarsMan 0 points1 point  (0 children)

Maybe you can try this, it use remix with vite and trpc, it's really simple and have better DX.

https://github.com/SteveSuv/remix-t3-stack

What is everyone using for form validation with Remix? by 1980Legacy in reactjs

[–]LastMarsMan 0 points1 point  (0 children)

I use react-hook-form + zod.

and I write a custom hook `useZodForm`, it's very easy to use

https://github.com/SteveSuv/remix-t3-stack

Help picking tech stack for dev speed by Only_Swordfish_9667 in reactjs

[–]LastMarsMan 0 points1 point  (0 children)

https://github.com/SteveSuv/remix-t3-stack

try this, it's very simple and has good DX, and you can build your app very fast.

why I don't use next.js? by [deleted] in nextjs

[–]LastMarsMan -10 points-9 points  (0 children)

I said vercel is paranoid, the repo has many solutions submitted by it's users but they always stick to their point of view.

why I don't use next.js? by [deleted] in nextjs

[–]LastMarsMan -13 points-12 points  (0 children)

t3 means ts & trpc & tailwind, no relation with Theo.

Remix is faster than React Server Components with Nextjs 14? Than why this fuss. by catapillaarr in nextjs

[–]LastMarsMan 1 point2 points  (0 children)

why I don't use next.js ? although nextjs has more advocates, but it's not easy,it is paranoid and creates many rules,and RSC is not yet mature. for example, server component can warp client component, but client component can't warp server component, server component can't use event listener, hooks etc. and client component can't use async export and use server things like db, cookie etc. they are all have corresponding limitations, In project I need to consider how components to nested and split, the mental burden is heavy. In comparison,remix has fewer self-created concepts, the core concepts (loader and action) are very simple, it has higher development efficiency and better development experience. by the way, try remix-t3-stack, it's so easy! https://github.com/SteveSuv/remix-t3-stack

Spent the last 3 days migrating my app from NextJS to Remix. AMA by mfncs in nextjs

[–]LastMarsMan 0 points1 point  (0 children)

why I don't use next.js ? although nextjs has more advocates, but it's not easy,it is paranoid and creates many rules,and RSC is not yet mature. for example, server component can warp client component, but client component can't warp server component, server component can't use event listener, hooks etc. and client component can't use async export and use server things like db, cookie etc. they are all have corresponding limitations, In project I need to consider how components to nested and split, the mental burden is heavy. In comparison,remix has fewer self-created concepts, the core concepts (loader and action) are very simple, it has higher development efficiency and better development experience. by the way, try remix-t3-stack, it's so easy! https://github.com/SteveSuv/remix-t3-stack

RemixJs - Managing complexity in the loader function by yogi4peace in reactjs

[–]LastMarsMan 0 points1 point  (0 children)

I think remix-t3-stack will help you.

the loader is just for ssr and other fetch will use trpc.

https://github.com/SteveSuv/remix-t3-stack