I am a Full stack .NET Developer, I like to work with C#, Asp.Net Core, SQL, Mongo DB, Azure, JavaScript...
Always eager to learn new technologies. I am here to share, ask & eventually learn.
Now we are searching for 3rd party router, in this case Isn't Angular better, all libraries in one place ? Is Angular is for large apps and React and Svelte for small apps ? What do you guys think ? @khrome83@softchris
It is the same with React, no official router. At one point there were 4 routers.. I would say this: there are two different mentalities here. Get everything you need = Angular vs React/Svelte = let the community build what's missing. Ultimately use what works for you. I see different audiences here for Angular I see an enterprise audience that is used to great tools/types etc.. with other frameworks it's more down the specific lead dev what choices are made on approach and which 3rd party library.. As I always I would say it depends... I've seen large React apps as well... :)
I slightly disagree here. I think the author of Svelte, Rich Harris, very liked jQuery because it had (nearly) everything included, and made Web development easy: everything was documented in one place, the jQuery API docs.
I think Svelte tends to get to this point, he already included a store and transitions. A router might be included at some point, if it doesn’t conflict with Sapper.
At the end, what you don’t use is not included in the bundler, so it a win/win for the developer and the end user!
I am a Full stack .NET Developer, I like to work with C#, Asp.Net Core, SQL, Mongo DB, Azure, JavaScript...
Always eager to learn new technologies. I am here to share, ask & eventually learn.
Think you misunderstood, everyone is using tree-shaking.. What I think he meant was that Svelte will probably move in a direction where it becomes more of an app framework than a library, all critical parts should be there.
Now we are searching for 3rd party router, in this case Isn't
Angularbetter, all libraries in one place ? IsAngularis for large apps andReactandSveltefor small apps ? What do you guys think ? @khrome83 @softchrisIt is the same with React, no official router. At one point there were 4 routers.. I would say this: there are two different mentalities here. Get everything you need = Angular vs React/Svelte = let the community build what's missing. Ultimately use what works for you. I see different audiences here for Angular I see an enterprise audience that is used to great tools/types etc.. with other frameworks it's more down the specific lead dev what choices are made on approach and which 3rd party library.. As I always I would say it depends... I've seen large React apps as well... :)
I slightly disagree here. I think the author of Svelte, Rich Harris, very liked jQuery because it had (nearly) everything included, and made Web development easy: everything was documented in one place, the jQuery API docs.
I think Svelte tends to get to this point, he already included a store and transitions. A router might be included at some point, if it doesn’t conflict with Sapper.
At the end, what you don’t use is not included in the bundler, so it a win/win for the developer and the end user!
We'll just have to see how Svelte develops then :)
Good 😄 , So you mean In
AngularandReactwhat we don’t use is included in thebundle.jsfile ?Think you misunderstood, everyone is using tree-shaking.. What I think he meant was that Svelte will probably move in a direction where it becomes more of an app framework than a library, all critical parts should be there.
Yeah I agree with Chris.
I will say that I see a lot of benefit for Svelte across organizations of any size. It’s just simply smaller bundle for users and less code overall.