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

  1.  @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
  2. Never wear a cap again please 😂
    2
  3. Wait can someone explain how is it possible for a Chrome extension to redirect Cortana requests which is a native app?
    2
  4. NFL's library naming game is on top.
    2
  5. Good luck! which framework are you going to use to serve your wood shop blog?
    2
  6. Really curios about their business model going forward. I am guessing its hosting or selling commercial licences?
    2
  7. 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
  8. 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
  9. 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
  10. Quoting from a random YouTube comment I read some time ago... "Don't be a frameworker, be a software engineer"
    2
  11. Man this is too complex, I am gonna stick to window.location
    2
  12. This begs the question. Why is it not already a feature.
    2
  13. 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
  14.  @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
  15. I built a todo app that was connected to the internet!
    1
  16. 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
  17. As if a new framework every day wasn't worse enough, Now frameworks are fusing together.
    1
  18. Preserving the tradition of borrowing names from Java: JavaScript SE JavaScript EE
    1
  19. The "hackers" CrowdStrike protects against could only dream of doing a fraction of the damage lol
    1
  20.  @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
  21. Enter ReactQuery Devtools.
    1
  22.  @Gludek  Hmm that's true. Unless you tested on that day then now way to catch it.
    1
  23. 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
  24. As a web dev, Basement Studio seems like a nightmare to have as your design team. 😂
    1
  25. I don't understand shadcn/ui, if they want people to build on top of their library then why not go fully headless.
    1
  26. ​ @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
  27. 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
  28. I suggest an alternative name for JavaScript to remove the ambiguity with Java while also highlighting its shortcomings, behold: UntypedScript
    1
  29. 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
  30. 1:47 What happened with your voice there lol
    1
  31. This decision has Microsoft written all over it.
    1
  32. 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
  33. Enshittification.
    1
  34. "Do not harras this person" "This person needs to be fired and their business shut down" Make up your mind Theo.
    1
  35. ​ @barjo_ At that point it seems like inventing a problem then creating a solution for it
    1
  36. Carcinisation, but its operating systems trying to be Linux.
    1
  37. The censors really make it more interesting.
    1
  38. I can't wait until people optimize the heck out of it.
    1
  39. Excalidraw
    1
  40. 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
  41.  @FrontendSquad  Can you point me to some docs? I can't find anything related.
    1
  42. 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
  43. Excalidraw
    1
  44. So we have CSR, SSR, ISR and now PPR lol
    1
  45. You don't have to sell it to me, I already use and love it.
    1
  46.  @victorstergaard2767  Fair point, I didn't consider that.
    1
  47. 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
  48. 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
  49. "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
  50. And everyone was wondering why did the State of JS survey came out the way it did...
    1