Nice article! Only one question. Why do you want to use Dart instead of plain JS or TS?
Why do you want to adapt that language instead of one with larger community?
The pull Dart has on me is the fact that as a statically-typed language from the get-go, it also comes with tooling that has made me productive working in it. Dart shines when building applications that can be made sense of while it grows.
I’ve found myself working on large JS projects and I’ve struggled to understand it, due to the fact that JavaScript as a dynamically-typed language means that working out the flow of data and the structure of that data requires more mental effort. I've also struggled to stay ahead of type-related errors on larger projects. The amount of times I’ve right clicked a method in VS Code and used the “Go to definition” command to be met with no feedback, still annoys me today.
TypeScript, however is a good effort by Microsoft to address this concern. My only qualms with this is that TS code I’ve seen looks more like C# rather than JavaScript, especially when you include namespaces and interfaces, so it can be difficult to grasp at times. I would have loved to have seen TS stand on it’s own two feet, rather than be tied to the JS ecosystem. Ryan Dahl seems to be looking into that with his Deno project. This tells me that Dart may have been on the right track by not tying itself too much to the JS ecosystem. I haven't really done much with Flow, so can't comment on that.
This series with Vue.js is an investigation using the js package. I'm not selling any silver bullets. My ideal framework of choice for SPA development would be AngularDart, although I still need to look into it :)
This is beginning to feel like an essay, so I'll leave it at that.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice article! Only one question. Why do you want to use Dart instead of plain JS or TS?
Why do you want to adapt that language instead of one with larger community?
Hey Kovács, thanks for your question.
The pull Dart has on me is the fact that as a statically-typed language from the get-go, it also comes with tooling that has made me productive working in it. Dart shines when building applications that can be made sense of while it grows.
I’ve found myself working on large JS projects and I’ve struggled to understand it, due to the fact that JavaScript as a dynamically-typed language means that working out the flow of data and the structure of that data requires more mental effort. I've also struggled to stay ahead of type-related errors on larger projects. The amount of times I’ve right clicked a method in VS Code and used the “Go to definition” command to be met with no feedback, still annoys me today.
TypeScript, however is a good effort by Microsoft to address this concern. My only qualms with this is that TS code I’ve seen looks more like C# rather than JavaScript, especially when you include namespaces and interfaces, so it can be difficult to grasp at times. I would have loved to have seen TS stand on it’s own two feet, rather than be tied to the JS ecosystem. Ryan Dahl seems to be looking into that with his Deno project. This tells me that Dart may have been on the right track by not tying itself too much to the JS ecosystem. I haven't really done much with Flow, so can't comment on that.
This series with Vue.js is an investigation using the js package. I'm not selling any silver bullets. My ideal framework of choice for SPA development would be AngularDart, although I still need to look into it :)
This is beginning to feel like an essay, so I'll leave it at that.