The Beginning of the End ? Deno vs Node.Js
Creator of Node.js regretted !
Yes you heard that right , But WHY ?
Ryan Dahl creator of Node.js thin...
For further actions, you may consider blocking this person and/or reporting abuse
Deno is cool, but after playing with webassembly and working a webdev internship with a python backend Im curious if the future of JS will come to expiration soon
Python, no doubt is a great language but it is more like what is more suitable for your requirements ? and which defers case to case.
The decision not to support npm and the existing huge collection of npm packages makes it seem unlikely it will be a serious choice for some time to me. Feels like it lacks a killer feature - the closest it has is native TypeScript support - but hmmm, not sure that's actually very compelling.
heh, your evaluation criteria seems freelancer focused. Node/NPM is a black hole security wise; Typescript shouldn't optional (though I dislike Angular's approach) and have I mentioned the security problems (cause they're a big deal)?
Well I'm not a freelancer and I spend a great deal of time on security considerations and pen tests as it sounds like you do :) I'm happy with the balance we have now between security and accessibility of modules to speed development. If deno becomes a thing then the security is a significant improvement I grant you, but not sure how having potentially multiple versions of different modules sub referenced is going to help?
Typescript - already doable is my point. Out of the box is nice.
By me,this is the bigest improvement in security,npm registry allows to much unchecked modules.
I'm very intresting by the technology behind Deno and the learning of TypeScript, but I think package.json and the NPM library is not a very bad thing, it's very helpfull when you need something and you don't want to loose 5 hours to search about it!
me too, problem being "we have a security department" and "I work at a power utility". Ain't no flippin way anyone wants that black hole on our internal network (interns do bring it up, often .. like we don't know it exists :-).
Yeah of curse it's understandable!
I think it's good to start track this tech from it's birth I will say in the next 5 years it will be a thing.
Absolutely right, its in early stage but has great potential.
The differences you've pointed out are almost entirely "require" vs "include".
The latest node supports es6 modules natively, which mostly closes this gap.
So, other than typescript, it's hard to see any illustration here of any difference that actually matters.
I'd work on making those differences which matter more clear, to support your argument.
The npm eco system is a poisonous snake in the grass next to the poppy fields of free software.
Makes me love the Laravel backend ecosystem even more! Would never build a backend for a web app on Node or Deno for that matter!