πΎπππππ πΎππππ
TTCTheo's Typesafe Cult
β’Created by bythewayitsjosh on 4/22/2024 in #questions
Choosing a React stack
Good point too. Btw, you're able to host Astro app as easily as the Nextjs one on Vercel, just add on that
42 replies
TTCTheo's Typesafe Cult
β’Created by bythewayitsjosh on 4/22/2024 in #questions
Choosing a React stack
'CRA is dead, Now what?' 22:10 β 31:25, in case it didn't catch timestamp from mobile
42 replies
TTCTheo's Typesafe Cult
β’Created by bythewayitsjosh on 4/22/2024 in #questions
Choosing a React stack
@bythewayitsjosh https://youtu.be/Fctw7WjmxpU?si=PqVbj51Y6R1tuOIn&t=1331
42 replies
TTCTheo's Typesafe Cult
β’Created by bythewayitsjosh on 4/22/2024 in #questions
Choosing a React stack
Iβm trying to find the interview with Dan Abramov, where he explains, what and why they suggest as a React team
42 replies
TTCTheo's Typesafe Cult
β’Created by bythewayitsjosh on 4/22/2024 in #questions
Choosing a React stack
Between these two? Not really, since you can use other frameworks/libraries inside of Astro templates
42 replies
TTCTheo's Typesafe Cult
β’Created by bythewayitsjosh on 4/22/2024 in #questions
Choosing a React stack
I usually start from figuring out the amount of client interactions the app has to deal with.
Pretty few of them and theyβre simple -> Astro
Kinda dynamic app with more stuff, than a simple like button -> prolly Next
A ton of them -> definitely go with Qwik
42 replies
TTCTheo's Typesafe Cult
β’Created by bythewayitsjosh on 4/22/2024 in #questions
Choosing a React stack
^word. As Iβve said, you can always use something like @astro/react, you feel like plain Astro doesnβt provide you enough ways of handling client interactivity
42 replies
TTCTheo's Typesafe Cult
β’Created by bythewayitsjosh on 4/22/2024 in #questions
Choosing a React stack
I mean, it depends. Just for sake of the example, project that feeds me is heavily reliant on a ton of client interactions like sliders, clicks & dragβnβdrop. Thus why Iβve chosen Qwik over Next there
42 replies
TTCTheo's Typesafe Cult
β’Created by bythewayitsjosh on 4/22/2024 in #questions
Choosing a React stack
Basically, the last sentence. Whatβs the point of using it, if youβll end up opting out of like 60-70% of the features? Thatβs just a personal opinion
42 replies
TTCTheo's Typesafe Cult
β’Created by oldspicebodywash on 4/22/2024 in #questions
What does data flow mean in the context of react props?
It has nothing to do with streams directly
6 replies
TTCTheo's Typesafe Cult
β’Created by oldspicebodywash on 4/22/2024 in #questions
What does data flow mean in the context of react props?
Thatβs what is βunidirectional dataflowβ
6 replies
TTCTheo's Typesafe Cult
β’Created by oldspicebodywash on 4/22/2024 in #questions
What does data flow mean in the context of react props?
As far, as I understand, thatβs just more technical way of saying, that youβre passing props form parent to child component
6 replies
TTCTheo's Typesafe Cult
β’Created by bythewayitsjosh on 4/22/2024 in #questions
Choosing a React stack
With it you are always able to inject React components, in case client reactivity is needed
42 replies
TTCTheo's Typesafe Cult
β’Created by bythewayitsjosh on 4/22/2024 in #questions
Choosing a React stack
That sounds like βif I donβt pick Next, Iβll build my own one, but with other piecesβ
I agree on the part, where Next is a gigantic overkill. If you donβt have any signs of project going crazy in scale, stick with Astro
42 replies
TTCTheo's Typesafe Cult
β’Created by bythewayitsjosh on 4/22/2024 in #questions
Choosing a React stack
That should give you some sort of solid ground to try and form your personal opinion and taste
42 replies
TTCTheo's Typesafe Cult
β’Created by bythewayitsjosh on 4/22/2024 in #questions
Choosing a React stack
Greetings. Imo, you should start with Theoβs video on how to choose a framework. Even though, I disagree with some things, he basically answers your question on almost every framework besides, at that time, app router next js
42 replies
TTCTheo's Typesafe Cult
β’Created by Gaz on 4/3/2024 in #questions
Horizontal scroll bar tailwind
My first assumption is that you might've forgotten css resets, thus header is taking more space via its native margin
6 replies
TTCTheo's Typesafe Cult
β’Created by Crim on 3/30/2024 in #questions
Basic system design questions for a big project
Couldn't find Theo's one, but repo seems to be using Pusher and tRPC too.
https://github.com/YaroslavChuiko/GlassyChat
5 replies
TTCTheo's Typesafe Cult
β’Created by Crim on 3/30/2024 in #questions
Basic system design questions for a big project
Hey. I really hope, that it's more like a study project, because you're touching a few points that could lead to an ultimate footgun.
1. You can use almost anything, depending on how secure you want it to be. If you need teamID, for example, to identify the dynamic route, feel free to use URL params. On the other hand, if it grants some sort of access, you could use any state management solution, e.g. passing props or ctx or basically anything. There're a lot of videos on how to choose them for your goals.
2. Using WS on serverless is a pretty big painpoint. To me, personally, it was significantly more difficult, than while having a server. Though, you still can hook up pusher with trpc. I'll try to find an example Theo was making long ago.
3. "It depends" on a lot of things. Like, figuring out your app's data flow, the amount of data you need to query, the need in preloads, etc.
Per page basis is the most common one, I'd assume, but make sure to place data fetching as deep as it could be. Don't just yolo query everything in page.tsx if you'll have to pass it like 5 layers deep, while these layers have nothing to do with the data
5 replies
TTCTheo's Typesafe Cult
β’Created by FleetAdmiralJakob π π π on 3/15/2024 in #questions
trpc v11 error: The transformer property has moved to httpLink/httpBatchLink/wsLink
That seems like a strange behaviour, though I'm not that familiar with RSC version of T3 yet, to help out. All I can suggest is to debug the ctx everywhere starting from observable callback
15 replies