21 ms·

What’s the killer feature that will lead to node developers switching over in droves?

kybernetikos 6y ago
It's just so different, lots of people could claim different killer features. A strong contender for one section of the community might be the first class typescript support. Other people might like the way you can run so much from a single executable. Anyway, node is a pretty mature platform now, if it dies, it'll die like java-the-language is dying. Very very slowly, and with parts of its platform holding out much longer than other parts. Or alternatively it'll evolve and slowly adopt things from other ecosystems. I don't think we're at the stage where we can say that a bet on deno is definitely right, but it has a lot of interesting ideas and lots of people will be picking it up where they can. If you're interested in the difference between node and deno, check out the talk '10 things I regret about Node' https://www.youtube.com/watch?time_continue=1&v=M3BM9TB-8yA&feature=emb_logo https://www.youtube.com/watch?time_continue=1&v=M3BM9TB-8yA&...
- silentprog 6y ago
  Since when is java slowly dieing?
  - andai 6y ago
    It's been 3 billion devices for twenty years :)
  - snazz 6y ago
    Java mindshare has been dying for a long time. That said, it's still taught in schools and all sorts of companies still use it (including "cool" ones like Google and Apple).
    - The_Colonel 6y ago
      Java mindshare might be slowly shrinking but it is very, very far from dying.
      - rektide 6y ago
        I'd ask, what is sustaining java? Where are the replacement techies picking up the torch, where are youngsters seeing java? I have some answers. It's not a lost cause. Death is not likely, & I do appreciate a lot of java (cdi rocks, microprofile is doing great, performance is good, it has excellent big data tools & many serious pieces of infra are built with it). But how java can retain liveliness, over time, & how the experience & knowledge base continues, is a real challenge. Being on Android helps a lot but also it's a radically different immensely unlike the server side world, with its own elaborate platform specific architectures & libraries. There's not a lot of places java has a hold on UI/ux centered systems, outside Android, so it risks becoming too invisible.
        pjmlp 6y ago
        When SAP rewrites their stack to something else other than Java, Amazon or Alibaba stop contributing to Java, then I start worrying. Microsoft decided that Java death is so imminent that they are now an OpenJDK contributor, collaborate with Red-Hat on VSCode Java support, have bought jClarity and Java has first class support on Azure.
        doteka 6y ago
        I guess a Roman, asked circa 300 AD how he feels about the decline of the empire, would have replied similarly. Java’s mindshare just isn’t where the exciting things in this field are happening. It’s more the domain of overengineered “big data” platforms and clunky enterprise software. Yes, SAP employs a ton of java developers I’m sure, but many devs would rather switch careers than work on anything resembling a crufty ERP. Thus, the ecosystem stagnates, due to the dead see effect - everyone who could push it forward into new areas has no interest being anywhere near it. And stagnation is a long, drawn out death all the same. It still has a ton of momentum, and millions of outsourcing devs who only know Java, so it will be with us for a while - but make no mistake, the decline started quite a while ago.
    - nzly 6y ago
      It is nothing about Java or even mindshare, it is all about money, shareholders, new companies, or even just have to reshape a wheel again. This type of subject is a pseudo-proposition. When many people are using Java, some guys need to create something new (may not really new) to gain the financial interest. Of course they have to pick up something bad about Java or whatever languages and then fill his new stuff in the marketplace, but actually nothing really new. C, C++, Java, Php, Ruby, Python and do on. When everyone is familiar with something or know something for long, the capital and money stop moving, which is bad for game players such as new companies in Silicon Valley and money makers from Wall Street.
    - spiritwander 6y ago
      java is not platform-dependent,it is a platform..
  - kybernetikos 6y ago
    Well, part of my point is that it's very very slow, and because of that, there are all kinds of points I could pick for 'since when'. Maybe I'd pick when apple removed the default install from mac os, or maybe I'd pick when browsers made it impossible to run applets, or maybe I'd pick when the major java IDEs started pushing other languages like kotlin or xtend, or maybe I'd pick the oracle acquisition (never a good thing), or maybe I'd pick the release of go - a language squarely targetting pretty much the only niche that java has left (enterprise development of servers by mixed ability teams), maybe I'd pick the point when java development felt like it became more like configuring metadata for frameworks than actually coding, or maybe I'd pick when google started showing kotlin as the default language for developing on Android rather than Java. Here's google trends for java: https://trends.google.com/trends/explore?date=all&geo=US&q=java https://trends.google.com/trends/explore?date=all&geo=US&q=j... Java-the-language is not going away any time soon, but if you expect it to do anything except decline, I think the future will be disappointing.
    - pjmlp 6y ago
      Yep, so much decline with 80% of the mobile phones, even if it is based on Android Java, on top of which do you think all Android tools run on? Then do you think the likes of SAP, Adobe, Amazon, Azure, Ricoh, Gemalto, PTC, Azul,.... are going to port their golden eggs to Go now?
      - sinsterizme 6y ago
        This doesn’t refute his point, Java the language is separate from the JVM. And those big companies will follow the decreasing Java usage trend due to developer supply and demand. Anecdotally, it seems pretty obvious some of those companies are already doing this by writing new stuff in other, better languages when possible! To me that’s a good indicator a language is slowly dying, maybe you use a different definition.
        andyroid 6y ago
        Pretty much any language running on the JVM will make it dead simple to import and use libraries written in Java - in fact one of the main reasons to choose the JVM is the huge amount of high quality libraries available. So while true that Java != JVM, it’s not as simple as that either.
  - findjashua 6y ago
    JVM as a platform is doing just fine, but other JVM languages seem to be taking over Java’s territory: 1. Kotlin replaced Java for Android development 2. Scala has become the primary language for some of the major tools in the data stack - spark, kafka etc I’m sure there are other examples as well
    - pjmlp 6y ago
      Java is going away from JVM as much as UNIX is loosing C. 1. Politics due to how Google screwed Sun with Android Java 2. Scala is a tiny dot on JVM world and it remains to be seen how Scala 3.0 will be taken up, specially if Python like syntax is actually adopted
      - reader_mode 6y ago
        Well UNIX (or Linux more importantly) is "losing" C, C++ and more recently Rust are slowly displacing it. It's still probably going to be the ABI everything is based on but the language itself is not a first choice for many and that number is increasing over time. Is that what you were implying ? It doesn't sound like it from the rest of the comment because you seem to disagree that Java is losing mindshare on JVM.
        pjmlp 6y ago
        First get a UNIX clone to take over the world written in something else other than C.
        bitwize 6y ago
        https://redox-os.org https://redox-os.org
        pjmlp 6y ago
        That is not an UNIX. Having some level of POSIX compliance doesn't turn an OS into UNIX, unless you mean Windows is a UNIX as well.
  - pjmlp 6y ago
    It is a HN thing, on my circles the choice is only Java or .NET and it isn't going to change for years to come. Java is dying so fast than nowadays even Microsoft contributes to OpenJDK, having bought jClarity in the process.
    - nullsense 6y ago
      Where I am it's largely dominated by Java and .NET with bits of other languages here and there. I jumped ship to .NET after Oracle changed their licencing. I don't like them as a vendor and don't want to be tied to them. Java will still live to a pretty ripe old age but it does feel like it's a little over the hill nowadays.
      - pjmlp 6y ago
        As if Microsoft would be an angel vendor. .NET Core also doesn't run in all platforms where there is a Java implementation and not everyone is happy to rewrite their .NET Framework into Core, while Microsoft is in mix of leaving again stuff behind like the ongoing discussions about CoreRT, .NET Native, Project Reunion, MAUI vs Blazor vs WPF vs Forms show.
        nullsense 6y ago
        Cool. I'm happy enough with it all, so that's me sorted.
      - lenkite 6y ago
        The problem with .NET is that Microsoft have a proven history of seeing the next shiny over the hill and dropping support for existing frameworks and libs while the "new and improved" framework is rolled out. See ! This way is better! Well, until the next better way comes up within a few years. I know of teams who have moved to Java simply to avoid the churn. Many folks prefer the boring but stable Java ecosystem.
  - Shorn 6y ago
    You're on HN. If it's not growing explosively - it's dead. Do I really need a "/s" here?
    - alephu5 6y ago
      As well as this, I think it's also perceived to be a clunky old language. Our modern languages have much more ergonomic build systems, are much less verbose and have coding conventions tailored to modern tastes. This is important, so I predict that over the next few years, as the 20-30 year olds of today gain more senior positions, they're going to choose python, JavaScript, kotlin, golang or rust for new projects.
- throwaway189262 6y ago
  Java is still the best choice for many backend systems. C# and Go still don't have nearly the breadth of open source libraries available. And performance between the three is very similar, besides Java's new GC's are far better. For a majority of enterprise type integrations, which I would argue are the majority of software projects, Java and C# are still the only viable choices. And I don't see that changing any time soon. Go and JS haven't really touched that space despite widespread use for webapps. If you need a big enterprise MMORPG type system with tendrils reaching across the cosmos into your stagnant data ponds, creaky AS400, and React customer facing mirage, Java is the legendary weapon. It's your only choice, your destiny.
  - ornornor 6y ago
    > React customer facing mirage Nice
benatkin 6y ago
It's better aligned with browser technology and with Rust. I think that in time it will run JavaScript apps that depend on browser APIs and/or Rust APIs better than Node. If it also leads to lots of people switching to Rust I don't think Deno's creators would have a problem with that.
- nickcox 6y ago
  > I think that in time it will run JavaScript apps that depend on browser APIs and/or Rust APIs better than Node Yes! For example, you get fetch out of the box.
ecmascript 6y ago
For me its: - Support for "browser" apis like fetch and ES modules. - Security - No NPM necessary, just import code like a browser would - No political agenda is being pushed, they simply focus on the tech The only thing I really miss from node is the cluster api.
- iknowstuff 6y ago
  What political agendas have you had a problem with in other projects?
  - Ayesh 6y ago
    I suppose the elephant in the room is Ryan and npm inc.
  - ecmascript 6y ago
    The node.js has a big blm banner for example and claims that white surpremacy and police brutality is global issues when it's really just very US-based. I just don't see how that has anything to do with javascript development.
    - true_religion 6y ago
      It takes different forms. In the US, the it was slavery, segregation and today police brutality and ideological oppression. Yet the US, isn't alone in this. It never has been. For example, although the famous poem Whiteman Burden was about the American-Phillipine war, it was written by a British poet based on his view of British Imperialism. That legacy of colonialism lives on today throughout everywhere in the English speaking world. As for the French, the less said about how they exploit the CFA zone countries, the better. The Russians? Currently the leaders of European racism. This isn't simply a topic isolated to a parochial country, far far away from the ideologically pure Old World. What occurs in the US was merely a Flashpoint.
      - ecmascript 6y ago
yulaow 6y ago
I am involved in a lot of nodejs communities here in EUW and no one is even talking about deno recently. In my twitter feed the only ones talking about it are those who are asking themselves why it was so over-hyped The adoption is basically nil.
- mosselman 6y ago
  What are you trying to say? You come over as being threatened by either Deno or parent comment or both. What are your thoughts on Deno then, besides that people around you are not talking about it?
  - yulaow 6y ago
    I don't understand your questions nor your tone. [edit: see posts below, I understand now. Sorry I misread the parent post] I was just contesting the assertion of "switching in droves" by parent post. Find me a case of a nodejs community "switching in droves" to deno if you know some, or even a high impact project in nodejs currently switching to deno, if your intention is to assert that parent's assertion is correct. My thoughts are that atm there is no reason to switch your project(s) to it and that, for the features Deno offers right now, it was indeed severely overhyped
    - sturadnidge 6y ago
      The OP didn't assert anyone was switching in droves... they were asking what feature of deno would _cause_ that to happen.
      - yulaow 6y ago
        You are right, I misread. My bad on this one. Now I understand why the other user was curious about the way I answered.
  - TheRealPomax 6y ago
    No they don't? They're pointing out that anecdotally, Deno seems to be a non-player right now. Which is pretty spot on: it's still very new, and hasn't found a critical application yet (e.g. would Node have taken off the way it did without Express? Probably not). So right now, it's an enthusiast's plaything, even if the architectural principles are much cleaner (wrt modern JS) than Node can ever become - without a rewrite so drastic it'll split the Node community like Perl 5/6 or Python 2/3, at least.
programmarchy 6y ago
Types and saner dependency management
rektide 6y ago
> What’s the killer feature that will lead to node developers switching over in droves? The killer feature is that it offers nothing new or distinguishing. It looks like other JS elsewhere. It offers WebSockets via the same sort of WebSocket support you'd have in the browser. You read files via the FileReader api you'd use in the browser. The killer feature is native developers who have an easy te embedding or writing add-ons for deno, not end of line developers. This killer feature / mass adoption mindset is such an ugly poison. The size of a community is far down the list of considerations, a proxy only for easy consumability & fitting within current pop-culture sensibilities myths & current styles. Think different. Look for what really may matter.
forty 6y ago
I have been running nodejs in production since 0.6 (2012) and I'm not emotionally involved with nodejs, being actually a scala person who happened to work on a nodejs project. I'm curious and interested by new things, so I looked at deno with interest. And honestly, for now, I don't see a single practical benefit that would make me switch over. I'm still happy that deno exists, experiment is good and if they ever find something that could make nodejs better, then it could be used to actually improve nodejs, which everyone will benefit from.
sktrdie 6y ago
Permissions for anything from local files access to network.
royletron 6y ago
It has string padding built in...
- TheRealPomax 6y ago
  So does Node? The joke stopped aging well after ECMAScript updated the spec for String with a padStart function, among many other improvements to the String type.
  - royletron 6y ago
    party pooper.
rhacker 6y ago
You asked. Minimally: * module management that isn't in the code. * lock files that are not an afterthought. That all being said, even if it were true, I get the user experience of deno with ts-node, and the package.json and lock file support is free.
golergka 6y ago
For me, two small things that haven't yet been mentioned here. Dependency management that's much more friendlier to forks. Very often I want to patch something small in a public NPM library and point my company's private project to the fork that contains that patch, not having to wait for the maintainer to accept the PR. Publishing a separate private or public version of this is still a chore. Typescript support. The current "building" from Typescript to JS is something that mostly works, but still feels icky and sometimes breaks down. Setting up a great debug environment in Typescript/NodeJS codebase is still a pain, and mostly I don't even bother. I see that none of those are "killer" or seem very important, but it's enough just to try it for some small project in the future. And then, who knows? May be it'll just turn out to be better in general.
lmiller1990 6y ago
It has a super well vetted standard library written in TS. I think this is a pretty great feature.
TheRealPomax 6y ago
If that's the question you're pondering in order to decide whether or not to switch, you basically have no reason to switch yet. Stick with Node. However, if you've gotten more and more annoyed with Node's legacy method of requiring modules (because it predates modern modules) and legacy method of dealing with asynchronous code (because it predates promises and async/await), then you already know why Deno might -once it's matured a bit, because it's super early days still- be worth your time.
throwaway189262 6y ago
More hype. The lustrous sheen of Node is wearing thin after years of parading. On a technical level, they're trying to fix a bunch of mistakes made in Node. And build it on Rust which will hopefully mean less vulnerabilities. Kinda miffed they gave up on Typescript though
- afiori 6y ago
  > Kinda miffed they gave up on Typescript though What do you mean by this?
  - ballenf 6y ago
    Deno stripped types from internal code due some headaches and development issues it was causing: https://docs.google.com/document/d/1_WvwHl7BXUPmoiSeD8G83JmS8ypsTPqed4Btkqkn_-4 https://docs.google.com/document/d/1_WvwHl7BXUPmoiSeD8G83JmS... It will still support TS as a first-class language for users and projects.
MehdiHK 6y ago
A event loop that juggles between more than one thread, run async tasks in different v8 isolates.
deleted 6y ago
[deleted]

It's just so different, lots of people could claim different killer features. A strong contender for one section of the community might be the first class typescript support. Other people might like the way you can run so much from a single executable. Anyway, node is a pretty mature platform now, if it dies, it'll die like java-the-language is dying. Very very slowly, and with parts of its platform holding out much longer than other parts. Or alternatively it'll evolve and slowly adopt things from other ecosystems. I don't think we're at the stage where we can say that a bet on deno is definitely right, but it has a lot of interesting ideas and lots of people will be picking it up where they can. If you're interested in the difference between node and deno, check out the talk '10 things I regret about Node' https://www.youtube.com/watch?time_continue=1&v=M3BM9TB-8yA&feature=emb_logo https://www.youtube.com/watch?time_continue=1&v=M3BM9TB-8yA&...

silentprog 6y ago
Since when is java slowly dieing?
- andai 6y ago
  It's been 3 billion devices for twenty years :)
- snazz 6y ago
  Java mindshare has been dying for a long time. That said, it's still taught in schools and all sorts of companies still use it (including "cool" ones like Google and Apple).
  - The_Colonel 6y ago
    Java mindshare might be slowly shrinking but it is very, very far from dying.
    - rektide 6y ago
      I'd ask, what is sustaining java? Where are the replacement techies picking up the torch, where are youngsters seeing java? I have some answers. It's not a lost cause. Death is not likely, & I do appreciate a lot of java (cdi rocks, microprofile is doing great, performance is good, it has excellent big data tools & many serious pieces of infra are built with it). But how java can retain liveliness, over time, & how the experience & knowledge base continues, is a real challenge. Being on Android helps a lot but also it's a radically different immensely unlike the server side world, with its own elaborate platform specific architectures & libraries. There's not a lot of places java has a hold on UI/ux centered systems, outside Android, so it risks becoming too invisible.
      - pjmlp 6y ago
        When SAP rewrites their stack to something else other than Java, Amazon or Alibaba stop contributing to Java, then I start worrying. Microsoft decided that Java death is so imminent that they are now an OpenJDK contributor, collaborate with Red-Hat on VSCode Java support, have bought jClarity and Java has first class support on Azure.
        doteka 6y ago
        I guess a Roman, asked circa 300 AD how he feels about the decline of the empire, would have replied similarly. Java’s mindshare just isn’t where the exciting things in this field are happening. It’s more the domain of overengineered “big data” platforms and clunky enterprise software. Yes, SAP employs a ton of java developers I’m sure, but many devs would rather switch careers than work on anything resembling a crufty ERP. Thus, the ecosystem stagnates, due to the dead see effect - everyone who could push it forward into new areas has no interest being anywhere near it. And stagnation is a long, drawn out death all the same. It still has a ton of momentum, and millions of outsourcing devs who only know Java, so it will be with us for a while - but make no mistake, the decline started quite a while ago.
  - nzly 6y ago
    It is nothing about Java or even mindshare, it is all about money, shareholders, new companies, or even just have to reshape a wheel again. This type of subject is a pseudo-proposition. When many people are using Java, some guys need to create something new (may not really new) to gain the financial interest. Of course they have to pick up something bad about Java or whatever languages and then fill his new stuff in the marketplace, but actually nothing really new. C, C++, Java, Php, Ruby, Python and do on. When everyone is familiar with something or know something for long, the capital and money stop moving, which is bad for game players such as new companies in Silicon Valley and money makers from Wall Street.
  - spiritwander 6y ago
    java is not platform-dependent,it is a platform..
- kybernetikos 6y ago
  Well, part of my point is that it's very very slow, and because of that, there are all kinds of points I could pick for 'since when'. Maybe I'd pick when apple removed the default install from mac os, or maybe I'd pick when browsers made it impossible to run applets, or maybe I'd pick when the major java IDEs started pushing other languages like kotlin or xtend, or maybe I'd pick the oracle acquisition (never a good thing), or maybe I'd pick the release of go - a language squarely targetting pretty much the only niche that java has left (enterprise development of servers by mixed ability teams), maybe I'd pick the point when java development felt like it became more like configuring metadata for frameworks than actually coding, or maybe I'd pick when google started showing kotlin as the default language for developing on Android rather than Java. Here's google trends for java: https://trends.google.com/trends/explore?date=all&geo=US&q=java https://trends.google.com/trends/explore?date=all&geo=US&q=j... Java-the-language is not going away any time soon, but if you expect it to do anything except decline, I think the future will be disappointing.
  - pjmlp 6y ago
    Yep, so much decline with 80% of the mobile phones, even if it is based on Android Java, on top of which do you think all Android tools run on? Then do you think the likes of SAP, Adobe, Amazon, Azure, Ricoh, Gemalto, PTC, Azul,.... are going to port their golden eggs to Go now?
    - sinsterizme 6y ago
      This doesn’t refute his point, Java the language is separate from the JVM. And those big companies will follow the decreasing Java usage trend due to developer supply and demand. Anecdotally, it seems pretty obvious some of those companies are already doing this by writing new stuff in other, better languages when possible! To me that’s a good indicator a language is slowly dying, maybe you use a different definition.
      - andyroid 6y ago
        Pretty much any language running on the JVM will make it dead simple to import and use libraries written in Java - in fact one of the main reasons to choose the JVM is the huge amount of high quality libraries available. So while true that Java != JVM, it’s not as simple as that either.
- findjashua 6y ago
  JVM as a platform is doing just fine, but other JVM languages seem to be taking over Java’s territory: 1. Kotlin replaced Java for Android development 2. Scala has become the primary language for some of the major tools in the data stack - spark, kafka etc I’m sure there are other examples as well
  - pjmlp 6y ago
    Java is going away from JVM as much as UNIX is loosing C. 1. Politics due to how Google screwed Sun with Android Java 2. Scala is a tiny dot on JVM world and it remains to be seen how Scala 3.0 will be taken up, specially if Python like syntax is actually adopted
    - reader_mode 6y ago
      Well UNIX (or Linux more importantly) is "losing" C, C++ and more recently Rust are slowly displacing it. It's still probably going to be the ABI everything is based on but the language itself is not a first choice for many and that number is increasing over time. Is that what you were implying ? It doesn't sound like it from the rest of the comment because you seem to disagree that Java is losing mindshare on JVM.
      - pjmlp 6y ago
        First get a UNIX clone to take over the world written in something else other than C.
        bitwize 6y ago
        https://redox-os.org https://redox-os.org
        pjmlp 6y ago
        That is not an UNIX. Having some level of POSIX compliance doesn't turn an OS into UNIX, unless you mean Windows is a UNIX as well.
- pjmlp 6y ago
  It is a HN thing, on my circles the choice is only Java or .NET and it isn't going to change for years to come. Java is dying so fast than nowadays even Microsoft contributes to OpenJDK, having bought jClarity in the process.
  - nullsense 6y ago
    Where I am it's largely dominated by Java and .NET with bits of other languages here and there. I jumped ship to .NET after Oracle changed their licencing. I don't like them as a vendor and don't want to be tied to them. Java will still live to a pretty ripe old age but it does feel like it's a little over the hill nowadays.
    - pjmlp 6y ago
      As if Microsoft would be an angel vendor. .NET Core also doesn't run in all platforms where there is a Java implementation and not everyone is happy to rewrite their .NET Framework into Core, while Microsoft is in mix of leaving again stuff behind like the ongoing discussions about CoreRT, .NET Native, Project Reunion, MAUI vs Blazor vs WPF vs Forms show.
      - nullsense 6y ago
        Cool. I'm happy enough with it all, so that's me sorted.
    - lenkite 6y ago
      The problem with .NET is that Microsoft have a proven history of seeing the next shiny over the hill and dropping support for existing frameworks and libs while the "new and improved" framework is rolled out. See ! This way is better! Well, until the next better way comes up within a few years. I know of teams who have moved to Java simply to avoid the churn. Many folks prefer the boring but stable Java ecosystem.
- Shorn 6y ago
  You're on HN. If it's not growing explosively - it's dead. Do I really need a "/s" here?
  - alephu5 6y ago
    As well as this, I think it's also perceived to be a clunky old language. Our modern languages have much more ergonomic build systems, are much less verbose and have coding conventions tailored to modern tastes. This is important, so I predict that over the next few years, as the 20-30 year olds of today gain more senior positions, they're going to choose python, JavaScript, kotlin, golang or rust for new projects.
throwaway189262 6y ago
Java is still the best choice for many backend systems. C# and Go still don't have nearly the breadth of open source libraries available. And performance between the three is very similar, besides Java's new GC's are far better. For a majority of enterprise type integrations, which I would argue are the majority of software projects, Java and C# are still the only viable choices. And I don't see that changing any time soon. Go and JS haven't really touched that space despite widespread use for webapps. If you need a big enterprise MMORPG type system with tendrils reaching across the cosmos into your stagnant data ponds, creaky AS400, and React customer facing mirage, Java is the legendary weapon. It's your only choice, your destiny.
- ornornor 6y ago
  > React customer facing mirage Nice

benatkin 6y ago

It's better aligned with browser technology and with Rust. I think that in time it will run JavaScript apps that depend on browser APIs and/or Rust APIs better than Node. If it also leads to lots of people switching to Rust I don't think Deno's creators would have a problem with that.

nickcox 6y ago
> I think that in time it will run JavaScript apps that depend on browser APIs and/or Rust APIs better than Node Yes! For example, you get fetch out of the box.

ecmascript 6y ago

For me its: - Support for "browser" apis like fetch and ES modules. - Security - No NPM necessary, just import code like a browser would - No political agenda is being pushed, they simply focus on the tech The only thing I really miss from node is the cluster api.

iknowstuff 6y ago
What political agendas have you had a problem with in other projects?
- Ayesh 6y ago
  I suppose the elephant in the room is Ryan and npm inc.
- ecmascript 6y ago
  The node.js has a big blm banner for example and claims that white surpremacy and police brutality is global issues when it's really just very US-based. I just don't see how that has anything to do with javascript development.
  - true_religion 6y ago
    It takes different forms. In the US, the it was slavery, segregation and today police brutality and ideological oppression. Yet the US, isn't alone in this. It never has been. For example, although the famous poem Whiteman Burden was about the American-Phillipine war, it was written by a British poet based on his view of British Imperialism. That legacy of colonialism lives on today throughout everywhere in the English speaking world. As for the French, the less said about how they exploit the CFA zone countries, the better. The Russians? Currently the leaders of European racism. This isn't simply a topic isolated to a parochial country, far far away from the ideologically pure Old World. What occurs in the US was merely a Flashpoint.
    - ecmascript 6y ago

yulaow 6y ago

I am involved in a lot of nodejs communities here in EUW and no one is even talking about deno recently. In my twitter feed the only ones talking about it are those who are asking themselves why it was so over-hyped The adoption is basically nil.

mosselman 6y ago
What are you trying to say? You come over as being threatened by either Deno or parent comment or both. What are your thoughts on Deno then, besides that people around you are not talking about it?
- yulaow 6y ago
  I don't understand your questions nor your tone. [edit: see posts below, I understand now. Sorry I misread the parent post] I was just contesting the assertion of "switching in droves" by parent post. Find me a case of a nodejs community "switching in droves" to deno if you know some, or even a high impact project in nodejs currently switching to deno, if your intention is to assert that parent's assertion is correct. My thoughts are that atm there is no reason to switch your project(s) to it and that, for the features Deno offers right now, it was indeed severely overhyped
  - sturadnidge 6y ago
    The OP didn't assert anyone was switching in droves... they were asking what feature of deno would _cause_ that to happen.
    - yulaow 6y ago
      You are right, I misread. My bad on this one. Now I understand why the other user was curious about the way I answered.
- TheRealPomax 6y ago
  No they don't? They're pointing out that anecdotally, Deno seems to be a non-player right now. Which is pretty spot on: it's still very new, and hasn't found a critical application yet (e.g. would Node have taken off the way it did without Express? Probably not). So right now, it's an enthusiast's plaything, even if the architectural principles are much cleaner (wrt modern JS) than Node can ever become - without a rewrite so drastic it'll split the Node community like Perl 5/6 or Python 2/3, at least.

programmarchy 6y ago

Types and saner dependency management

rektide 6y ago

> What’s the killer feature that will lead to node developers switching over in droves? The killer feature is that it offers nothing new or distinguishing. It looks like other JS elsewhere. It offers WebSockets via the same sort of WebSocket support you'd have in the browser. You read files via the FileReader api you'd use in the browser. The killer feature is native developers who have an easy te embedding or writing add-ons for deno, not end of line developers. This killer feature / mass adoption mindset is such an ugly poison. The size of a community is far down the list of considerations, a proxy only for easy consumability & fitting within current pop-culture sensibilities myths & current styles. Think different. Look for what really may matter.

forty 6y ago

I have been running nodejs in production since 0.6 (2012) and I'm not emotionally involved with nodejs, being actually a scala person who happened to work on a nodejs project. I'm curious and interested by new things, so I looked at deno with interest. And honestly, for now, I don't see a single practical benefit that would make me switch over. I'm still happy that deno exists, experiment is good and if they ever find something that could make nodejs better, then it could be used to actually improve nodejs, which everyone will benefit from.

sktrdie 6y ago

Permissions for anything from local files access to network.

royletron 6y ago

It has string padding built in...

TheRealPomax 6y ago
So does Node? The joke stopped aging well after ECMAScript updated the spec for String with a padStart function, among many other improvements to the String type.
- royletron 6y ago
  party pooper.

rhacker 6y ago

You asked. Minimally: * module management that isn't in the code. * lock files that are not an afterthought. That all being said, even if it were true, I get the user experience of deno with ts-node, and the package.json and lock file support is free.

golergka 6y ago

For me, two small things that haven't yet been mentioned here. Dependency management that's much more friendlier to forks. Very often I want to patch something small in a public NPM library and point my company's private project to the fork that contains that patch, not having to wait for the maintainer to accept the PR. Publishing a separate private or public version of this is still a chore. Typescript support. The current "building" from Typescript to JS is something that mostly works, but still feels icky and sometimes breaks down. Setting up a great debug environment in Typescript/NodeJS codebase is still a pain, and mostly I don't even bother. I see that none of those are "killer" or seem very important, but it's enough just to try it for some small project in the future. And then, who knows? May be it'll just turn out to be better in general.

lmiller1990 6y ago

It has a super well vetted standard library written in TS. I think this is a pretty great feature.

TheRealPomax 6y ago

If that's the question you're pondering in order to decide whether or not to switch, you basically have no reason to switch yet. Stick with Node. However, if you've gotten more and more annoyed with Node's legacy method of requiring modules (because it predates modern modules) and legacy method of dealing with asynchronous code (because it predates promises and async/await), then you already know why Deno might -once it's matured a bit, because it's super early days still- be worth your time.

throwaway189262 6y ago

More hype. The lustrous sheen of Node is wearing thin after years of parading. On a technical level, they're trying to fix a bunch of mistakes made in Node. And build it on Rust which will hopefully mean less vulnerabilities. Kinda miffed they gave up on Typescript though

afiori 6y ago
> Kinda miffed they gave up on Typescript though What do you mean by this?
- ballenf 6y ago
  Deno stripped types from internal code due some headaches and development issues it was causing: https://docs.google.com/document/d/1_WvwHl7BXUPmoiSeD8G83JmS8ypsTPqed4Btkqkn_-4 https://docs.google.com/document/d/1_WvwHl7BXUPmoiSeD8G83JmS... It will still support TS as a first-class language for users and projects.

MehdiHK 6y ago

A event loop that juggles between more than one thread, run async tasks in different v8 isolates.

deleted 6y ago

[deleted]