For me, working with Dart is a lot linear, since the necessary tooling are provided by the Dart team. Because it's a typed language, being productive in little time is easier, especially when combined with the range of utilities that come as part of the SDK. I can also use JavaScript libraries in my Dart web apps.
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
Thanks for the reply, so I work with Typescript 99% of the time, from experience, I need to get a definition file in order the use them in TS in a meaningful way. How does this compare?
Is there a reason to consider Dart over TS? What is the coverage for the JavaScript library ecosystem in pub, have you had to make decisions based on what is in the pub repo.
from experience, I need to get a definition file in order the use them in TS in a meaningful way. How does this compare?
Similarly, a definition file is needed to use JS libraries in Dart. You can create one yourself with little effort. Furthermore, you can use this tool developed by the Dart team to convert TS definitions to Dart.
Is there a reason to consider Dart over TS?
Dart and TypeScript are both attempts to address the shortcomings of native JavaScript. I would consider Dart especially in the area of mobile app development with Flutter. Dart can be compiled to native ARM code, which is good for performance.
The pull with Dart here is the tooling and utilities that come with it, not just the language. I find with TypeScript that one can fall into the trap of writing code that looks too much like C# than JS, which tells me Dart may have been the right approach, implementing conventions that programmers use and love without being bound to the constraints of JavaScript.
What is the coverage for the JavaScript library ecosystem in pub, have you had to make decisions based on what is in the pub repo.
Haven't got any numbers on that one I'm afraid. There are Dart packages that act as wrappers over JS libs, using the js interop package I covered in my tutorial. I found examples like Google Maps and ChartJS, although you can make your own using the tools provided.
Thanks for your questions. I'm up for suggestions on any future topics you wish for me to cover. Message me on Twitter 🐦.
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
Before Dart as it is today, Dart was going to be a replacement for JavaScript (in Googles mind), There is a Dartium version of chrome that ran Dart 1. The decision was made to rebirth Dart into what it is today, but I see that the JavaScript compiler exists. So the idea is not dead, just different.
The dart2js compiler to JavaScript is necessary if we need to develop apps that run on the web. An aim with Dart 2 was to improve the tooling geared towards clientside development. They wrote about this on their Medium blog.
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.
For me, working with Dart is a lot linear, since the necessary tooling are provided by the Dart team. Because it's a typed language, being productive in little time is easier, especially when combined with the range of utilities that come as part of the SDK. I can also use JavaScript libraries in my Dart web apps.
Thanks for the reply, so I work with Typescript 99% of the time, from experience, I need to get a definition file in order the use them in TS in a meaningful way. How does this compare?
Is there a reason to consider Dart over TS? What is the coverage for the JavaScript library ecosystem in pub, have you had to make decisions based on what is in the pub repo.
Sorry to go off topic here @Kinyanjui.
Similarly, a definition file is needed to use JS libraries in Dart. You can create one yourself with little effort. Furthermore, you can use this tool developed by the Dart team to convert TS definitions to Dart.
Dart and TypeScript are both attempts to address the shortcomings of native JavaScript. I would consider Dart especially in the area of mobile app development with Flutter. Dart can be compiled to native ARM code, which is good for performance.
The pull with Dart here is the tooling and utilities that come with it, not just the language. I find with TypeScript that one can fall into the trap of writing code that looks too much like C# than JS, which tells me Dart may have been the right approach, implementing conventions that programmers use and love without being bound to the constraints of JavaScript.
Haven't got any numbers on that one I'm afraid. There are Dart packages that act as wrappers over JS libs, using the
jsinterop package I covered in my tutorial. I found examples like Google Maps and ChartJS, although you can make your own using the tools provided.Thanks for your questions. I'm up for suggestions on any future topics you wish for me to cover. Message me on Twitter 🐦.
I didn't know you can use Javascript libraries in Dart. That's really cool.
Before Dart as it is today, Dart was going to be a replacement for JavaScript (in Googles mind), There is a Dartium version of chrome that ran Dart 1. The decision was made to rebirth Dart into what it is today, but I see that the JavaScript compiler exists. So the idea is not dead, just different.
The
dart2jscompiler to JavaScript is necessary if we need to develop apps that run on the web. An aim with Dart 2 was to improve the tooling geared towards clientside development. They wrote about this on their Medium blog.