Its a chronic ilness, once you get into this bullshit youtube influencing category, there is no way out, your rank in among other influencer is based on your hair color.
@@adotinthecosmos this is the opposite of Theo hate - reducing Zoom to a "Ping competitor" (Theo is a founder of Ping, a video call app - saying Zoom will be more successful now that they're employing the T3 stack (which Theo played a major part in creating)
I use Lucia and Drizzle and can't wait to see more projects adopt it. I would seriously consider T3 stack but currently a big van of SvelteKit. I think though for open source projects, T3 looks pretty nice.
Congrats, but I'd take it as you helping them, not as good PR for the T3 stack. Zoom has historically had *terrible* software. Like "Are you malware? Why can't I properly uninstall you" levels of terrible.
just because you can do something, doesn't mean you should. WASM on the front-end is not great, at the very least not until we get good support for Interface Types, and well, access to DOM. You just get the worst performance and bundle size, which is somewhat counter-intuitive to the whole "blazingly fast" thing. If you ARE ready to sacrifice your user's experience, then, yeah, if your team likes Rust, writing both front-end and back-end in the same language is nice.
@@illiadenysenko7776 WASM on frontend has come a long way and is getting much better. Debugging can be troublesome sometimes, but even that hasn't been too bad. In my opinion, SPAs are fantastic in WASM. Internal state is fully managed in the WASM binary and writing in a real compiled language makes it very approachable. For sure, WASM is not for small regular sites, but for complex SPAs, I think it's new best way to write them.
@@illiadenysenko7776 I think rust should just be for low level code that requires safety and speed, even tauri to me(even though i like it) sometimes feel like a waste of time
@@illiadenysenko7776 it makes sense if you need a high performance backend. the frontend performance isn't far off. a leptos todomvc is actually smaller than a nextjs todomvc. it's faster at updates too because it's based on signals. turns out architecture is more important than language in this context.
Random thought I had who le watching this... Where is the quality RUclips channels with examples in Go? Someone like Theo who is talking about the state of things and getting excited about patterns and skills, not just making tutorials.
Theo already said on a previous stream that most of his focus has shifted away from Ping. Turns out, making a tool most people aren’t asking for won’t grow quickly.
tRPC sounds like a good solution as a layer between React and the backend written with TS, but does anybody know what could I use to generate and expose types from Django backend into the React environment?
It seems like Theo hasn’t been using trpc for demo projects recently. So you definitely don’t “need” it. That said, I like keeping it around as a data access layer for any app that I build that involves different user roles. The trpc middleware makes life so much easier when you can just slap a “role” attribute in the ctx and keep the bulk of the authorization logic in a trpc procedure. Just my 2 cents 🤷♂️
@@SpeakChinglish that's the same. There is no runtime that actually can run Typescript, they all transpile down to Javascript and run that. Bun pretends to do it, but they throw away all types and then run the code. So it's Javascript again. If you really know a Typescript runtime, I would love to hear about it.
@@kriffos How is it the same if you do type-checking beforehand? This is such a stupid thing to say because statically typed languages like C throw away language specific type information too. Dynamically typed languages have ways of checking types at run-time but why the hell would you do that when it's usually always better to have type safety at compile time if possible. Some people really do just hate on TS/JS without knowing what the hell they're talking about.
@@0x6e95 Typescript does not give you any type safety, it's more like linting and autocompletion. Some checks are indeed compiled to Javascript for runtime checks, but thats still Javascript in the end and no Typescript. I think if one of us does not know what he is talking about, it's you. Typescript is my daily business and I think I know relatively good what it can do and what it can't (and don't get me wrong, I still like it despite it's shortcomings). Btw. languages like C only throw away parts that are not used at all in the final binary - if I remember correct. The relevant parts remain intact.
there should be no reason to use typescript over another strongly-typed language that compiles to javascript and represents web apis. To me it makes more sense to go from strongly typed compiled language -> javascript rather than trying to add types to javascript.
I'm currently using Tailwind, begrudgingly using it, I still hate it, it's design decisions are just so backwards. If I could use something other than Tailwind in my Nativescript apps for Android, I would, because I would rather tear my eyeballs out of their sockets than use Tailwind :(
Wild that you wasted your time watching a video for someone you apparently strongly disagree with and even spent the time to leave a comment to boost engagement on said video.
I have used tailwind about 3 times, ranging from 4 days up to 2 weeks making a laravel app. I hate the use of tailwind, it is writing css in html without having it centralized. Yes you can split up in components (and laravel supports so) but not every web framework does. Still your component files are bloated and makes it hard to read.
Speaking as primarily a React dev, the main examples in docs should not be react, they should be vanilla typescript. You can provide a react example sure, but asking react devs to translate vanilla JS into their framework is a whole lot more reasonable than asking literally everybody else to do the opposite.
t3 is a react framework, it uses next js. No non-react developer is going to work with t3. The examples should be in react as that is what you code in when using the framework.
@@masterflitzer I thought the comment was asking to not have react in the sample code of t3's docs... not zoom's. Yeah, I am dumb, sorry about that lol.
It doesn't mean anything at all. And based on this blog, it sounds like it was written by someone who doesn't have the capacity to select technology stacks.
both zoom and ms teams are really slow and unresponsive at times, the more conversations you have the less usable it is. Really strange because older teams were way faster..
Zoom is much faster than teams, idk what you are talking about. Zoom is as swift as it gets honestly, for a meeting/conferencing app. Also, MS teams is not just a conferencing app, so that's that. You are comparing apples with an apple tree, if that makes sense?
What is up with youtubers and their hairs
Its a chronic ilness, once you get into this bullshit youtube influencing category, there is no way out, your rank in among other influencer is based on your hair color.
Ikr feels like chances of dying your hair increase by 100 times if you're popular
@@adityaanuragi6916 first prime did it and now theo
It gets more views
Looks a bit like the people from the hunger games movies
What if Theo said "bazinga I hate tRPC" and deleted the repo
it's probably get forked
He doesn't own trpc so he can't. He could remove it from t3 but that wouldn't stop them from using it anyways.
maybe this Ping competitor will get more successful soon
Where is all the theo hate coming from?
@@adotinthecosmos How is this hate lol, it's just a joke
@@adotinthecosmos this is the opposite of Theo hate
- reducing Zoom to a "Ping competitor" (Theo is a founder of Ping, a video call app
- saying Zoom will be more successful now that they're employing the T3 stack (which Theo played a major part in creating)
@@adotinthecosmos lmfao you can’t read this joke?
@@samuelgunter ahh... thanks. That comment was me not up to date with the lore, and not up to snuff with coffee. I thought Ping was a file share site
I use Lucia and Drizzle and can't wait to see more projects adopt it. I would seriously consider T3 stack but currently a big van of SvelteKit. I think though for open source projects, T3 looks pretty nice.
Congrats, but I'd take it as you helping them, not as good PR for the T3 stack. Zoom has historically had *terrible* software. Like "Are you malware? Why can't I properly uninstall you" levels of terrible.
Historically, yes. But as of recently, their software has improved a lot. Performance and security wise, as well as w.r.t. supporting devices.
I like Google meet better, a lot of zoom feature require refregirant, like background removal. Meet run smoothly without turning old client to toaster
@@franchocou Yeah because google has a custom extension that gives CPU debugging information on *meet services, and only for google. Suspicious huh?
Nah. It's good pr. Large companies using it validates t3. No matter who they are.
That client / server type checking and clicking from client to server code - blew my mind.
Cool video, it made me rethink some of the structure i'm doing with Nuxt on a pet project
amazing video, happy to be using the same exact stack 😄
Finally. The real Slim Shady
Awesome video. More importantly.. share the hair secrets man 😂 Looking good!
Seen on X today mrng wondered why theo haven't made video on it and here it is ❤
Congrats, Theo.
yay more issues on github from a large corporate entity that most likely wont provide any financial support
Theo looks like tintin now
congratulations Theo! great impact!!
bro's hair is beautiful. like sonic after a powerup
gonna withdraw my application to zoom though based on this jkjkjjkjk
why do you use a seperate client/server in your picthing project instead of server components?
Congrats, for the new haircut Teo. Looks classy.
Breaking News from the future: Zoom acquires Ping!!
that code explanation was flawless
Rust on frontend makes complete sense using something like dioxus.
no it doesn't
just because you can do something, doesn't mean you should. WASM on the front-end is not great, at the very least not until we get good support for Interface Types, and well, access to DOM.
You just get the worst performance and bundle size, which is somewhat counter-intuitive to the whole "blazingly fast" thing.
If you ARE ready to sacrifice your user's experience, then, yeah, if your team likes Rust, writing both front-end and back-end in the same language is nice.
@@illiadenysenko7776 WASM on frontend has come a long way and is getting much better. Debugging can be troublesome sometimes, but even that hasn't been too bad.
In my opinion, SPAs are fantastic in WASM. Internal state is fully managed in the WASM binary and writing in a real compiled language makes it very approachable.
For sure, WASM is not for small regular sites, but for complex SPAs, I think it's new best way to write them.
@@illiadenysenko7776 I think rust should just be for low level code that requires safety and speed, even tauri to me(even though i like it) sometimes feel like a waste of time
@@illiadenysenko7776 it makes sense if you need a high performance backend. the frontend performance isn't far off. a leptos todomvc is actually smaller than a nextjs todomvc. it's faster at updates too because it's based on signals. turns out architecture is more important than language in this context.
Random thought I had who le watching this... Where is the quality RUclips channels with examples in Go? Someone like Theo who is talking about the state of things and getting excited about patterns and skills, not just making tutorials.
why is the article so bright?
Love the 90's look.
Zoom should pay you for that Theo.
You are the competitor Theo, remember ping?
Theo already said on a previous stream that most of his focus has shifted away from Ping. Turns out, making a tool most people aren’t asking for won’t grow quickly.
"reference" (for other people) not "production" apps (for their own use)? huh?
2:03 called me out 😢
Nice, congratulations.
Don’t agree with Theo on a lot of things, but the T3 stack is baller
What's Next? Nuxt 4.
aaah,
i see what you did there😎
tRPC sounds like a good solution as a layer between React and the backend written with TS, but does anybody know what could I use to generate and expose types from Django backend into the React environment?
would also be interested in trpc with other languages (like kotlin)
Zoom finally making good decisions.
Too bad Theo doesn't pump Elixir more. Forever a "loved" language with awesome tools to only never be adopted by anyone lol.
Lucia instead of Nextauth?
With the Nextjs server action, do i need to use tRpc for small project, Theo?
It seems like Theo hasn’t been using trpc for demo projects recently. So you definitely don’t “need” it. That said, I like keeping it around as a data access layer for any app that I build that involves different user roles. The trpc middleware makes life so much easier when you can just slap a “role” attribute in the ctx and keep the bulk of the authorization logic in a trpc procedure. Just my 2 cents 🤷♂️
What about T4 though
Sorry, still don't trust JavaScript for backend
That's why this video is telling you to use Typescript, you are welcome mate 👍
@@SpeakChinglish that's the same. There is no runtime that actually can run Typescript, they all transpile down to Javascript and run that. Bun pretends to do it, but they throw away all types and then run the code. So it's Javascript again. If you really know a Typescript runtime, I would love to hear about it.
@@kriffos How is it the same if you do type-checking beforehand? This is such a stupid thing to say because statically typed languages like C throw away language specific type information too. Dynamically typed languages have ways of checking types at run-time but why the hell would you do that when it's usually always better to have type safety at compile time if possible.
Some people really do just hate on TS/JS without knowing what the hell they're talking about.
@@0x6e95 Typescript does not give you any type safety, it's more like linting and autocompletion. Some checks are indeed compiled to Javascript for runtime checks, but thats still Javascript in the end and no Typescript.
I think if one of us does not know what he is talking about, it's you. Typescript is my daily business and I think I know relatively good what it can do and what it can't (and don't get me wrong, I still like it despite it's shortcomings).
Btw. languages like C only throw away parts that are not used at all in the final binary - if I remember correct. The relevant parts remain intact.
there should be no reason to use typescript over another strongly-typed language that compiles to javascript and represents web apis.
To me it makes more sense to go from strongly typed compiled language -> javascript rather than trying to add types to javascript.
wasm exists. take a look at leptos and dioxus.
what’s a ‘reference app’?
I'm currently using Tailwind, begrudgingly using it, I still hate it, it's design decisions are just so backwards. If I could use something other than Tailwind in my Nativescript apps for Android, I would, because I would rather tear my eyeballs out of their sockets than use Tailwind :(
Tailwind have enough fans and do not need you to join
steve berra of web development
Wait.. did Theo code T3?.... As in coded it from scratch?
An hour ago is wild
I don't know nothing bout none of this but now I want to learn the T3 stack too. Evergreen skill? 🤔
Your hair!!!!
😂😂😂
Endorsed by Zoom™
omg theo's hair it's gone wake up babe theo's hair!!
looking more like Anatoly Dyatlov day by day
Theo can't go 2 minutes into the video without making an L take
Interesting how his takes matter and yours don’t
enlighten us, what was the L take
Wild that you wasted your time watching a video for someone you apparently strongly disagree with and even spent the time to leave a comment to boost engagement on said video.
Nobody hates Theo’s take more than Theo watchers
Going for react was a bad decision
Nice, but you know you will have a hard time coming...
here comes the botss
damn that's a flex
Wow, impressive
I want next 14 with app router in t3 please
I have used tailwind about 3 times, ranging from 4 days up to 2 weeks making a laravel app. I hate the use of tailwind, it is writing css in html without having it centralized. Yes you can split up in components (and laravel supports so) but not every web framework does. Still your component files are bloated and makes it hard to read.
This haircolor really takes away from your moustache. Before looked better, still handsome though!
PogYou !!
OMG ur hair looks dope ngl
What???
Speaking as primarily a React dev, the main examples in docs should not be react, they should be vanilla typescript. You can provide a react example sure, but asking react devs to translate vanilla JS into their framework is a whole lot more reasonable than asking literally everybody else to do the opposite.
t3 is a react framework, it uses next js. No non-react developer is going to work with t3. The examples should be in react as that is what you code in when using the framework.
@@Hmm-p9tprecisely why zoom shouldn't use t3 stack for their example lmao, like your answer doesn't match the comment at all
@@masterflitzer I thought the comment was asking to not have react in the sample code of t3's docs... not zoom's. Yeah, I am dumb, sorry about that lol.
why not nextjs?
As per policy, disliking any video that says that Tailwind is good.
sending hate from ohio
So t3 stack is just a scaffold of some libraries, and you call it "my" stack? Lmao
what did you think
What do you think a stack is? Hold onto your disrespect when you’re inexperienced
...and a cli to create your app and decent structure
Only cool kids use Astro.
Thank you for closing with peace nerds again
Long Live Jquery
I guess Zoom loves tech debt
I feel like they'll regret this
shows that the community + theo knows wtf they're talking about
Zoom sucks tho 😂
It doesn't mean anything at all. And based on this blog, it sounds like it was written by someone who doesn't have the capacity to select technology stacks.
First
Zoom is trash Microsoft Teams makes Zoom obsolete. Zoom just provides a worst experience for users less features and more hassle.
teams is worse, Microsoft's business stack is one of the most dogshit software I've ever used.
ehh teams can suck too
both zoom and ms teams are really slow and unresponsive at times, the more conversations you have the less usable it is. Really strange because older teams were way faster..
Zoom is much faster than teams, idk what you are talking about. Zoom is as swift as it gets honestly, for a meeting/conferencing app. Also, MS teams is not just a conferencing app, so that's that. You are comparing apples with an apple tree, if that makes sense?
@@Hmm-p9t true why have a single apple (zoom) when you can have the tree (MS Teams)
dam lol
jquery ui