Slashdot Mirror
'State of JavaScript 2018' Survey Announced (stateofjs.com)
"The JavaScript world could use a bit of classification," reads this year's announcement at StateofJS.com:
In 2017 this survey helped us do just that, by collecting data from over 20,000 developers to identify current and upcoming trends. This year, we're asking for your help once more to find out which libraries developers want to learn next, which have the best satisfaction ratings, and much more.
The survey launched in 2016 "mostly to scratch my own itch," its founder explained in a Medium essay. "I wanted to know what libraries were worth learning, and which ones were on the way out." Last year's survey discovered that React was the dominant framework, though the second most-popular framework was "none," with 9,493 JavaScript developers saying they didn't use one. Vue had increased in popularity while Angular lost steam, and developers collectively rating their overall happiness with front-end tools at 3.8 (on a scale up to five).
And more than 28% of the survey's respondent's said they'd used TypeScript, Microsoft's typed superset of JavaScript, and that they'd use it again.
The survey launched in 2016 "mostly to scratch my own itch," its founder explained in a Medium essay. "I wanted to know what libraries were worth learning, and which ones were on the way out." Last year's survey discovered that React was the dominant framework, though the second most-popular framework was "none," with 9,493 JavaScript developers saying they didn't use one. Vue had increased in popularity while Angular lost steam, and developers collectively rating their overall happiness with front-end tools at 3.8 (on a scale up to five).
And more than 28% of the survey's respondent's said they'd used TypeScript, Microsoft's typed superset of JavaScript, and that they'd use it again.
It still sucks.
Result: Brainfuck can still produce more useful code than javascript "web apps" and don't need a 500mb browser to run it.
- 80% are ads, web trackers and other malware
- 10% are useless eye candy that waste time and CPU
- 5% are misguided attempts to turn web browsers into terminals and bypassing HTML as much as possible, that usually result in unusable interfaces that don't behave properly and waste CPU
- 5% are actually useful on the pages they're used on
Javascript isn't the problem, it's the developers who foist it on us because they're incompetent, greedy or nefarious. Still, I can't count the number of hours I waste every week trying to find out in Noscript or uBlock the minimal number of scripts I have to allow to access a web page. Fuck Javascript.
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
It’s easily summed up in two words:
Shit sux.
Actually Javascript is the problrm. It’s got most of the worst traits of C’s implictness (you did want that string converted to a bool right?) while none of the positives.
No string should ever be converted into a bool or an int or a float. Who comes up with this shit? Shitty shitty shit shit
Sure, pretend the name of the logic language is the problem and not the advertisers.
because we all know everyone would mutate into completely different people if we called it .net or c# right?
Do people need to wipe your bum and help you eat? you sound like a retard
I have known some Javascript ever since it was invented and spent decades avoiding it as much as possible. I can't remember who it was but they wrote that "Javascript is the most feared language" in computer science.
Now that I am doing client-side web apps it is unavoidable. Except, of course, for Microsoft wonderful effort into Typescript. It takes away none of Javascript's "strengths" (such as they are) but it makes it possible to get serious assistance from your IDE. You end up not as constrained as Java but you feel less like you are tossed into a chaotic lake of famished crocodiles, horny hippos and drunk rednecks in speedboats firing guns everywhere.
Thanks to Typescript I don't feel like I am writing Javascript any more than I feel like I am writing in assembly language when I code in C. Only an occasional trip to w3schools or stackoverflow is all that is needed to cover the quirky things I didn't know.
That said, I always wonder why anyone can be in doubt about why Javascript is so ascendant. There can be no reason other than it had access to the pervasive API of the browser environment. In other words the DOM and the browser-provided objects. That, and the fact that the build environment and the runtime environment were one and the same, helping countless legions of amateurs to get "into" web programming.
With all its flaws Javascript fell into a mucky pond and evolved into an ecosystem were a lot of people could make a living from using it. That's what made it successful. It has little or nothing to do with the merits (or demerits) of the language itself.
Imagine if Google had created node.js first, and all browsers were using some other language like Python. Nobody but a quirky minority would pay any attention to Javascript whatever. Now pretty much all of us have to pay attention.
The name is meaningless. The language itself is shit on a stick.
http://vanilla-js.com/
Look at the speed comparisons. And the other big bonus is not having to download multiple hundred kilobytes (if not megabytes) of framework code.
#DeleteFacebook
the language doesn't even matter, nor does the name.
Jesus are you just as stupid as the parent poster? Like do you all drink fucking gallons of lead paint each day?
It wouldn't matter what language you put it in, advertisers will be advertisers
Looks like we got a Trump voter in our midsts.
"I love the poorly uneducated."
But Microsoft's attempt to embrace, extend and extinguish makes me want to defend it. Just not enough to do so.
Tcl was once a rival to JavaScript. There was a plugin for Netscape when it was at peak fame and JavaScript was still relatively unknown that allowed you to run client-side Tcl scripts in web pages. It would have been a lot better, in some respects, but Tcl isn't a terribly stable language and the plugin got no traction.
Still, you'd have far better code today.
JavaScript does serve some purpose, although HTML5 now includes tags for some of the functions.
Part of why it did succeed was that it Just Worked(tm), unlike applets.
If early applets had been secure, as fast as JavaScript and able to push HTML to the browser page, this conversation would not be happening. Sun screwed up badly with applets. Too much bad press and too many performance issues.
JavaScript isn't that much better. It's still slow and it's still dogged by security problems. But they're at an acceptable level for many. It's tolerable defective.
Still, there's nothing out there that can compete. Since the Tcl attempt, I've seen no serious effort to embed other scripting languages in browsers. You'd need Mozilla, Google and Safari to agree on one to get any traction now and they don't agree on the time of day.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
You forgot cryptomining and Spectre/Meltdown.
In C, there's a basis. It's near machine level and machines don't see data types. Types in C are a sugar to make life easier.
JavaScript is not machine level. It has no excuse. Same goes for Python.
Once you go past the very low level, you should have strongly typed languages because type means something then. It's a real thing that's independent of the machine.
It would be interesting to see an Adascript or an Eiffelscript.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
Wake me up when we can stop doing dumb hacks like this to detect what version of the language the browser has implemented. I guess providing a const window.JSVER took too much effort.
"use strict"; is a necessary kludge. Is there a way to turn it OFF after being turned on???
When are Int64 and UInt64 going to be standardized and supported?
When is BigInt going to be standardized?
Can we deprecate that shitty double equals comparison and keep triple comparison?
9999999999999999 === 10000000000000000
true
*facepalm*
I think you mean "strictly," not "strongly." // JavaScript // not strict // strong // C // strict // not strong
let foo = 'bar';
typeof(foo) === 'string';
int blah = 5;
void *glarb = blah;
Aside from that, you're still wrong. :-) Languages are for people to understand and write, not computers. People can (and do) write more lines of code with JS and Python nowadays than in C even though fewer lines of code are necessary than the equivalent C. They're getting more done. Harkening back to "good old days" that never existed doesn't help anyone, nor prove you're a better coder.
And I'm old enough to remember people who were still skeptical of C because assembly didn't hide anything from you. Feel free to find your way clear of my grass frontage.
- I don't need to go outside, my CRT tan'll do me just fine.
BigInt: Arbitrary precision integers in JavaScript
https://github.com/tc39/proposal-bigint BigInt64Array,BigUint64Array
Arbitrary precision is inefficient beyond belief for the vast majority of cases where integers are appropriate.
When all you have is a hammer, every problem starts to look like a thumb.
Ok, I'm oh approaching 50, and no, strongly typed is the correct term.
And, no, if programs were written for people, we'd be using 4th and 5th generation languages, not 3rd, and the most popular 3rd gen would be D, not Java.
Harkening back... so you're saying there was an Eiffelscript? Because I sure as hell have never said anything nice about the old days.
There's only one thing that proves one coder better than another -- the ability to learn something new. For every other metric you can think of, there'll be just as many contexts that expect an opposite result and far far more that don't care at all. Learning is the one universal trait.
I'm not "better" (or worse) because of what I know, that's luck of the draw and nothing to do with me. If I'm better, it's because I don't restrict myself to someone else's wisdom.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
I don't care about the latest fashion trends. Javascript isn't able to meet basic requirements that have been standards for decades.
And the vast majority of people don't need numbers larger than 2^53. Don't get me wrong, I'm looking forward to using BigInt, but mostly for conversions to/from 64bit numbers. In actual usage, I rarely find 2^53 to be constraining.
I take that back; bitwise operations being limited to 32bits is a legitimate pain. Yet another reason I'm looking forward to working with BigInt.
- I don't need to go outside, my CRT tan'll do me just fine.