The Most Hyped JavaScript Of 2023 

Loving it!!

The clickbait is getting too cringe and the videos are just noise about what's happening in the js world. Theo's channel is ironically experiencing enshittification. You can see he's just making videos for the sake of making videos.

​@@skyhappy the best decision in my life was to leave react and move into backend professionally

@@skyhappy Yeah. It has gone downhill.

​@@skyhappy yeah, i understand the clickbait is needed for the engagement but i certainly don't feel respected as a subscriber when I read it

Cool site

Same! I wanna know if i should bail now cuz I am using it for my SHADCN haha

I'm not a fan of storybook either - my guess would be - he doesn't like the boilerplate needed + it's a massive dependency for what it is. A normal react-app node_modules is like 40,000 files - install storybook, and suddenly it's 100,000 !!!!

Same. If you work together with a design team, I think figma + storybook is a great combo. A little troublesome to make it effective in terms of process, but I wouldn't blame the tooling.

I created a shadcn component library with storybook and next js client and server separation

If you're not using storybook as a separate package then I understand that you don't like. They're also not great att communicating how you should set it up in your projects. A common setup I see is creating a "workshop" package in your monorepi. Disregarding the setup though, when it's up and working it's a godsend in projects with size and scope that requires it. Some of the pros include: - No need to trigger edge cases, e.g. fail states, to develop UI components to handle those cases. - After you have developed your UI using storybook, stories describe some of the edge cases you expect and support, no need to question "do we handle this" 6 months down the line and then try to go and trigger it to find out. - If your app doesn't hot reload, or takes a while to load in general (e.g. slow apis) storybook still enables an instant devloop. - In my experience, storybook enforces better component interfaces/props as a side effect. It's much harder to just "add another prop to fix my need" when it doesn't make sense to do so. - It also forces you to ensure that components work in isolation. No weird styling reuse that risk breaking and no side effect abuse of the global scope.

Don’t worry, it will all change again next month.

I was quite interested in using appsmith, mind sharing why you switched from appsmith?

Storybook is great. It's a bit strange to get up and running but if you're at a company/project with a need for it, just go for it. We've decided to wrap it as a tooling module in our monorepo with custom scripts wrapping storybook-cli (this allows us to dev-depend on it without installing it in every frontend project). Imo that's the way to go

He talks about this in his video where he celebrates the launch of the new t3 docs launch.

Go and htmx go hand in hand today 😂

@@more-sun yup. It's a great combination even if combined with templ

yes, mobx is amazing ❤

This generation of engineers don't have a clue about web design. That's why it's so complicated. They find problems to fit the tools they know, not the other way around.

skill issue tbh

@@levyroth I like that take.

@@asdasdasdasdss8603 likely

@@asdasdasdasdss8603 oh yeah, for new people it's a skill issue when they google what to use and they hear people having 1000 options and the poor person is like "what now", and nobody tells them "learn what the local job market requires at first to get a job"

Previous NestJS users for a few years around 2020. I left when I realized NestJS uses every single day to day packages we already have, and I already structure my projects just like NestJS without the need for NestJS. When using NestJS you just waste extra time if you already know how to build a good structure for projects. If you don’t know good structuring for projects, then use NestJS. It will teach you well. But I built TRPC in the same structure as NestJS with type safety from typescript, and I don’t have to rely on NestJS first party dependencies waiting to be up to date as the dependency package anymore, or get slowed down by their opionated nature.

@@kodekorp2064 Thank you for the insight. How do you achieve end to end typesafety? With monorepo?

I just don't know how to run rust go is genuinely just easy to learm

Python is slow , maybe we can retry the approach in nim.

hi

I don't foresee that happening purely cause he's a web dev instead of software/desktop dev.

Looks like they’re in the same space as MUI but worse?

@@azizsafudin no definitely closer to Shadcn if not better try it before you have an opinion