I think within a few years WASM will finally be in a place where it becomes usable without relying on JavaScript for interfacing with the web browser and people will be able to develop high-performance, isomorphic web applications in other programming languages. This will definitely start to eat into it as it makes gains elsewhere. As such, I don't really see JavaScript reaching the level of dominance implied in this…
> it becomes usable [...] for interfacing with the web browser As soon as you add DOM integration... all the things people hate about JS in terms of architecture and compromises will show up in WASM.
What if JavaScript wins?
31–40 of 88 posts
Re: What if JavaScript wins?
#32Earlier quoted context omitted.
"In the future programmers won't be replaced by robots, they will be replaced by import statements." I disagree. How is this different from someone 20 years ago saying programmers will be replaced by jar files.
Yeah, the reality is some of us got replaced by Adobe and Salesforce.
Re: What if JavaScript wins?
#33Earlier quoted context omitted.
You literally restrict yourself to one of the worst languages ever designed. What could be solved with elegance and without demoralizing your staff in 5 minutes in some other language, in JavaScript it might require "sailing to Africa and back" to achieve the same (though I must say it has improved a bit recently from the insanity it used to be). On paper it might look good to you, but the reality is very different a…
What's an example of a "sailing to Africa and back" problem in JavaScript?
Re: What if JavaScript wins?
#34For me, as a founder of a young startup, the overarching benefit of being proficient in modern JS and sorrounding tooling is that I can use the same language for my whole stack(servers, web, Android, iOS), and spend more time thinking about the product and business. In the possible future where the company grows enough where it needs a distributed server software, the only part of the product that'd be changing would…
You literally restrict yourself to one of the worst languages ever designed. What could be solved with elegance and without demoralizing your staff in 5 minutes in some other language, in JavaScript it might require "sailing to Africa and back" to achieve the same (though I must say it has improved a bit recently from the insanity it used to be). On paper it might look good to you, but the reality is very different a…
2. What sort of scalability issues related to Node.js are you talking about? Isn't node.js (thanks to V8, and async IO) much more performance friendly than other scripting langs?
3. Regarding web-stack changing quickly, this hasn't effected me on server side yet. It has effected me on the mobile apps and web app side of things where I am using react 15.x, but it'll make sense to tackle that after raising meeting the next few business milestones.
Re: What if JavaScript wins?
#35Re: What if JavaScript wins?
#36I used to hate JS because the language is objectively badly designed, but then I realized that the merits of the language provide a glimpse of the future of programming. Most programming problems people have are highly generic, often looking to implement something completely off the shelf as far as problems go. Wheels can only be reinvented so many times in so many ways. To me the JS ecosystem offers a level of high…
Re: What if JavaScript wins?
#37https://www.destroyallsoftware.com/talks/the-birth-and-death... was supposed to be satire... but "asm everything" might actually kind of happen.
Re: What if JavaScript wins?
#38To put things in perspective, every decade there is an uber popular so called simple but highly inadequate non-type checked language that is taking over the world of novice developers. It's a social phenomenon. Started with Basic, JavaScript is the latest incarnation. By the same token, there is also one overcomplicated yet unavoidable professional language. In that sense, Scala these days has a proud lineage of C++…
Re: What if JavaScript wins?
#39For me, as a founder of a young startup, the overarching benefit of being proficient in modern JS and sorrounding tooling is that I can use the same language for my whole stack(servers, web, Android, iOS), and spend more time thinking about the product and business. In the possible future where the company grows enough where it needs a distributed server software, the only part of the product that'd be changing would…
100%. In addition, I know I can hire tons of mid-level people with JS skills and they'll be effective quickly. As much as I'd love to throw a bunch of Haskell into the codebase, the vast majority of engineers will take a while to be productive in it.
Re: What if JavaScript wins?
#40Earlier quoted context omitted.
> highly generic, often looking to implement something completely off the shelf as far as problems go. There is serious work being undergone in automating this using advanced ML. In 5-10 years most of these problems will be LEGO-ized and humans won't be needed on that level. So your generic JavaScript developer used to glue these pieces will be gone.
That’s been 5-10 years out since the 50’s, right?