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
  51. You couldn't make a less obvious ad lol
    12
  52. Oracle should also discontinue itself while they're at it.
    12
  53. It certainly feels like an unusual direction to move in, but I have stopped trying to make sense of what goes on in the JS land.
    12
  54. I wouldn't expect anything less from a guy who puts his first name in his company name. The only thing that worries me is that this will paint FOSS in negative light.
    12
  55. Its cool to see how far Next.js can take React, but in the end Vercel is a private company so you always have to be cautiously optimistic.
    12
  56. Finally some real innovation in this field. Super hyped for Bun.
    11
  57. Also he wanted something minimal but the winner is the exact opposite of that. The redesign with the subtle animation was the winner for me.
    10
  58. You don't necessarily have to use the Tailwind classes inline, you can use the @apply directive to extract the style under a singular class name like "button" or "link" and use that class name to simplify your components.
    10
  59. Bring in Low Level Learning, would be fun to see whats actually happening at the instruction level. Especially if it can be compared to regular JavaScript code.
    9
  60. This is just an overall sad situation. The maintainer who added the easter egg should've known better considering the scale of the project. (If true) The more sad part is companies which fired devs over it, or worse, learning that China is literally arresting people for celebrating their own festivals.
    9
  61. You know I had to pinch myself because someone was proposing a change to the spec instead of just creating yet another framework. I thought methods like these were forbidden and everything new had to be done via a new framework in JS land. These brave guys really challenging the status quo and I hope it works for them. /s
    9
  62. This hits too close to home. I can put 10 callouts warning why this code is only a PoC and it would somehow still end up in production.
    9
  63. More like respect for EU increased.
    9
  64. Turbopack + Next13 is going to be even better if we take Vercel's word on Turbopack. Granted its still very early for Turbopack.
    8
  65. The wrapper gave me class based components ptsd, hope it gets fixed soon.
    8
  66. *Insert Ryan Gosling Blade Runner meme*
    8
  67. 0:18 I'd argue any or every job there ever exists, "who you know" is probably one of the important bits if not the most important bit.
    7
  68. I think you mean Chromium not Chrome.
    7
  69. ​ @t3dotgg  Where are the leaks, I checked the closed issues I can't find it.
    6
  70. In a month, Vercel could make a meta framework for LLRT
    6
  71. Solid point
    6
  72. They also own Tumblr
    6
  73. Its mind blowing that React is going to be the next PHP 😂
    6
  74. And the only good feature
    6
  75. For the empty dependency case you can create a wrapper around useEffect and pass an empty dependency array by default. Then use that wrapper everywhere instead of the vanilla useEffect. May be hacky but it works and you don't have to constantly worry about passing empty dependency arrays.
    6
  76. I maybe wrong, but a very simple solution could be to set a minimum age for packages and only reward them based on weekly downloads.
    6
  77. Oh my god
    5
  78. Theo has almost gone full circle.
    5
  79. Now I am actually wondering, what would happen if the internet only dropped during the first few keypresses when typing something.
    5
  80. As someone who has previously worked with Android Studio which has a very similar graphical editor I love this! The only major problem is that the trade-off here is leaving the VSCode ecosystem and I don't think anyone will be willing to make it. If they make this a paid extension I would definitely pay for it because it would definitely streamline a lot of workflows.
    5
  81.  @iiNoorbd  Where did I say that good CSS didn't exist before Tailwind? Its certainly did, but creating your own design system from scratch takes a lot of resources, time, and expertise. It is considered a massive undertaking and also the reason why ready made component and ui libraries become popular. Tailwind solves exactly that. It lets you adapt to any design very fast and build quickly. Of course there is a downside of the inline classes, the syntax is ugly. But it didn't take long for me to get used to and at this point its second nature for me, I can even immediately recognize it in other websites. Now I am not usually the one to fight over libraries, If something works for you go ahead and use it, but my DX with Tailwind has been phenomenal that I can't recommend it enough.
    5
  82. ​ @Iswimandrun  One thing I learned the hard way was to never build a good proof-of-concept or demo and present it to non-technical higher ups, it will 100% get shipped because "it works".
    4
  83. I don't know if I should laugh or cry.
    4
  84. React Query is data agnostic, meaning it doesn't care how you provide it the data, via fetch, via XMLHTTTRequest, via axios or pull it from localStorage. All it cares about is that you give it a function that returns some data or throws an error. If the function returns the data it is considers a success, if it throws it is considered an error.
    4
  85. Am I missing something or does it do the same things that you can do with Tailwind + CVA (Class Variance Authority)? 🤔 Also you can easily achieve dynamic styles with Tailwind using CSS vars or plugins so its kinda questionable to downright dismiss it. Either way, it seems like another bloated CSS library.
    4
  86. Legend. Thanks.
    4
  87.  @RoarMcRipHelmet  Welp, I was hoping they would treat Enterprise users better since they're basically gaining them at the cost of their own reputation, but I guess not.
    4
  88. Same lmao
    4
  89. Looking at the comments, he wasn't joking about dying on this hill lmao
    4
  90. Yes, Serverless does scale effectively infinitely, but that means It's cost will also scale infinitely, and that is a scary thought.
    4
  91. Its the way of life.
    4
  92. Before you get into arguments like this you should always remember that your users don't give a sh*t about any of this. They want something that works and gets the job done.
    4
  93. I think problem with the AdventOfCode challenge was that you literally said "Its a problem from AdventOfCode" in the prompt and pasted the problem word for word. AoC being a very popular coding event was likely part of the training data and this type of prompt is likely to align well with the model weights because of it. I think it would be interesting to see the results if the problem is completely rephrased and presented without the mention of AoC.
    4
  94. Call me crazy but the real problem here is serverless. At this point its like we are creating problems just so we could invent the solution.
    4
  95. You can have trademarks for colors? Wtf.
    4
  96. Recommending someone to learn a framework before the building blocks (HTML/CSS/JS) easily takes the cake here for the worst take. This is how you create bad engineers who have existential crisis when they run into a real problem.
    4
  97.  @baka_baca  I feel you. But imo both the developers and React are to blame here. React is too low level for building apps. You absolutely need a framework or at the least a solid set of conventions that stop the "entropy" in a codebase from getting out of hand. React being unopinionated about everything has only contributed to this problem.
    4
  98. Always use burner cards for hobby projects.
    4
  99. I like the initiative but their idea seems brittle for a few reasons - Donations can easily turn into expectations for a lot of companies. "we donate 100k a year to your project, please prioritise fixing our issues over others" sort of thing. - $2k / per dev / per year is a big commitment unless you're already a big company. In some countries 2k is the monthly salary of the devs. I think it should be some % of revenue in addition to how dependant they're on the software. - It doesn't define who you should be donating to - independent maintainers, teams, companies? For example does it make sense to donate to nextjs since it is tightly coupled with Vercel. There are a lot of other intricacies like this that arise due to the nature of open source.
    4
  100. Exactly my thought! This is a dead simple use case for AI and they're failing it
    3
  101. Legendary
    3
  102. This would be a bad solution because the state can potentially be out of sync by 500ms or whatever arbitrary time you have picked. Imagine if someone pasted (not typed) a long text and hit submit within interval, they would recieve incorrect value. This is why uncontrolled input is the way to go, if you still want the input value in state you can hook up a setState in the onChange, or just use the reference.
    3
  103. From a developer standpoint its pretty useless, but from a business stand point the SEO and load times that SSR provides are a big deal.
    3
  104. Not sure what you mean here. Tailwind itself is production ready. But if you want a component library built on top off Tailwind theres a few that immediately come to mind. Tailwind UI, Daisy UI, Headless UI.
    3
  105. I think it would be abnormal if there wasn't any new frameworks before GTA 6
    3
  106. This is a great point. There is a place for low code tools but if you think you can do everything with low code then its just a recipe for disaster. For example, Appsheet is really good at abstracting away the Google Sheet complexity but if you want to build a product on top of it then its going to be impossible.
    3
  107. What you can do in the dev tools is usually outside of the scope of any security specification. If your website can be compromised from the dev tools its not a language problem, its an implementation problem.
    3
  108. I can't with the kitty running around 😭
    3
  109. I am glad there is collective hatred for Outlook when it comes to emails.
    3
  110. Its great to know what tools you prefer, but you should shed some light on what you actually ship with these otherwise this video comes off as "you can do anything with this stack"
    3
  111. With the amount of time webdev goes full circle I am surprised we never get dizzy.
    3
  112. Your point doesn't really make sense, In the worst case scenario Tailwind will have to bundle only a fixed size CSS, for an average scenario a lot of the unused CSS is pruned so the size is even smaller. Depending on how you write your custom CSS it will only grow with the project. And good luck writing custom CSS that is maintainable, reusable and scales well with the rest of the project. If you managed to write custom CSS that meets all three of these requirements, congratulations you just reinvented Tailwind CSS.
    3
  113. One thing thats most sketchy about it is the training data. To have this level of quality in the output you would need massive amounts of diverse data, when I say massive I mean petabytes. There is no way they had licensed every bit of it. Not only would that be expensive, but extremely impractical. So I am assuming a large part of the training data was just YouTube videos. I mean, where else would you get the same video, in multiple resolutions, multiple languages, captions, multiple genres and basically anything you could ask for. When you think about it, YouTube is just a massive unorganised training data if you have the resources. If you had a popular video on social media, then chances are you contributed to training Sora. Whether you like it or not. I would hope theres some regulation in place which prevents these companies from just straight up stealing the data to train their models or someone would strong arm OpenAI to open about their data but with Microsoft behind them, its just wishful thinking.
    3
  114. All these "techfluencers" are always pretentious to some extent. They'll do a hot take for the sake of doing a hot take because it gets more engagement.
    3
  115. I don't think most devs break down huge chunks of code into files to hide complexity as much as they do it for the sake of maintainability and reusability. The benefits become immediately clear when you're working with a sizeable team.
    3
  116. Finally some real innovation in this field.
    3
  117. Well, Of Course I Know Him. He's Me.
    3
  118. Damn you pulled out a classic 💀
    3
  119. The beauty of Tailwind is that it was the WYSIWYG of CSS. You look at a class name and be guaranteed that it does what it says in the name and nothing else. With descendant variants this stops being the case which is why I think its best if it was a plugin instead. That said, I can't wait for people to slap some stars on body and get confused later.
    3
  120. That should be the takeaway from this incident. Easter eggs shouldn't be in libraries.
    3
  121.  @nordern1  Good point. Another solution could be to reward for age + downloads over time and analysing the dependants but it would be complicated to get right.
    3
  122. When the JS devs got tired of creating new frameworks, they went for the runtimes.
    2
  123. A .config folder sounds good. But even better would be a config standard that encourages one language, preferably JSON, so we don't end up with config files written in YAML, JSON, JavaScript etc
    2
  124. Its quite concerning that people talk about how good x model is but never about how it got so good. I am not talking about a particular company, I am talking about any company with a private commercial LLM. Where do they get the training data, what actually happens to your conversation with the LLMs. Do people actually think that flicking a switch saying "Don't use my data for training" is good enough? Just imagine, people basically dump anything and everything into these LLMs without a second thought and that data will eventually be used to train more LLMs whether they like it or not. OpenAI's practices were already questionable and now we have Deepseek, a Chinese company in the game, and we all know how good China is at data privacy. Not to sound like a tin-foil doomer but I think the worst thing to come out of the AI race is going to be the death of privacy.
    2
  125. This is a very niche market to target, but good luck to Resend. That said, have you heard of MJML? Its same thing without the managed part.
    2
  126. I am surprised neither the library nor the end users had visual testing in place to catch something like this.
    2
  127. It sucks that Theo didn't even get to the best part of the article - Zorro The Anti-Victimizer (The comment is now deleted sadly)
    2
  128. Honestly, things like Next and Vite make working with React very likeable.
    2
  129. Agreed, YouTube was a terrible example because its a complex hybrid of both a site and an app.
    2
  130. ​ @dealloc  You can do it using the integrity attribute, it's generally a hash of the script, so any time the script changes and the hash doesn't, it fails to load the script. However in this case it's impossible to do because the script changes based on the user's browser so you can't know the hash in advance.
    2
  131. Two types of people: 1. People who love Tailwind 2. People who hated Tailwind, but love it now (includes me)
    2
  132. I refuse to believe that Jia Tan is a single person, its most definitely a group of people.
    2
  133. Reddit was one last "social media" that was actually good, of course it had the bad sides depending on how you used it, but the resource value Reddit had was Insane. For programmers it was basically Stackoverflow but better.
    2
  134. I have never seen this syntax before, is this done using variants or plugins?
    2
  135. They don't belong in libraries. Libraries are contracts. Contracts which are expected to fulfill particular needs. They should never deviate from their original deliverable without being explicitly clear.
    2
  136. Screw the exploit, I wanna see their Firebase bill.
    2
  137. Serverless is not an ultimate solution, you still want a stateful backend in majority of cases.
    2
  138. Venture Capital, basically a company that gives you money to make money if they think your company has potential.
    2
  139. Respect for making it open source.
    2
  140. Almost half way through, I love that you're completely transparent about using companies that fund your channel. And last but not least, its relieving to see you make the same silly mistakes that I do 😅
    2
  141. What do you mean by 50% open source is fake open source? If you use an open source license on your project it is open source regardless of your personal beliefs.
    2
  142. The incident was an accident, but the gift cards were planned, approved and handed out with an intent. This just goes to show that they care more about saving face than help their customers. Their service costs upwards of $180 per device per month. If you make a very conservative example of a company where 100 devices need Crowdstrike, that's $18k a month. The $10 gift card means absolutely nothing in comparison, if anything it's an insult, a f*** you. If they really want to show that they care, they should waive their service charges for a few months for the affected customers. Anything less would be an insult. Last but not least, this is just wishful thinking, but this should be treated as a cyberattack with Crowdstrike brought to court and held accountable.
    2
  143. What does that mean? CORS doesn't have any significance outside of browsers
    2
  144. I don't think Flutter has as much adaptation or maturity for web to belong in this survey.
    2
  145. We have come full circle haven't we? We started with server side static HTML, it felt too bland so we invented stuff like jquery and dom manipulation libs, manual dom manipulation got too complex so we invented libraries like react, turns out doing everything on client side was a bad idea so now we need to go back to statically generated HTML again.
    2
  146. I think they have a bigger fish to fry at the moment, Yuzu.
    2
  147. No/Low-Code is like wanting a custom painting but then using an image from the internet and printing it using your office printer.
    2
  148. So basically Posthog with a report button?
    2
  149. Thank god he showed the abort signal at the end, because I wouldn't believe Tkdodo would use something hacky as the ignore solution lol
    2
  150.  @iiNoorbd  Kind of hard to not think of your original comment as a shitpost when you start with "Tailwind is for bozos" As for the performance, Your metric of bytes sent seems very inconsistent when comparing different approaches. For example Tailwind will send HTML with inline CSS, so its HTML file may vary in size but the CSS bundle will always be the same. If you use modular CSS, your HTML files will have comparatively smaller sizes but the browser might have to request multiple CSS bundles which may result in multiple HTTP requests. I think we live in an age where its pointless to think of bytes of CSS sent as a performance metric, no matter what approach you use. Unless you're sending 10s of mbs of CSS, in that case there is clearly something wrong.
    2
  151.  @iiNoorbd  "Seems like according to you barely anyone was writing maintainable, reusable and scalable CSS" There. As for my position, I still stand by what I said earlier. Creating a full fledged design system is not easy. If you and your team of devs and designers think its a piece of cake, thats great, you have some nice talent onboard! As for your advice about "Just get better", I have worked with vanilla CSS, SCSS, component / ui libs, styled components etc while they work and do what they say, none of them have allowed me to be more productive than Tailwind, and thats why I will always have a strong opinion of it. Not the point of this conversation, But if someone in my team proposed a different and potentially better way to do things, or if they are having a hard time understanding why we do the things the way we do, I would love to discuss it with an open mind rather than jumping to replace them because they don't want to do it my way. But hey, how others run their teams or company is not my business.
    2
  152. Never wear a cap again please 😂
    2
  153. Wait can someone explain how is it possible for a Chrome extension to redirect Cortana requests which is a native app?
    2
  154. NFL's library naming game is on top.
    2
  155. Good luck! which framework are you going to use to serve your wood shop blog?
    2
  156. Really curios about their business model going forward. I am guessing its hosting or selling commercial licences?
    2
  157. Code should never feel "magical" it should always be reasonably easy to understand. If code is feeling "magical" it just means there are too many abstractions going on that will make it easy to shoot yourself in the foot. This pattern is cool for sure but I haven't seen any real apps using it to actually believe it. Like I have so many questions right now about auth, security etc.
    2
  158. Clickbait title, you can do better than this. But I generally agree with you, there is no need to learn every language from a professional stand point, being super good at one will get you far.
    2
  159. Interpreting Tailwind classes at runtime is asking for bugs. Use something like Class Variance Authority if you want to change Tailwind styles depending on props. And there is nothing wrong with using @apply its there for a reason.
    2
  160. Quoting from a random YouTube comment I read some time ago... "Don't be a frameworker, be a software engineer"
    2
  161. Man this is too complex, I am gonna stick to window.location
    2
  162. This begs the question. Why is it not already a feature.
    2
  163. Not really. I have worked on a website where the UI is contained within resizable panes, so if a user shrinks a pane small enough then they would expect the inputs inside it to shrink accordingly.
    1
  164.  @alexandrecosta2567  In my case it was required for the panes to be "collapsible", so a user can shrink a pane to basically be 0 width or height.
    1
  165. I built a todo app that was connected to the internet!
    1
  166. I don't think S3 is that hard to use. The real problem here is that you think you're on free tier but then magically you're paying thousands of dollars without any notice.
    1
  167. As if a new framework every day wasn't worse enough, Now frameworks are fusing together.
    1
  168. Preserving the tradition of borrowing names from Java: JavaScript SE JavaScript EE
    1
  169. The "hackers" CrowdStrike protects against could only dream of doing a fraction of the damage lol
    1
  170.  @shikharraje  That's the thing though. If concurrency is a feature of your product then it makes sense, look at Google Sheets, Notion etc. Making a guess here, but even they would batch these requests at the least so it reduces the overall load. But when we're talking about an isolated form field that no one except for you is going to see, it doesn't need to be persisted, it resets between sessions or even component mounts - there's no excuse to do this.
    1
  171. Enter ReactQuery Devtools.
    1
  172.  @Gludek  Hmm that's true. Unless you tested on that day then now way to catch it.
    1
  173. It doesn't even have to be something as complex as rolling releases. Something this severe would be easily caught if they actually tried to run their production build.
    1
  174. As a web dev, Basement Studio seems like a nightmare to have as your design team. 😂
    1
  175. I don't understand shadcn/ui, if they want people to build on top of their library then why not go fully headless.
    1
  176. ​ @flickwtchr  what would you call it then? An LLM no matter how big, just tries to predict the next set of token based on the input set of tokens. It doesn't "think" the same way we do.
    1
  177. This looks good for a starter product. The biggest missing piece I notice however is access control. File upload is one problem but who, why and when someone can acces the file is another.
    1
  178. I suggest an alternative name for JavaScript to remove the ambiguity with Java while also highlighting its shortcomings, behold: UntypedScript
    1
  179. Does this mean I can play pre-recorded answers and just pretend to lip sync to fool it? Or better yet, setup my own TTS that takes text from ChatGPT and converts it to audio on the fly. I don't think you would even have to lip sync because there is no way they're making sure the audio is matching with what you're saying. There needs to be a round 2, where you actually fool this tool.
    1
  180. 1:47 What happened with your voice there lol
    1
  181. This decision has Microsoft written all over it.
    1
  182. Pretty sure they don't because on a traditional server there is no setup or teardown of db on each request, instead you'll have a continuous connection or a connection pool.
    1
  183. Enshittification.
    1
  184. "Do not harras this person" "This person needs to be fired and their business shut down" Make up your mind Theo.
    1
  185. ​ @barjo_ At that point it seems like inventing a problem then creating a solution for it
    1
  186. Carcinisation, but its operating systems trying to be Linux.
    1
  187. The censors really make it more interesting.
    1
  188. I can't wait until people optimize the heck out of it.
    1
  189. Excalidraw
    1
  190. React-pdf is nothing but godsend. Our company had a feature to generate pdf reports from our dashboard. For whatever reason, we had implemented the report generation in a cobbled together AWS environment. The problem was, we can't just generate a report and forget about it. In case the related data updated the report also had to be regenerated. Our "clever" solution was to track account activity and regenerate the report in a predictive fashion. It led to the further complication of our AWS infra. The whole solution worked most of the time but as you can imagine there were always some discrepancies where the reports didn't get updated despite the data being updated. We decided against adding a "Generate report" button on frontend because it wouldn't have solved the complexity with our AWS infra. The answer? React-pdf. We simply ditched our AWS solution and wrote a report API that returned all the latest data required for generating a report, then on frontend we just used react-pdf to render the report on the fly. Now customers can update one character in some insignificant field and it would still be reflected in the report instantly, they can generate 100 or 1000s of reports without us worrying about huge AWS bills or out of sync data. As an added bonus we got reports that looked way nicer than what we had, thanks to react-pdf's web-like design system. Someone at the company even managed to get tailwind to work with it! At first everyone was surprised because it felt so simple compared to the AWS monstrosity. It sounded too good to be true at first but we have been waiting to run into any problems for 2 years now. We even have different themes and layouts for reports now and things just work!
    1
  191.  @FrontendSquad  Can you point me to some docs? I can't find anything related.
    1
  192. 6:04 I too wanna die when I run into issues with .js .mjs .cjs .ts .jsx .tsx .mjsx .cjsx I don't even know if .mjsx or .cjsx are real extensions but I am sure we'll invent them as we go.
    1
  193. Excalidraw
    1
  194. So we have CSR, SSR, ISR and now PPR lol
    1
  195. You don't have to sell it to me, I already use and love it.
    1
  196.  @victorstergaard2767  Fair point, I didn't consider that.
    1
  197. I may be biased but I am afraid Microsoft wants to pull off something thats could be considered immoral or unethical with AGIs. Here is my theory Microsoft wants to loosen governance and compliance on the OpenAI tech so they can experiment more freely. The board is not ready to make this trade-off and asked for changes that may hinder Microsoft's projections. Microsoft is not happy with it so they ask Sam to convince the board or make a meet-in-the-middle type of deal. The board remains unconvinced after Sam's attempt. Due to the pressure from Microsoft, Sam tries to move things forward without board's approval or gets an approval on a plan that has intentionally blurred details. The board fires same for "Not being candid in his communications"
    1
  198. I am still having a hard time wrapping my head around tRPC. Is it a full fledged, opinionated server framework? or Just some "middleware" that sits between backend and frontend to guarantee type safety?
    1
  199. "It's like a closure between the server and client" I swear Dan can explain nuclear physics to a five year old in one sentence.
    1
  200. And everyone was wondering why did the State of JS survey came out the way it did...
    1
  201. If I understand it right, Vinxi is a framework to build frameworks? How did we get here?!
    1
  202. I doubt those links lead to actual leaks, it's usually just spam, virus or other ad nonsense.
    1
  203. Reject state management tools, return to useReducer + useContext.
    1
  204. As the kids would say, its a not poggers huge L moment.
    1
  205. 🤨
    1
  206. <div role="<element-name>"> GOD TIER
    1
  207. I am just going to stick to Chrome + Firefox, but I hope the new browser at least doesn't use Firebase.
    1
  208. Never let JS devs think, let alone rethink.
    1
  209. Twitch shot themselves in the foot. Reddit about to strangle itself to death. Twitter is already on a ventilator. This may be the best time for alternatives to pitch in.
    1
  210. Preach
    1
  211. ​ @skayu2000  I have been hearing that since I learned Flutter which was about 5 year ago? Since then Flutter has done anything but gain constant adoption. It's nothing disruptive like React when it came out but it's definitely reached a point where it won't just disappear.
    1
  212. This is a react-native problem not a library problem. If TanStack form uses controlled input it would be broken in the same way.
    1
  213. Please do the world a favor and make something that takes a webp URL or file and downloads it as png or jpeg.
    1
  214. Vercel even took his shirts?! 😭
    1
  215. So use tailwind-prettier on a pre commit hook, gotcha!
    1
  216. This seems like a case-specific optimization which doesn't suite NodeJS.
    1
  217. 27 minutes 💀 I swear Its the same circle jerk but it gets longer everytime. There is hardly anything worth watching left here.
    1
  218. Looks meh. Can't wait for Vercel to release the meta framework for Stylex.
    1
  219. "Reading time: 14 minutes" Video: 1:25:59 Just wow
    1
  220. Not if you want to shrink the content
    1
  221.  @PhillipLippi  I didn't mean that literally. What I meant was that React and a lot of other frameworks with SSR support are basically trying to do what PHP was invented for.
    1
  222. ​​ @st-jn2gk  I know, especially if you have worked with React for so long. It feels like everything React should've been.
    1
  223. That's not feasible because each config file behaves differently and needs to work in a different context. You can't possibly have a plugin that would satisfy all of them.
    1
  224. Someone already opened a PR for TS support lol
    1
  225.  @asemyamak3984  Nothing has changed. React is still going in the same direction.
    1
  226. ​ @alexhein1738  51% means no one can overrule your decision since you would be the biggest shareholder regardless of how the other 49% is spread out. Yes you can also be the biggest shareholder with any % of the shares less than <51% depending on how they're spread out but it doesn't guarantee that someone could acquire more shares than you and overrule your decisions. That's why 51% is the lowest number of preferred shares.
    1
  227. Good lord, how much more jargon do we need.
    1
  228. Who wants to bet that in the next five years server components are gonna be legacy.
    1
  229.  @vanzed7539  The whole point is to create a utility wrapper hook for when you don't need dependencies (aka empty array) and strictly use the said wrapper because there maybe cases where you could forget passing the deps array and the effect runs on each render. When you need deps you'll obviously have to use the vanilla useEffect
    1
  230.  @chocolateimage  Actually a great app for taxis and parcel delivery in India. Can't blame a start up for saving money by picking cross platform.
    1
  231.  @doc8527  I have always felt like serverless didn't really solve any big problems and it was more of a way for cloud providers to increase their compute revenue.
    1
  232. Fun thought experiment: With the same requirements and constraints, how would you do this project with your current knowledge of React? Maybe go one step further than a thought experiment, make a prototype.
    1
  233. 100% agree. Its crazy that most of whats used in real world is generally ignored by universities. If you don't wanna be dumbfounded on the first day of your job, then absolutely learn git.
    1
  234.  @SteelSkin667  I was mainly talking about how JS frameworks have been lately lol
    1
  235. Where is o2?! I hope o2 doesn't turn out to be the evil AI we are all afraid of because OpenAI killed it in its infancy.
    1
  236. 40:23 Why tho?
    1
  237. Are we just calling everything a "x killer" nowadays? lol
    1
  238. Your download speed can only get as good as the server's speed from where you're downloading from.
    1
  239. Not to undermine the effort of any of the contestants, but this video is a perfect example of how overthought and subjective design has gotten.
    1
  240.  @TurtleKwitty  To create a PR on a public repo you have to first fork it on to your account, make changes and then open a PR. That's where apnastudent slash expressjs comes from
    1
  241. ​@avguzr It doesn't matter. As an educator she should not have left any ambiguities in her communication. If you're trying tell someone not to do something then make it very obvious. When learning to drive you don't let someone crash their car and then tell them, oops you weren't actually supposed to do that.
    1
  242. This would not have been a problem with Ladybird.
    1
  243. Backend is not the place where you want too many abstractions, if something is not working then good luck with debugging because there is so much stuff hidden away its impossible know whats broken. This also feels like a nightmare to scale, if you misconfigure one thing you may end up DDOSing yourself. I still think React Query is the peak of innovation when it comes to managing server state on the client side.
    1
  244. Its sad that everyone wants to kill React meanwhile its one of greatest libraries that taught me a great deal of all I know about web dev, seriously. Thankfully its impossible to kill.
    1
  245. What exactly is the create-t3 stack?
    1
  246. I will never understand how Meta's OS side can be so good, while their business side is always being so predatory.
    1
  247. relevant to nextjs because once in the browser nextjs is basically react
    1
  248. I don't trust benchmark these days. Can it tell me how many Rs there are in the word strawberry?
    1
  249. You have little iOS experience if you think it is any better. Both App store and Play Store are cancer, especially for indie and small devs. Also I don't agree with "Don't attribute to malice that which is adequately explained by stupidity" malice and stupidity are not mutually exclusive. Google can definitely be stupid and malicious.
    1
  250.  @noelgallagher3646  React is a wanna be functional program haha
    1
  251. Leave it to React to support a basic web feature after 19 major versions and still have it be practically useless.
    1
  252. Screw you man, for a second I thought you ditched Tailwind for MUI.
    1
  253. React has always boasted about being unopinionated, meaning that it gave you the primitives to build but didn't care about what or how you built with it. This is the same reason why some of the greatest libs like react-hook-form and react-query exist. I say greatest because these libs do one thing and do it perfect, but with react trying to "borrow" bits from them makes it feel like React is blurring its own boundaries. To me, that seems like a step in the wrong direction.
    1
  254. How does react-email differ from MJML?
    1
  255. ASAC Schrader spitting facts
    1
  256. For anyone wondering the site is Gamdom.
    1