Comments by "WloCkuz" (@wlockuz4467) on "Theo - t3․gg" channel.

  1. "I am the tech YouTuber with good hair" It's like Thor is invisible to him 😂
    1000
  2. I don't wanna get into the framework wars because they're pointless. But can we all agree that a network request on each keypress is ridiculous. No matter your tech stack, its just horrible design.
    330
  3. I will never understand how Meta can be a dogshit company when it comes to users, public relations and privacy, but be genuinely good at open source.
    273
  4. When its publically available, the first thing we are obligated to do is create Will Smith eating spaghetti.
    249
  5. Rust, a language with zero cost abstractions and potentially multi thousand dollar cost lawsuits.
    168
  6. We have put a bandaid on the bandaid that was supposed to stop the bleeding from the previous bandaid so that you don't have to put more baindaids yourself over the bandaids you already have put.
    161
  7. GET OUT
    155
  8. The author of Apna College is an Ex-Microsoft engineer but didn't have the foresight to create a demo repo which is astounding. She could've actually taught her audience more about the PR workflow if she owned the repo, this is what almost everyone does. I think Fireship did this the best with his Git/Github video! Worst part is that she unintentionally damaged the reputation of people trying to learn Git/Github and her community in general. Hope she takes responsibility and does the right thing asap.
    151
  9. ElasticRedis*
    142
  10. One of the most simple and fundamental components of UI - an input, turned into a complicated and unusable mess. Its just sad at this point.
    133
  11. UI = f(state) UI = f(data, state) That's such a beautiful way to describe React's evolution. If only developing with it was as elegant.
    124
  12. Just an unopinionated javascript library. Nothing to see here.
    104
  13. He already shits on JS/Node enough that it would be just a compilation of clips from his old videos 🤣
    103
  14. Its wild to me how Theo just casually uses his personal anecdotes to entirely discard serious discussions like Google throttling their services on other browsers. "I had a bad developer experience with Firefox, hence Google slowing down their services on other browsers must be bullsh*t" How does that even matter or make any sense. like do you even think before you speak or listen to yourself? Same goes for the whole video, the point is not about what that code can do, but more so about why does company specific code exist in an OS project.
    97
  15. Can we all agree the word art totally slaps. Its not pretentious and sparks a feeling of nostalgia. Something that is so rare these days.
    88
  16. Am I the only or the T3 logo looks more like T6?
    72
  17. Prime has been in God mode ever since he left Netflix. How do you even fold a digital page 💀
    67
  18. Couldn't agree more. If you look at the history of this channel then its basically "I am excited about this shiny new thing" and a few years later its "I am moving away from my current thing because theres a new shiny thing". I wouldn't even be surprised if he is like "Why I moved away from Vite" in a couple of years. This pattern keeps repeating. I'll admit there are some informative videos but they probably don't bring in much revenue so we don't see those kind of videos being produced often. Its not just a problem with this channel. Its a problem with the tech bubble in general. Everyone just does hot takes and shills the new things because thats what makes them the money. Its basically tech brainrot, you don't get anything of value, just disappointment.
    62
  19. I'd usually make a JS framework joke, but after using TanStack Query and Table for so long I have high hopes for this. These guys know how to have a crazy good DX while also making an extremely flexible library. The only concern I have about this is the amount of abstraction that is going on. Its hard to even tell what is doing what unless you're already deep in the weeds, If something broke in an unexpected way, it would surely be debugging hell.
    60
  20. Of all the "React killers" out there, Solid feels like the only one that can actually compete with React. In fact, I'd go as far as to say that this is what modern React should've looked like.
    60
  21. Nobody: Me calling all my functions "funion" because I can
    58
  22.  @t3dotgg  I think the counter argument in the OP is pretty clear? we are creating solutions to solutions that were supposed to solve problems and at the end we just end up having a different set of problems so there is no net positive. But my point was you getting defensive and saying something like "...and eventually you won’t have a job :)" which just sounds immature and petty coming from someone like you.
    56
  23. I think the worst part about this whole argument is that public callout is the only way to get something like this sorted. The more I think about it the more terrifying it gets. Its exactly like YouTube's copyright strike system, if a small guy gets unfairly striked there's no way he will get help, unless by some miracle he gets some attention in the community. You said "chill, it gets handled" as if that the case with every incident. There have probably been many cases that just got unheard of and that's sad because the only medium to get attention of these companies is Twitter. Companies don't need to worry about my moment of glory, they need to give me more control.
    45
  24. It is hilariously ironic that Microsoft, the bastion of AI, has failed to use AI in one place where it would be the most efficient.
    43
  25. I feel like abstracting away this behaviour was a horrible idea to begin with. This is clearly something that should exist at the app level and not the framework level.
    41
  26.  @t3dotgg  Why do you get so defensive when someone offers a counter argument to one of your opinions?
    34
  27. So in the end Microsoft wins. Who would've guessed. But more importantly what about Emmett's investigation? Now it feels like they're definitely trying to hide something because they would rather let Sam back in than have an investigation.
    33
  28. It will also give rise to reputation farms, basically accounts creating bogus repos and contributing nonsense to each other in order to gain rep.
    26
  29. 30:15 Oh my god. All that build up and he just ends up describing why Tailwind exists. The self-awareness of this article is non-existent. "You start with a pure semantic layout and figure out reusable pieces of CSS" First this approach is impractical when working professionally because you just don't have time and resources. Second, this is literally what Tailwind does, it has figured out a sane way to make CSS reusable without getting lost into specificity and naming hell. God forbid BEM and OOCSS and other conventions. "At times, especially when building new components, you might want to prototype quickly with inline styling" Again this is barely feasible. Good luck prototyping with inline styling then migrating to CSS, worse yet having to go back and change these because you changed something elsewhere and its affecting your previous classes because of cascading. "But that's okay and part of the system" That's just an excuse. You need a very good argument as to why such a big bottleneck should be a part of the system if there are no clear benefits. "You can clean things up later" Again, like already mentioned in the video this is a pipe dream. But this is where Tailwind shines the best imo. You can prototype something quickly and leave it in there without having to worry about "cleaning" it up. Example, If you have a "flex flex-col" in your prototype you can be guaranteed that it will stay that way regardless what other things change.
    26
  30. Missed opportunity to run it on Facebook and Instagram, two sites that probably use most amount of React.
    26
  31. I think "use client" is more fitting because when we think of servers we usually do so in a server-client relationship. "use interactive" may be more misleading because when you think about it, not all clients have to be interactive.
    25
  32. At this point itt clearly shows their MO: "If you're anywhere below the Enterprise plan, you're not worth the hassle for us."
    25
  33. Exactly, haha
    22
  34. Don't decide what you do or don't based other's opinions, especially influencers whose whole job is to make money while giving hot takes. If you think something would be fun to learn and would be a great addition to your skills, go ahead and do it!
    20
  35. Simply speaking Vercel is basically a wrapper around AWS, so its essentially: AWS charges + Vercel's operational charges + Vercel's margin
    19
  36. Surprised you don't use query key factories in your code, this is something I learned from Tkdodo's blog and its been amazing because now I don't have to remember query key names if I want to invalidate them in any place.
    18
  37. At this point, React just feels like Apple of frontend frameworks. They "reinvent" what already exists and present it as Innovation. I loved and learned React for its simplicity but the more I used it the more I realised its just a false promise and anytime you want to do something even remotely useful, you have to throw the "simplicity" into a trash can. I wish in the future React fixes itself with a major non-backwards compatible version that just forgets existing React and applies the collective knowledge of decades to actually make a decent framework. Or It gets replaced by something already doing things right, like Solid.
    18
  38. The point of the video aside, How can you tell your community to not harass this guy, but then constantly cuss at him and resort to personal attacks yourself? Grow up.
    17
  39. I used to work with Firebase a while ago so take this with a grain of salt. Yes, its okay to expose public config as long as you have setup the rules. Without the rules authorization doesn't exist, meaning any user can write to any other user. If you don't setup correct rules then Firebase will keep yelling at you with a red warning, but it is possible to ignore it and still proceed.
    17
  40. I don't know what would be worse, a bad developer using Firebase or a bad developer rolling their own backend.
    17
  41. In Firebase's defence they show a big red warning when deploying without proper rules. At least they used to when I worked with it a few years ago. On the other hand, I think its better for any platform to be restrictive by default so in Firebase's case, it shouldn't let you deploy without you understanding the implications of the rules. Something like this probably doesn't exist because the execs think its not important and creates a lot of friction for customers trying out the platform for this first time. Its the classic example of business goals undermining good security practices.
    15
  42. Well this has actually happened already. So when dealing with dates and server side rendering there is an obvious problem. If you generate a date on server and then try to hydrate it on client then you get two slightly different dates because some time has passed between the two events. This results in a hydration error because the hydration needs the state to be the same between server and client. The proposed fix by react team is to monkey patch the standard Date class which is a horrible idea imo. I'd much prefer if they just gave their own wrapper around Date instead of messing with the standard classes.
    15
  43. ​ @XNaos  What are you even saying? If they could optimize it that well they would've already done it.
    15
  44. Whenever I run into obsecure issues like this, my first go to is to reproduce in a different browser. You'd be surprised how greatly this narrows down the issue. In this case it may not have helped immediately but if by some chance you inspected Firefox's dev tools, you would've noticed the styles. I know it doesn't have to be this way, but its something that has helped me in past with navigating this stupid mess we call web.
    15
  45. Finally some good content that isn't about reinventing the same thing or AI. Really enjoyed this one, threejs never fails to blow my mind.
    15
  46. ​ @tejasaditya551  It shouldn't matter how she got hired, the problem is she tried to teach something that she her self didn't understand well enough and that caused all the ruckus. If theres one thing to take away from this incident, its to screw courses and do your own research if you actually care to learn.
    15
  47. If Phil is still learning design, then I am basically striking rocks together in my Figma cave.
    14
  48. Not a risk unless you actually have an account singed in on that website.
    13
  49. Ah yes, the Senior SQL Model Manager
    13
  50. 8:40 Why should the end users understand or care about the infrastructure at all. Its like saying you need to fully understand the electric grid of your city to turn a light on or off in your room.
    12