Comments by "Luther T.S." (@LutherDePapier) on "Theo - t3․gg" channel.

  1. Thank you.
    1
  2. How is a new language any similar to some other entity writing in the same language? If we were talking about brand-new AI-ready languages that AIs write better than humans like they've always done with 1s and 0s, sure. But we're not though.
    1
  3. And why would a * child be in a different file EVER. Are you insane.
    1
  4. Is this about React 19?
    1
  5. I agree with the comment saying survivor bias. Most passionate people never saw return on their investment within the specific project they were invested in.
    1
  6. That's a life lesson right here.
    1
  7. Does it work if you're Black?
    1
  8. Apple will be buying them soon.
    1
  9. ​ @p99chan99 That is a gamechanger idea.
    1
  10. That's what I'm worried about, and why I haven't used it yet.
    1
  11. I think it always depends. If it's a clear improvement of what you've always used, it's worth upgrading. But if it's a complete rethinking, it's worth trying out in your spare time.
    1
  12. If AI is the code that WordPress writes for you in the editor, then what we're talking about here has been true for about the decade. So what are we actually talking about?
    1
  13. When I hear about how all of these (Western) technologies we use everyday are fundamentally flawed, I can't even begin to imagine what is going to happen when a serious competitor like China will pull the entire weight of its governement and industries to make their own, dramatically superior solution, obviously initially exclusively for their own developments.
    1
  14. I disagree. You don't need to use Google for research anymore now that ChatGPT can do it for you. What Copilot does can not only be done via ChatGPT, but is even done using ChatGPT.
    1
  15. Before I watch, everything about this thumbnail is true.
    1
  16. If kitze was wrong, GitHub would be out of business. Sadly she isn't wrong yet.
    1
  17. Is it compatible with most modern browsers?
    1
  18. Agreed, I didn't notice that the video ended.
    1
  19. "It does not have server components yet." *closes video"
    1
  20. Xuan was working on Hermes.
    1
  21. Put my fellah DeepSeek's name out of your mouth please. No hate on my lord and savior.
    1
  22. We've been running this for years.
    1
  23. And "kinda right" is not what you would bet your entire product on.
    1
  24. There's already a .forEach in Javascript. For of is different.
    1
  25. It's not "these guys." It's Matt.
    1
  26. The hate on the * variant is making want to set my virtual keyboard aflame. WHY WOULD YOU EVER DECOUPLE A PARENT WITH A * FROM ITS CHILDREN??? WHY??? Not only is this feature optional, it is specifically designed for this use case, for when parent and children are this intrinsically linked. Any other usage, and the inference of any other usage, is the demonstration of nothing short of a skill issue. Now let sat a parent needs to be a Server Component and the child needs to be a Client Component. Fellah, just make two different files in the same repository. Problem solved.
    1
  27. Disagreed. You should specifically use * to affect children that should NEVER be imported without their parents. Basically you're using * in cases where you can do otherwise, especially with inputs.
    1
  28. You were what years old?!?!?
    1
  29. OK. What junior takes two years to train? Someone who's never coded before? Meaning someone who can't even dream about seriously applying?
    1
  30. I agree.
    1
  31. PERSONA MENTIONED.
    1
  32. "Election meltdown watch party." 😂😂😂
    1
  33. Where does the hate on reduce comes from?
    1
  34. "Web developers aren't used to dealing with access control." So all this is is a skill issue. Noted.
    1
  35. ...And Ryan Florence is 100% right on this.
    1
  36. It's funny though. The same dude who was moving on from Arc, weighing options about browsers, and dismissing Firefox outright, now makes an entire video about Firefox.
    1
  37. I love reduce now that I know how to use it.
    1
  38. Which effectively means the Chinese in China and the Chinese who will return to China.
    1
  39. If you want separation of concern between client and server, there's Next.js for that. I for one find it great that RRv7 is providing another alternative.
    1
  40. React Server Components package spotted.
    1
  41. I knew. 😌
    1
  42. Actually I learned it on MDN a few days ago. 😅
    1
  43. So the issue is not React it's GitHub. And it won't be React once React Compiler is stable, which it's about to be.
    1
  44. I can't believe Theo has to explain what a for of loop is.
    1
  45. I disagree with the assumption around 1:50. It's literally BECAUSE the dude made Svelte that he SHOULD have been in a position to know this. And it's because his framework has clout that he should then have used that clout to influence the evolution of HTML, much akin to Next.js and React.
    1
  46. Imagine one day React leaves Meta and becomes independent.
    1
  47. No.
    1
  48. So basically Bolt is an AI product that knows it's going to fail and therefore gives you the opportunity to manually fix its failures.
    1
  49. 11:49 Again, disagreed. Being obsessed doesn't guarantee that you'll get to the point you're talking about either.
    1
  50. Disagreed. For gradients, just use @apply.
    1