@@med5032 except for people who need to write/take notes. People in the audience laying down seems to be progressive simply for the sake of progressiveness, if that makes sense
The 2000 other audience are actually sitting, so just some have the chance to lurk. I think maybe the speaker feels more personal to this small audience, because he can focus on some people and doesn't see the big crowd (getting more nervous eventually)..
Couple of points related to the Svelte part -> * Svelte now supports TypeScript, so the plusOne example will work as normal in Svelte with TypeScript * You can reuse stores with Svelte simply declaring them in one common js file, solved !! ... no drama as mentioned in the Svelte stores part
Just a quick comment on your second point regarding Svelte Stores. I think you missed what he was saying. He did actually mention Svelte stores. He said that the stores API is different from the normal Svelte code you would write in your component. When he said you cant compose functions to share across components he was specifically talking in the context of "without switching to a different syntax like Svelte stores." Where as in Vue you can use the same syntax you use within components to share code across components. If you go to 20:11 where he shows the slide for that point, the slide even states "*cross component logic must use a separate store API" So, the criticism here isn't that its impossible to share code logic across Svelte. Its that you have to switch between multiple APIs to do it. Where as other solutions like Vue or React allows you to reuse logic easier by having a single API that allows for logic composability out of the box.
@@peaksome4392 you cant, but the statically typing of the language far out weighs every other thing that you can come up with against it. btw, debugging and testing is for those who dont write their own DSLs, a very crude way of writing software
7:22 'this' and data-reactive UI components. Departure from classes. Sharing component logic. React, Vue, Svelte.
12:03 Design tradeoffs - React Hooks, Vue Composition API
why audience prostate on floor?
Yeah, I would imagine it affects the speaker in a bad way. Looks comfy for the audience, though.
@@med5032 except for people who need to write/take notes. People in the audience laying down seems to be progressive simply for the sake of progressiveness, if that makes sense
hmm, yeah kinda disrespectful to the speaker i would think with your feet right in his face.. as a developer im happy sitting in a comfy chair
yeah bad thing moreover by lying down, the mind becomes lazy.
The 2000 other audience are actually sitting, so just some have the chance to lurk. I think maybe the speaker feels more personal to this small audience, because he can focus on some people and doesn't see the big crowd (getting more nervous eventually)..
Honestly, I probably would prefer picture-in-picture more on these talks, bcs sometimes it's nice to see the code longer while speaker is talking
me too
Evan, get your glasses sized properly 😅
Couple of points related to the Svelte part ->
* Svelte now supports TypeScript, so the plusOne example will work as normal in Svelte with TypeScript
* You can reuse stores with Svelte simply declaring them in one common js file, solved !! ... no drama as mentioned in the Svelte stores part
Just a quick comment on your second point regarding Svelte Stores. I think you missed what he was saying. He did actually mention Svelte stores. He said that the stores API is different from the normal Svelte code you would write in your component.
When he said you cant compose functions to share across components he was specifically talking in the context of "without switching to a different syntax like Svelte stores." Where as in Vue you can use the same syntax you use within components to share code across components.
If you go to 20:11 where he shows the slide for that point, the slide even states "*cross component logic must use a separate store API"
So, the criticism here isn't that its impossible to share code logic across Svelte. Its that you have to switch between multiple APIs to do it. Where as other solutions like Vue or React allows you to reuse logic easier by having a single API that allows for logic composability out of the box.
Não sabia que existiam "preguiçosas" fora do Ceará :)
O que quer dizer?
@@victorfds O nome dessa cadeira que está no palco chamamos de preguiçosa no Ceará :)
Bacana !!
why these people are lying in front of a god? shame on them
tell you god that those are called "Composition classes"
voted down since Rust can do this far better,
who is still using pathetic JS ?
Ah so you are writing frontend browser code in Rust :-D?
@@matzesox , you should try some rust stdweb examples
Rust is overkill for now. How do you debug webassembly btw?
@@peaksome4392 you cant, but the statically typing of the language far out weighs every other thing that you can come up with against it.
btw, debugging and testing is for those who dont write their own DSLs, a very crude way of writing software
@@theoligarchist1503 You talk like a trump supporter. No point of making logical argument with you.