Sometimes, but then I do some work in Java/.NET and part of me wishes I was using express/rails/django or something else lightweight. The grass is always greener
Ask HN: Is anyone else just tired of JavaScript?
31–40 of 47 posts
Re: Ask HN: Is anyone else just tired of JavaScript?
#32No
Re: Ask HN: Is anyone else just tired of JavaScript?
#33Tired of JavaScript? Not particularly. Tired of the #hype around JavaScript and more specifically the constant frameworks of the week? Absolutely. I don't think this is a problem unique to JavaScript, however. We see the same sort of thing around technologies. Right now it's ML and Blockchain, earlier it was Cloud and IOT. The industry in general appears to be mostly built on inventing problems that can be solved by…
And I am tired of the "tired of JavaScript hype and new frameworks every week" speech.
It has a huge community, of course there will be new things created every week.
But, if it as bad you will not even hear about it, if you hear it is probably good or better on some aspects compared to others, who doesn't want that? do everyone wanted to be stuck with MooTools or JQuery forever?
Re: Ask HN: Is anyone else just tired of JavaScript?
#34not tired about JS, but in some cases I don't like that we keep reinventing libraries (for whatever reason), instead of contributing to existing ones to make them better.
Re: Ask HN: Is anyone else just tired of JavaScript?
#35Tired of JavaScript? Not particularly. Tired of the #hype around JavaScript and more specifically the constant frameworks of the week? Absolutely. I don't think this is a problem unique to JavaScript, however. We see the same sort of thing around technologies. Right now it's ML and Blockchain, earlier it was Cloud and IOT. The industry in general appears to be mostly built on inventing problems that can be solved by…
And I am tired of the "tired of JavaScript hype and new frameworks every week" speech. It has a huge community, of course there will be new things created every week. But, if it as bad you will not even hear about it, if you hear it is probably good or better on some aspects compared to others, who doesn't want that? do everyone wanted to be stuck with MooTools or JQuery forever?
The major problem is that when you learn something in this current crazy JS/Front world, your knowledge is deprecated 6 months later.
I know a developer should always stay up to date with technology by constantly learning, but if I compare what I learned 5 years ago in Python, I would say 95% is still relevant today.
But if I look at the JS "state-of-the-art" stack today, compared to the 2 years old, it's completely different.
It's very frustrating to invest time and effort to learn something and then hear recruiters tell you things like: "Hmmm no one uses that anymore".
Re: Ask HN: Is anyone else just tired of JavaScript?
#36Earlier quoted context omitted.
Right now we can use any language which can be compiled to JavaScript. What will change? Wasm is not faster than JS.
For one thing, web assembly's architecture more closely matches the traditional backends that language designers are familiar with. Compiling to code to a byte code is a pretty much solved problem, and we have compilers that do this. Finally, while web assembly may not be faster than JS (although that really remains to be seen), it is faster to load.
AFAIK, today compilers are producing both asm.js code and Webasm binary. Webasm is for tomorrow, asm.js is for actual use, because it's backward compatible with any JS enabled browser.
Webasm is not so compatible. I tried to run random demo and got error message: CompileError: wasm validation error: at offset 8: binary version 0xd does not match expected version 0x1. WTF?
I tested https://webassembly.org/demo/Tanks/ demo, and on my system (Firefox, Fedora Linux 26), asm.js version is a bit faster to load than Webasm version. (Turn off support for Webasm in about:config to test). Asm.js: 1.57s to load from cache, Wasm: 1.82s to load from cache.
So what will happen when webasm finally more closely match traditional backends?
Re: Ask HN: Is anyone else just tired of JavaScript?
#37Tired of JavaScript? Not particularly. Tired of the #hype around JavaScript and more specifically the constant frameworks of the week? Absolutely. I don't think this is a problem unique to JavaScript, however. We see the same sort of thing around technologies. Right now it's ML and Blockchain, earlier it was Cloud and IOT. The industry in general appears to be mostly built on inventing problems that can be solved by…
And I am tired of the "tired of JavaScript hype and new frameworks every week" speech. It has a huge community, of course there will be new things created every week. But, if it as bad you will not even hear about it, if you hear it is probably good or better on some aspects compared to others, who doesn't want that? do everyone wanted to be stuck with MooTools or JQuery forever?
That's a totally reasonable sentiment and I can totally see how I didn't clearly articulate my feelings on the matter.
Of course we do want new tooling - ES6 and Angular in particular have worked well for me. Where I have some trouble is the tendency of some organizations to adopt these frameworks without considering whether the framework is actually solving a problem the have or expect to have in the near future. YAGNI is very tricky to get right.
Re: Ask HN: Is anyone else just tired of JavaScript?
#38Earlier quoted context omitted.
I mean... you could replace javascript with any other programming language and achieve the same thing. The choice of javascript as the language with which to access the standardized APIs is arbitrary. Browsers could have equivalently chosen any other sufficiently similar language, like Lua or Python.
If it wasn't because of Java the browsers language would be Scheme
> the browsers language would be Scheme
And the world would be 10000 times better off for it.
Re: Ask HN: Is anyone else just tired of JavaScript?
#39Re: Ask HN: Is anyone else just tired of JavaScript?
#40Earlier quoted context omitted.
And I am tired of the "tired of JavaScript hype and new frameworks every week" speech. It has a huge community, of course there will be new things created every week. But, if it as bad you will not even hear about it, if you hear it is probably good or better on some aspects compared to others, who doesn't want that? do everyone wanted to be stuck with MooTools or JQuery forever?
The major problem is that when you learn something in this current crazy JS/Front world, your knowledge is deprecated 6 months later. I know a developer should always stay up to date with technology by constantly learning, but if I compare what I learned 5 years ago in Python, I would say 95% is still relevant today. But if I look at the JS "state-of-the-art" stack today, compared to the 2 years old, it's completely…
Maybe because there is no need to evolve there?
I mean, you can see clearly why we came from jQuery, to AngularJs, then Angular/React/Vue, there was a need.