Lmfao rich harris is a true gem. He says he only knows the basics of git and then minutes later chides the js community for not understanding their tools hahahahhaa. ❤ Rich and svelte
I think Svelte 5 is the first version of Svelte where I can see React devs using it. Svelte 4 syntax was too magical for me but the Runes API gives me the control I need for fine grained reactivity. I think it will be a big hit.
@@WhiskeyWebAndWhatnot Updating a data table with 4k rows and updating only 1 row. A graphical dashboard that updates constantly from push events with large data sets. Updating only 1 object in the array make the UI much smoother.
Are you displaying all 4,000 rows at once? I think most frameworks handle this for you by only rerendering what changed. React does it backwards and rerenders everything all the time unless you use a lot of hooks to tell it what not to rerender.
@@WhiskeyWebAndWhatnot We use a virtual table component we wrote our selves that renders only what is visible and fetches more data from cache as the user scrolls. Still was smoother in Svelte 5 vs. 4 when we tested it.
I like BEM, yes i hate that is that verbose, but if there's something off to fix i can just copy the name of the class from the browser and find it in the source right away even from production, and that alone makes it really worth it despite all the drawbacks.
graphQL makes front end code so verbose. The only way it's truly useful is to compensate a broken back end / front end teams relation. I've been there dreaming about adding one f-in field in some API instead of having to bundle data into a page builder content or even worse, code. Some companies have no functional management, so half of the data used by front end are literally smuggled into the viewport by back channels. In a way graphQL forces management to give the front end teams some responsibility about data models and access. It still doesn't create things that are not found is DB but at least you don't need to wait for the 6 month delay to complete a simple API refresh task.
Lmfao rich harris is a true gem. He says he only knows the basics of git and then minutes later chides the js community for not understanding their tools hahahahhaa. ❤ Rich and svelte
Woah, woah, woah he was talking about other devs not himself 😝
Your producers were late .
You speak truth my friend 😂
Cricket is also big in UK.
Please we need some cricket people also in tech 😅
You’ll have to convince Chuck to like it more than football 😝
I think Svelte 5 is the first version of Svelte where I can see React devs using it. Svelte 4 syntax was too magical for me but the Runes API gives me the control I need for fine grained reactivity. I think it will be a big hit.
Do you have an example of something that needs fine grained reactivity control?
@@WhiskeyWebAndWhatnot Updating a data table with 4k rows and updating only 1 row. A graphical dashboard that updates constantly from push events with large data sets. Updating only 1 object in the array make the UI much smoother.
Are you displaying all 4,000 rows at once? I think most frameworks handle this for you by only rerendering what changed. React does it backwards and rerenders everything all the time unless you use a lot of hooks to tell it what not to rerender.
@@WhiskeyWebAndWhatnot We use a virtual table component we wrote our selves that renders only what is visible and fetches more data from cache as the user scrolls. Still was smoother in Svelte 5 vs. 4 when we tested it.
I like BEM, yes i hate that is that verbose, but if there's something off to fix i can just copy the name of the class from the browser and find it in the source right away even from production, and that alone makes it really worth it despite all the drawbacks.
Wouldn’t the same be true without BEM if you named your classes uniquely?
@@WhiskeyWebAndWhatnot yes, BEM only makes it very easy to have a unique name
graphQL makes front end code so verbose. The only way it's truly useful is to compensate a broken back end / front end teams relation. I've been there dreaming about adding one f-in field in some API instead of having to bundle data into a page builder content or even worse, code. Some companies have no functional management, so half of the data used by front end are literally smuggled into the viewport by back channels. In a way graphQL forces management to give the front end teams some responsibility about data models and access. It still doesn't create things that are not found is DB but at least you don't need to wait for the 6 month delay to complete a simple API refresh task.
Definitely not the ideal setup
KitQL
www.kitql.dev/docs
Postgraphile
www.graphile.org/postgraphile/introduction/
Hasura
hasura.io
Rich Harris, if you're a home cook, I'll share when I had kids I had to become a proficient short order cook 🍳
Rich: I can dance but I do not drink. Robbie and Charles: !