3 ms·
I don't conflate those things at all. I think it is a good language under the hood, and it remains in browsers because it is popular. Browsers got rid of VBScri
by WorldMaker 7y ago
I don't conflate those things at all. I think it is a good language under the hood, and it remains in browsers because it is popular. Browsers got rid of VBScript for several reasons, and they'd ditch Javascript if there was a populist uprising. (That seems unlikely and Google's efforts with Dart seem pretty clear that there is little interest in a second language in the browser, though we can argue that Google might not be capable of making a better language than Javascript.)
Javascript is an interesting language on the evolutionary chart with genes from Scheme and from Self. While those genetic traits are sometimes obscured by the last minute bolting of an ALGOL-like syntax on top (by way of Java, and thus the odd name), they are still fundamentally there. There are some really smart (albeit quick) decisions underpinning the language that have helped it to survive multiple decades of (ab)use on the web and elsewhere. It has had its flaws, its evolutionary dead ends, its quirks, but show me any language without those (and I'll sell you a bridge).
If there is a risk of a conflation problem here, I'd suggest it has more to do with people conflating "easy/accessible" and/or "populist" with weak or bad. BASIC is "bad" because it was made to be easy and welcoming to beginners. (But it still got a lot of serious work done in almost every field, by just as many [domain] experts as language beginners.) JS is "weak" because it was made for being embedded in browsers. (But the web browser became one of the most important forces on the internet for better and worse, and most of its weaknesses have been scrupulously filed off in daily usage and security audits and the pendulum swings between market competition and monopoly.)
- pdimitar 7y ago> If there is a risk of a conflation problem here, I'd suggest it has more to do with people conflating "easy/accessible" and/or "populist" with weak or bad. I never said that and never will because it would be quite naive. Let's not resort to strawman. I don't mind languages being "easy/accessible" -- if I did I wouldn't make Elixir my main language. There are many, valid, well-documented, warts of JS, so much so that an actual book called "Javascript: The Good Parts" had to be written. (I find that quite amusing.) > I think it is a good language under the hood, and it remains in browsers because it is popular. You might be mistaking what you said with "we literally had no choice for 20 years except use JS on the browser" (VB, ActiveX, Java Applets et. al. had game-breaking problems, cross-OS compatibility included, so they fell to the sides). "Popular" is the consequence of having no choice for a long time, not a function of any perceived high quality of JS. Google's efforts with Dart failed simply because Google has a short attention span and their numerous cancelled products can attest to that much better than any argument I could make. There's absolutely nothing preventing any corporation adopting any language and slapping a small DOM access library on top of it. This is not being done for HR reasons: the companies want to choose from a singular pool of devs so its operations are easier and quicker. A valid business decision which has zero correlation to JS being good. JS survived because it was "the least bad" at the time when everyone needed a browser language. Everyone is too busy making a living so we just rolled with whatever the browser vendors and corporations half-begrudgingly (and rather urgently) settled at. Assuming you hated JS, can you tell me with a straight face that you'll sacrifice all your free evenings and weekends to produce another browser language? For like 2 years? > It has had its flaws, its evolutionary dead ends, its quirks, but show me any language without those (and I'll sell you a bridge). It will have them for a looooong time still though. Even if many will stop supporting IE11 soon-ish, there's still a ton of baggage left that will never get fixed. The much more likely scenario is people will just start compiling language X to WASM and will go with that when hiring frontenders. And we will see the return of the full-stack role when you actually can work on the entire stack only with Rust, D, Nim, C++, or your language of choice. It is very probable we'll again start seeing web shops proudly touting themselves as "we only do C++ (or PHP, or Pascal) here".
- deleted 7y ago[deleted]