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

  1. The gymnastics people do to avoid using Firefox. Smh.
    879
  2. 6:28 OK I'm not gonna waste 20 more minutes of my life watching this.
    60
  3. Getting a job in tech nowadays is the equivalent of a 30-year-old+ woman trying to get married.
    30
  4. I love how the React docs aren't even up to date.
    30
  5. "...and you're actually part of communities of people who write code." That has literally become a requirement for employment, and I'm not sure that it should be for developers just to be able to eat from the skills they've acquired. And the worst part is, for example any frontend developer can go on the web and see the amount of work that needs to be done. Amazon does not have a dark mode. There's bugs in UI everywhere that every user encounters every single day that they go on the Internet, some even requiring to reload pages. You can't go on the website on an employer without noticing some bad UI or some poor optimization, which kinda makes you scratch your head as to why they didn't even let you reach the interview.
    23
  6. The day the Chinese launch their own fullstack React is the day RSCs are retired.
    14
  7. I heartly disagree about the comparison with gamers. We're not asking "why can't you add more maps?" We're asking: "You've designed and shipped a live game for which you require your users' time and money, why didn't you put in place the tools to better support said live game before you actually shipped it?"
    12
  8. HARD disagree on "eating your vegetables for you." If you want to be healthy you need to LOVE eating your vegetables. You need to develop a palate for vegetables. The same goes here for code. You need to find appreciation in the tedious things, especially for maintability purposes. Making a variable naming convention that you and your team understand at a glance, refactoring your code to make it yours and understand to your core exactly how it works, so that when the time comes to revisit, you have a holistic understanding how why you wrote that code in the first place. I'm not saying ditch the AI at all, hell no. I'm sayinf have the AI help you, but you do the implementation. I don't think people are ready for the technical debt they'll be hit with when every small thing would have been made by AI.
    7
  9. I don't think people understand that free is greater than paid.
    6
  10. Wait. It's been out since November 22?
    4
  11. I felt the exact same way in the beginning. But now I watch pretty much every new video because there's so much to learn in them. It's the YouTube game. If it wasn't for the silly thumbnail, I wouldn't even have known that Theo exists. Just like a man can't notice a nice woman if she doesn't at least try to get his attention like the less nice women do.
    4
  12. I swear to God and I'm just about to finish Royal too.
    4
  13. This is facts.
    4
  14. MariCar tried and they got sued successfully even though they got the shoutout from Hugh Jackman.
    3
  15. So basically in order to get started in tech nowadays you need to know someone.
    3
  16. It's not copying it's implementing. Like when React implemented Remix's actions, the word "copying" was never used there and if we think for a second we all know why it's been reflexively used here. Basically the Chinese made their own React framework which they'll be using and growing for the foreseeable future, powered by Alibaba just like React is powered by Meta. We'll need to start shitting our pants when they'll make and embrace their own React too.
    3
  17. "He's kinda right." We'll see about that in six months.
    3
  18. I've heard this before, the issue is that users need to be authenticated on every action. How is that not the most basic server-side best practice every developer should already know about?
    3
  19. 3:42 But that's exactly what Dario is saying.
    3
  20. I just want all my fellow junior devs to know that the chain of command which lead to this chaos has made more money in salaries this year so far than most of us will make in a lifetime. Think about this when bots online condescendingly refuse to allow you a single interview.
    3
  21. There's one downside of serverless that has not been discussed: Parler. What happens when your serverless decides to kill your business? Are you still saving money when that happens? And isn't it guaranteed to happen in a growing number of scenarios?
    2
  22.  @JanVerny  And you're 100 % correct. Amazon has all the means in the world to make and maintain a dark mode, but they probably decided that all the investments that are going to be required to make the same user stories they've crafted so well in dark mode (what about pictures, for example) are currently not cost-effective. So the true issue here is that all of the work we see that needs to be done and that could be handled easily by a well-led team of junior engineers, which could kickstart their careers and lead them to become valuable seniors down the line, is just not worth the expense for individual companies in the short term. It could and would be worth it in the long term in terms of nurturing new senior developers, but what guarantee do individual companies have that these seniors would stay and that a company would not have created a senior that would later defect to a competitor? None. This is fucked up. And it just come back down to what Theo alluded to. If you're a junior dev who wants a job, you need to be friends with the person that will give you that job. That has become your best selling point right now.
    2
  23. 13:00 That's literally not what Dario is saying since he literally says that it will reach virtually 100% and not stay stuck at 90. You're effectively hearing what you want to hear from this, while people are reacting to what he actually said.
    2
  24. They're not living in their own world. They're living in their own country. I don't know why still in 2025 this is so hard for Americans to understand.
    2
  25. Why am I the first to like this comment?
    2
  26. 🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣🤣
    2
  27. That's true.
    2
  28. No.
    2
  29. Theo stop this.
    2
  30. Why Promise.allSettled instead of Promise.all?
    2
  31. "It's a good interview problem." In other words, it's useless.
    2
  32. 9:46 Problem is, we're entering a world where instead of maintaining applications, people are just going to reprompt them to some form of "success." So all of these projects you see on Lovable are probably 1/10th of what is actually generated.
    2
  33. I don't know why anyone should be surprised by how polished this is when Alibaba makes it and therefore depends on it. We're talking about a company whose valuation has generally been around $250 billion to $300 billion USD.
    2
  34. React 19 does not control your server or something like that. React is a library, not a framework. As such, it only controls stuff over which React as agency: modules that export components, modules marked with directives, and modules that export Server Functions. For anything else, you're on your own, and you'll see the errors and the security issues in production soon enough.
    2
  35. Every second a new JS runtime is promised to hit the grave. Meanwhile, node be like:
    2
  36. I mean for real, actions in React 19 are like actions in Remix. They're basically an endpoint anyone can hit if they know the endpoint. If you have a route called /create in Remix anyone can type /create in the URL. It's up to you as a developer to always authenticate on the action itself before doing anything else, even if there already is some middleware auth somewhere else in the project. So I really don't see what the issue is here.
    2
  37. The real issue is that this is pretty much WordPress themes and WordPress plugins for React developers, and slowly but surely, because we're no longer going to be developing anything by hand, we're no longer going to be able to come up with anything truly unique this way.
    2
  38. Honestly, it's a thing that is doomed to crash and we're all going to be there laughing eventually. It's one of these stories where the Western world is one again failing, just like the aging population. People don't want to make babies because it's hard and expensive work with no outside support, and therefore once the senior generation retires, nobody will be there to replace it. Here, the contrast is there's an "overpopulation" of junior devs, and instead of accommodating for it to secure its own future, the industry and the Western countries do nothing to help except promoting expensive bootcamps that have eventually nothing to do with getting you hired. For me, the safest bet is to look for work where that mentality doesn't exist, or leave somewhere cheaper where you can remotely do works in the West for less money and a dramatically better purchasing power. (And, to be fair, a more satisfying life too.)
    1
  39.  @ItsUhMeIbraheem  Why thank you. 🫂
    1
  40. "Moving every back to the client." The idea about RSCs is not to move everything to the server but rather to finally have the possibility to move things to the server within (what ought to be) a 100% React paradigm. Then you can choose what's on the client, and what's on the server.
    1
  41. Is Temporal out yet?
    1
  42. OK, so they're saying it's replacing an engineer but it needs one as a copilot every step of the way.
    1
  43. STAAAHHHPP. Just a friendly reminder if someone comments the video without looking it doesn't count as a view. And Firefox automatically blocks autoplaying videos.
    1
  44. Why are we entertaining and celebrating something that is demonstratively unreliable and expensive at being unreliable?
    1
  45. I honestly have a hard disagree on your take on survivor bias, especially when the only examples you bring are those of successes, ignoring the mountain of failures you don't know about, most of which you will never be able to know about. Actually get this, you mention Amazon, the very company that purposefully kills 9 out of 10 projects for a single one to make all the money the other nine didn't. Without even going further than this example your point is effectively invalid.
    1
  46. Welcome back.
    1
  47. Honestly, these Darios, Sams, or whoever, would have been a lot more credible if they weren't so arrogant. "90% of the code will be written by AI." Sure. What code though? What happens when you realize that writing the code yourself is literally shorter than the prompt to get the AI to write it? If you've structured your code perfectly to make it AI agents-ready, that's 100% possible. But if you don't. Good luck. And you won't.
    1
  48. I thought about this before. I used to manually update 20000 articles by hand, having memorized my patterns, because I couldn't code yet. Now that I can code, it's something that I would be able to templatize programmatically. If 90% of the code means AI writing what I used to write by hand on every article, it literally has zero value. If it's coming up with the patterns and implementing them itself, now we're talking. But if my project is any unique, the amount of details it will need to implement the right patterns is literally more complex than me implementing it myself. What I mean is, if you're codebase can be 90% written by AI, then by definition your codebase is not unique, and I would argue that your product, without marketing, has no business being successful.
    1
  49. true
    1
  50. Except, the bias is open-source, while ChatGPT's biais is behind closed walls.
    1