... And what new things changed it the most?
For further actions, you may consider blocking this person and/or reporting abuse
... And what new things changed it the most?
For further actions, you may consider blocking this person and/or reporting abuse
Latest comments (38)
Nice video that show the JavaScript development progress:
The Story of Next.js
It definitely could be that way still but the critical thing promises added over callbacks was an immediate return (of a promise), where as callbacks didn't immediately return.
This lent itself more to a chainable
.thenstyle that could be structured into a relatively flat format. async/await just took that one step further by enforcing the linear progression. Interestingly, I see people awaiting every possible async call now even when it's not necessary.I no interest in furthering this narrow discussion on node for the server when a large proportion of my node apps are tools, good day.
You can say whatevery you want, but I don't think you're right. Of course you don't need to agree with me. You have your own option I have mine.
Also I think that you don't understand the purpose of this post and my comment. This is my personal milestones in JavaScript development. You can't say that I'm wrong if I write my own experience with JavaScript development. Your experience may be different why don't you write your own milestones instead of jumping on me.
Also I've written:
It was first framework that added reactive way of writing SPA with double data binding, with declarative way of writing components.
Not sure how math being slower relates to complexity but okay nobody claims that node is the fastest, it's not supposed to be fast is not the only metric I suppose.
The question Ben asked was what has changed and JavaScript moving to the backend was absolutely one of them.
I can see you have some issue with JavaScript people getting involved in a really complected world of backend and screwing it all up which is really short sighted, you can know a lot of typed languages and still write JavaScript
That is completely fictional, your tech stack matters to it's particular application, high per for high perf requirements.
Choosing a language for light speed when your making a to-do list is not a good idea contrary what some might tell you.
Being able to maintain a stack is, look at dev.to it's ruby, is ruby known to be fast? No, is it beloved, I hear it is
Yes but you write your code in ASP, you can write application and don't touch JS at all. The same Google GWT and R Shiny are not JavaScript. We talk about Pure JavaScript, not some Hybrid. ASP.Net is C# framework not JavaScript framework.
Check Wikipedia there is only one mention of JavaScript in this article. I think that you're confusing web app development with JavaScript development.
ASP.Net is not JavaScript if you're not aware. There was also GWT but we don't talk about other langauges.
Evidence to support these claims?
Lots!
I'll leave it to others to expand on the details. But believe me, it's lots! ;-)
A couple of decades here.
My hopes for the future
One of the best overviews I've seen here :)