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

  1. You couldn't make a less obvious ad lol
    12
  2. Oracle should also discontinue itself while they're at it.
    12
  3. 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
  4. 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
  5. 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
  6. Finally some real innovation in this field. Super hyped for Bun.
    11
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. More like respect for EU increased.
    9
  14. Turbopack + Next13 is going to be even better if we take Vercel's word on Turbopack. Granted its still very early for Turbopack.
    8
  15. The wrapper gave me class based components ptsd, hope it gets fixed soon.
    8
  16. *Insert Ryan Gosling Blade Runner meme*
    8
  17. 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
  18. I think you mean Chromium not Chrome.
    7
  19. ​ @t3dotgg  Where are the leaks, I checked the closed issues I can't find it.
    6
  20. In a month, Vercel could make a meta framework for LLRT
    6
  21. Solid point
    6
  22. They also own Tumblr
    6
  23. Its mind blowing that React is going to be the next PHP 😂
    6
  24. And the only good feature
    6
  25. 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
  26. 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
  27. Oh my god
    5
  28. Theo has almost gone full circle.
    5
  29. Now I am actually wondering, what would happen if the internet only dropped during the first few keypresses when typing something.
    5
  30. 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
  31.  @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
  32. ​ @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
  33. I don't know if I should laugh or cry.
    4
  34. 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
  35. 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
  36. Legend. Thanks.
    4
  37.  @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
  38. Same lmao
    4
  39. Looking at the comments, he wasn't joking about dying on this hill lmao
    4
  40. Yes, Serverless does scale effectively infinitely, but that means It's cost will also scale infinitely, and that is a scary thought.
    4
  41. Its the way of life.
    4
  42. 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
  43. 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
  44. 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
  45. You can have trademarks for colors? Wtf.
    4
  46. 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
  47.  @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
  48. Always use burner cards for hobby projects.
    4
  49. 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
  50. Exactly my thought! This is a dead simple use case for AI and they're failing it
    3