Mostly it depends on how stable it is and would there be any gains if I start ewvaluating this stuff at the moment.
For e.g.
In the JavaScript ecosystem, incorporating TypeScript in projects is gaining a lot of trend and rightly so as it is a great addition to the codebase to obtain compile-time errors. It has been implemented and used by lots of folks so diving into that would be easy as help isavailable there too.
But consider Deno, it's quite new, so getting help is a bit diffucult, there's no interop with NPM packages so you need to create those on your own. These are some points that make me not want to learn Deno as that wouldn't be helpful personally or in my organization. There wouldn't be any added advantages to my skillset that I could show.
This is my approach on how one should evaluate new technology.
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.
Mostly it depends on how stable it is and would there be any gains if I start ewvaluating this stuff at the moment.
For e.g.
In the JavaScript ecosystem, incorporating TypeScript in projects is gaining a lot of trend and rightly so as it is a great addition to the codebase to obtain compile-time errors. It has been implemented and used by lots of folks so diving into that would be easy as help isavailable there too.
But consider Deno, it's quite new, so getting help is a bit diffucult, there's no interop with NPM packages so you need to create those on your own. These are some points that make me not want to learn Deno as that wouldn't be helpful personally or in my organization. There wouldn't be any added advantages to my skillset that I could show.
This is my approach on how one should evaluate new technology.