Become a fan of Slashdot on Facebook

 


Forgot your password?
Close
typodupeerror
×
Oracle

Should JavaScript Be Renamed? (kieranpotts.com) 170

Posted by EditorDavid from the if-Perl-6-can-become-Raku dept.
Software engineer Kieran Potts asks: does JavaScript need to be renamed? There's no doubt there are problems with JavaScript's branding...

- Correctly, "JavaScript" refers to a subset of ECMAScript specified by Mozilla, but the word is used interchangeably to refer to multiple different ECMAScript supersets, depending on context.

- JavaScript is a trademark of Oracle Corporation, which doesn't fit comfortably with the language's position as a central component of the web platform, which is meant to be built entirely from open technologies and standards.

- There isn't even an official logo for JavaScript, let alone a cute mascot like Go's gopher or PHP's elephant.

- And famously, JavaScript is unrelated to Java. This has confused the hell out of non-technical managers and recruiters for decades.
The article also suggests "a standard convention" to identify the runtime's host system (for example, "WebJS" or "ServerJS").

But in response to the question of rebranding JavaScript, "the most common, knee jerk reaction was a quick guffaw and an exclaimed 'no!'" notes tech columnist Mike Melanson, "while others offered that the simple contraction to JS would suffice."
This discussion has been archived. No new comments can be posted.

Should JavaScript Be Renamed? More

Should JavaScript Be Renamed?

Comments Filter:

  • Yes (Score:5, Funny)

    by theshowmecanuck ( 703852 ) on Sunday October 27, 2019 @02:51AM (#59351672) Journal
    And it should be called "Only use this shitty language for web pages and nothing else, hear that you fucking node twats?" Or something like that.

    • Re: (Score:2)

      by Z00L00K ( 682162 )

      Not even there it's really a good language.

      Please let it die.

      • Look, I know JavaScript has lots of issues (wow, do I know from years of working with JavaScript and TypeScript). I've been programming about forty years (since a teenager learning 6502 Assembly on a KIM-1), and in general I'd prefer to use a language and environment more like Smalltalk or Clojure or Racket. Ideally, browsers would have supported a Smalltalk-like VM (webassembly-ish) from the start. But JavaScript, given its Scheme roots, especially now with ES6 and ES7 advances including async/await, can b

    • PHP, VB, C++ (sorry, I do think that), etc are also strong contenders.

      JS's implicit casts are insane, yep. But languages with implicit casts are generally insane. There is no sane way to do it.
      Its OO system is merely misunderstood, and a bit cumbersome in its implementation, but not bad. Just different from class-based systems. (Which, IMHO, are a bad concept that I consider constraining and harmful.)
      The rest comes from it being the language for every newbie and hack out there. Which is not the language's f

      • while others offered that the simple contraction to JS would suffice

        As the book says: You don't know JS [github.com]

      • JS is insane in every possible way. It has two null values. It has three different definitions of a "property". It has at least three kinds of values (objects, primitives and natives). You say that its OO system isn't bad: which one are you talking about in particular, because it has three of them and all of them are awful? Shall we talk about how new Boolean(false) evaluates to true? Php and C++ may suck as well, but putting them on the same level as javascript isn't intellectually honest.

        • JS is insane in every possible way. It has two null values. It has three different definitions of a "property". It has at least three kinds of values (objects, primitives and natives).

          Sure, but that's minimalist compared to PHP or Python or any of the other dreck that passes for computer languages these days.

          • I don't know, I mean... PHP has an unsurprising if ugly object model; perhaps it has two now.

            Javascript originally had objects that could inherit the properties of another hidden object, which was associated with the receiving object by a property of this latter object that you couldn't set yourself, but it would be set for you by the language runtime if you created the receiving object by calling the "new" operator against a function, which itself is an object, and in that case a property with a well-kno

    • Bikeshedding.

      • Re: (Score:2)

        by gweihir ( 88907 )

        Indeed. Although it seems many people do not know that idea these days. Which is really part of the problem.

        • The other side of that coin is people using bikeshed issues to force their way into management of a project. They demand something unrelated, like a name change, get a bunch of people fired up to support them, and then act like they're a core contributor to a project, entitled to force their way down everyone's throat begore they move on to a new project.

          These people have earned nothing. No right whatsoever to demand change. You want to change the name, fork it and write some code. Bam, name's changed. But

    • Shouldn't even use it for that - AFAIK people who use javascript for web front ends only use it for some really basic operations (like string concat). The real use is DOM manipulation, which could be donw in any language as its down to the (standard) API the browser provides.

      So how about it Mozilla, scrap JS for a web language that is small and has only those things you need to mess with the DOM. Make it a standard, wait for browsers to roll it out, then we can scrap JS and all its myriad of "interesting fe

    • I nominate:

      JavaSchit -- for how crappy its design is.

      But what can you expect that it was designed and implemented in 10 days.

  • No need. It will die soon. (Score:5, Insightful)

    by BAReFO0t ( 6240524 ) on Sunday October 27, 2019 @03:04AM (#59351688)

    As soon as WebAssembly gets proper browser API support, as was planned, everyone can use any language they want. And then, almost certainly, everyone who has to pick (like a newbie) will pick something better.

    The only reason that thst isn't the case yet, is because they chose to implement the minimum viable subset first, and that means you have to use JS to interface between the browser and wasm.

    - - - -

    I certainly won't use "HTML5" at all anymore. I will have a basic canvas page, and just compile my proper applications to wasm as a, how I call it, legacy target.
    Until browsers just become such generic virtual machines (which they mostly already are), that "HTML5" will be just one (shitty) of many platforms.

    For actual documents, I will keep using some better format, like TeX, PS/PDF, etc.

    • The oh-so talented web development community continues to pretend that big bad WebAssembly isn't going to nuke JavaScript from orbit in the very near future.

      And even the ones who see the writing on the wall for the rapidly approaching doom of JavaScript think that there will be high paying Cobol type jobs supporting legacy systems for the next decade or two.

      Once WebAssembly has minimum viable access to the DOM in the major browsers for real world sites, JavaScript usage numbers are going to look like WeWork

      • Just like JavaScript, WebAssembly will be blocked in the browser because, like JavaScript, it is an ill-conceived hunk of crap.

        • Re: (Score:2)

          by gweihir ( 88907 )

          And how did you arrive at that insight? "Fills the same role, must be the same thing"? Or was some actual thinking involved?

        • It evolved out from a few different projects with completely different approaches that went on their own for years of evolution of their own. It is not ill-conceived. Maybe a few things are not perfect but nothing ever is... which is why we have versioning.

          What is ill-conceived is adding DOM access to WebAssembly just for some slight speed bumps. The wise move will be to make WebAssembly a generic safe VM with the most minimal API possible which then requires a bridge to connect it to any environment it

      • There will be JavaScript jobs, probably not high paying like COBOL, but they will be there.

        We're better poised now than ever before to rapidly transition from the /user/ point of view -- browsers auto update, and very few use systems that won't support new technologies as they appear, it's not like the bad old days of having to worry about supporting older versions of IE, Netscape, whatever... ...but from the developer side of things there are trillions of lines of JavaScript out there happily doing what ne

    • Re: (Score:2)

      by gweihir ( 88907 )

      That is pretty much what I expect will happen. The freedom to use good tools will finally be reestablished. And you can finally do things like, say, Python with C modules for performance again. Completely agree on the document formats.

      • ...you can finally do things like, say, Python with C modules for performance again.

        I can't wait for you to start creating web pages. I'll have lots more free time while they download.

    • Javascript is just fine... (Score:4, Interesting)

      by bussdriver ( 620565 ) on Sunday October 27, 2019 @08:59AM (#59352314)

      1) scripting languages as classically defined have blurred the lines as compiled languages act more like scripting languages and we use compiling tools for scripting languages. Anything you compile should not be called scripting even if the end product is a script... hell, Java goes to bytecode which is interpreted (usually compiled... but then our scripting languages dynamically compile now too!) So I'd define it as something the developer does NOT need to compile.

      2) Quick (development,) dirty automation and coupling of abstracted components. That is what their purpose has been and same for javascript. Improper demands upon have them evolving in the wrong direction. Javascript's still a good language, but like C++ it gives you too many ways to hang yourself up... that is, the blame is largely yours (and ECMA for giving you extra rope and others for giving you a jungle gym to navigate. Most complaints can be levied against C++ too.)

      3) Tie things together with duct tape. One of the big time consuming problems of software engineering is the high level work of manipulating components that were not designed to cleanly work together. So we have tons of high level errors coupling things that were decoupled and insane amounts of refactoring to fit squares into round holes. Scripting allows easier ways to duct tape parts together without all the extra labor. The evolution of scripting should be to aid in the testing, experimenting and coupling of complex opaque components to AVOID refactoring (except in scripting because it's more flexible to refactor... and most often, profiling points out what needs porting to a compiled language.)

      4) ABUSE ONLINE: any programming ability will be exploited by marketing bastards to just beyond the limit of our tolerance. Web Assembly is next.

      5) WEB ASSEMBLY SHOULD NOT GET API SUPPORT. Did we learn nothing from Java Applets? Sure it'll be better... until it's not. Coupling the browser API with WebAssembly components with scripting makes it a much harder attack surface - and it uses scripting for it's intended purpose: coupling things together. The evolution should be in the direction of making this easy so there is almost no work to port code and compile it to webassembly. Most that labor should be JS bridging on the outside.

    • Re: (Score:2)

      by reanjr ( 588767 )

      Bwahahahahahahahahahahhhahahaha!!!

      You crazy...

  • If Microsoft, Google and Facebook did it together it could happen.

    My vote is DomScript.

  • Sure (Score:5, Insightful)

    by 93 Escort Wagon ( 326346 ) on Sunday October 27, 2019 @03:28AM (#59351714)

    Let’s change the name after it’s been known as “JavaScript” for the past 25 years. I can’t think of any problems with that.

    • Re:Sure (Score:4, Insightful)

      by AmiMoJo ( 196126 ) on Sunday October 27, 2019 @03:40AM (#59351730) Homepage Journal

      Javascript suits the language perfectly: thought up over a weekend with no real planning or consideration, became a de-facto standard and is almost entirely unsuitable for the tasks required of it.

      • Re:Sure (Score:4, Insightful)

        by gweihir ( 88907 ) on Sunday October 27, 2019 @07:19AM (#59352030)

        Indeed. It was something they wanted in before the impending release, so something was slapped together in a few days. And it was never really fixed.

  • The language for 3rd rate devs and over promoted graphic designers and typesetters everywhere.

    No serious dev chooses to program in this dogs dinner of a language, its mainly ones who arn't good enough to develop in or even understand C/C++, Java, C#, Python, Scala or 101 other properly designed languages.

    • I used it to help build a system that processes over 1 billion transactions per year at less than 0.005$ per transaction.

    • Which of those can do client side DOM manipulation to enable users to get things done faster, without adding unnecessary server side processing?

      No, WASM doesn't count because it's an unreadable BLOB.

      Anyone doing web stuff is going to have to learn some JavaShit, and changing the name after 25 years just invalidates all the search results or adds more substitution cruft to any decent search engine. Just no.

      • Re: (Score:2)

        by jythie ( 914043 )
        I don't know, invalidating search results might have some utility. One of the more frustrating parts of trying to look up help on something that is both old and keeps changing is having to check the dates on various answers to see if it still applies or not.

    • If that is your opinion, you have no clue about the topic.
      Why would a programmer that needs to know more than you in his environment be third rated?
      Are you fourth rated?

  • Do not to spoil the fun (Score:5, Funny)

    by mridoni ( 228377 ) on Sunday October 27, 2019 @03:44AM (#59351738)

    We could name it "Perl 6"

  • Something catchy and apt (Score:5, Funny)

    by DrXym ( 126579 ) on Sunday October 27, 2019 @04:01AM (#59351762)
    GarbageGlue has a ring to it.

  • logo (Score:2)

    by ebcdic ( 39948 )
    "There isn't even an official logo for JavaScript, let alone a cute mascot like Go's gopher or PHP's elephant" - good.

    • Is PHP really an elephant? That's hilarious and appropriate.

      I dunno, I've had a copy of The Rhino Book since 1996, but I do suspect most "professional" JavaScript programmers were born after that so maybe they are unaware. This logo complaint didn't need to happen.

      As far as the name, the industry tried for ECMAScript more than a decade ago. If it didn't work then, and this entire premise is a waste of energy until Oracle starts suing people. Which they rarely hesitate to do, but apparently haven't yet

      • Re: (Score:2)

        by laird ( 2705 )

        Well, the only real argument for using JavaScript is that it runs in all browsers, and no other language does. WebAssembly some day will probably replace it, and allow for pretty much any language to run safely in browsers, but until then, JavaScript is the only option.

        Sure, I am a bit sad that the browser scripting language was switched from the original scheme (lisp) to Java-ish syntax, but it's too late to fight that battle.

    • I suggest they adopt the logo of a Cane Toad. It seems to fit.

      Type system: "They’re well known for humping dead animals, even trying for hours to hump a female that has been run over by a car, but they don’t limit themselves to just dead frogs, they’ll even hump dead salamanders, snakes, lizards, mice, anything."

  • Truth in Naming (Score:4, Funny)

    by Retired ICS ( 6159680 ) on Sunday October 27, 2019 @04:07AM (#59351774)

    If there were Truth in Naming we would call it BlockMePlease

  • What's wrong with ECMAscript? (Score:5, Interesting)

    by blindseer ( 891256 ) <blindseer@noSPAm.earthlink.net> on Sunday October 27, 2019 @04:41AM (#59351828)

    I see the answer in the question.

    - Correctly, "JavaScript" refers to a subset of ECMAScript specified by Mozilla, but the word is used interchangeably to refer to multiple different ECMAScript supersets, depending on context.

    In the article it points out that the different subsets and/or implementations of ECMAScript were given trademarked names like JScript, TypeScript, and ActionScript. Seems to me that the problem is that people use the word "JavaScript" when they mean "ECMAScript", much like people use the brand name "Kleenex" when referring to any single use facial tissue. The answer to this question then is to use the right word for the context. If you mean to refer to the specific subset or implementation of ECMAScript then use the name given to that, be it JavaScript, JScript, ActionScript, or whatever. If you mean ECMAScript then use the word ECMAScript.

    JavaScript doesn't need a new name because JavaScript is a trademarked name for a subset of ECMAScript. Seems to me the question that is really being asked is if ECMAScript needs a new name. Which leads me to ask, what's wrong with ECMAScript? I guess it's because it doesn't quite roll off the tongue.

    I took a look at the Wikipedia page on ECMAScript and I see that they already have a proposed name for the next version, ES.Next.
    https://en.wikipedia.org/wiki/... [wikipedia.org]

    ES.Next isn't too bad. Maybe "NextScript", but that might run into some confusion. Maybe get rid of the period in the name and call it "ESNext".

    Perhaps before we can provide an answer the question needs to be clarified. What problem is trying to be solved exactly?

    • Or, since itâ(TM)s a subset of EcmaScript, why not just call it ESLite or PoopScript?

      Call me old fashioned, but a âoelanguageâ where variable type is determined by the scripting engine, interpreted based on context, and can change on the fly is well...poop. How anyone writes solid and reliable code is beyond me.

      This is why languages such as TrueScripr and Transpilers have become popular - they provide order to a chaotic scenario and a way to herd cats.

      • Re: (Score:2)

        by Sique ( 173459 )

        How anyone writes solid and reliable code is beyond me.

        That's easy. Just write a Fortran Compiler in ECMAscript first.

      • You are not old fashioned. You are a hipster.
        Old fashioned languages are dynamic typed but typesave.
        How anyone writes solid and reliable code is beyond me.
        1) discipline
        2) knowledge
        3) unit tests
        Unit tests where pushed in the Smalltalk circles. Unfortunately since Kent Beck wrote JUnit now half the people who read books like Clean Code think every class in a statically typed language needs a unit test.

        • Hipster? Think not. Iâ(TM)ve been doing this since the mid-70â(TM)s. JS is an ugly language.

          If, once a type is assigned to a variable, the type couldâ(TM)t change during application execution, Iâ(TM)d be less critical of it. But, the lack of type safety makes it very difficult to write solid, safe, code.

    • People was insane amounts of energy rebranding and rewriting things that are DONE already. UI people are the worst justifying their employment with BS changes; marketing is second...

      ECMAScript is the name; almost nobody uses it. A rebrand will not succeed only help the IT profession climb from the top 5 professions with the most jargon.

      Javascript was like a scripting version of C with objects. It's evolution is making it C++ script where it's trying to be everything to everybody. The fact it's now included

      • "Javascript is pretty good duct tape;"

        How true.

        Perhaps JavaScript should be renamed to DuctTape to reflect it's usage. While we are at it, WebAssembly can be renamed to ChickenWire to reflect how it is intended to be used. That way, you will have crap that runs in the browser (which should be just a display engine) being built with DuctTape and ChickenWire ... an apropos description of what a crock they in fact are in reality.

        Wanted: HTML Display Engineer fluent in DuctTape and ChickenWire to cobble toge

  • Let's call it Steve.

  • I renamed it long ago (Score:5, Insightful)

    by nospam007 ( 722110 ) * on Sunday October 27, 2019 @04:55AM (#59351840)

    I call it Noscript on my machine.

  • Putting lipstick on that pig won't help it.

  • Any manager or recruiter who doesn't understand there is a difference between JavaScript and Java needs to be out of the position that has them making choices for roles that use it... no excuse for that by now.

    • The problem is that managers are often appointed by executives to lead departments because they have an MBA and nothing more.

  • So, the name reflects the state of the language (Score:3)

    by GuB-42 ( 2483988 ) on Sunday October 27, 2019 @06:11AM (#59351932)

    The naming is a mess, the language is a mess. There are differences between interpreters/compilers and you have to support them all, or use tools that translate one variant to another variant.

    Nothing against the language itself though. It is not $otherlanguage but it does the job. Support is the problem.

    • That's not unlike dealing with supporting 3 or 4 different IE versions plus Mozilla, plus Chrome, and now Edge. (though mostly the problem was IE)
  • ...rename it to Betteridge [wikipedia.org].

  • That will also immediately give people a good appreciation as to what it is and what it can do. Or maybe scrap it completely and use PhP, hardly any difference.

  • Name changes never work (Score:4, Interesting)

    by hackertourist ( 2202674 ) on Sunday October 27, 2019 @07:15AM (#59352024)

    Changing the name of anything that's well-known under its old name is a recipe for disaster. It's even worse for something that will generate lots of questions (like a programming language) because the namechange will nuke the entire repository of existing resources and make everyone's life more difficult.

    Face it: this ship sailed a long time ago, and you're stuck with the current name.

    • What's even worse is to rename it to a super common word already in use. Like "There". Now imagine trying to use google to search for a solution to a programming problem with that language.

      Google: object inheritance with there

      The results would be nonsensical.

  • Gosling originally renamed Oak to Java.
    ECMAScript was renamed to Javascript.

    To follow the same twisted login, I proposed we rename Javascript to "Oak" in honor of Gosling's Oak tree that proudly stood outside his office at Sun Microsystems where he developed Java.

    Even though Java and Javascript have nothing to do with each other, I still propose the name "Oak" in honor of the tree that started that whole Java craze.

    Anyone want to sign my rename petition for W3C?

  • I thought of a great name. (Score:5, Funny)

    by Dunbal ( 464142 ) * on Sunday October 27, 2019 @07:45AM (#59352106)
    Why not just call it "Deprecated"?

  • This ship sailed 25 years ago. And, given the state of what Oracle is doing to Java, in 5 years this won't even be a concern for the ignorati.

  • Then people will soon discover the same code behind the new name...
    Fix the code, change to something better.
    A name change cant hide the existing results...

  • If you are coding to the standard, you're using ECMAScript. If you are writing a Node app, you're using Node.js. If you are making front-end web pages, you are using JavaScript. Why is this so challenging for people?

    C/C++ doesn't have a cute logo. Why the fuck does a programming language need a logo? What problem are you trying to solve?

    Stop the nonsense. There's no ambiguity unless you choose to speak with ambiguity. There's no trademark concern from Oracle, because they haven't defended their trade

  • Or maybe C++Script?
    RubyScript?
    PythonScript?
    ForthScript?
    PL/1Script?
    DigiCompScript?

    No, wait: VBScriptScript!

  • And no mascot, please

  • ... it should be replaced.

  • I can hardly count the times I was discussing technologies and solutions with non-IT people only to notice 2 days in that they are mixing up Java and JavaScript. It's a little late now for renaming, but better late than never.

    Just please give it a distinct name. WebScript, DynaScript or something like that actually would make sense. But please do *not* call it SomethingJS - that would be really stupid.

    My 2 eurocents.

  • I nominate ... (Score:5, Funny)

    by PPH ( 736903 ) on Sunday October 27, 2019 @10:25AM (#59352512)

    ... Scripty McScriptface.

  • There isn't even an official logo for JavaScript, let alone a cute mascot like Go's gopher or PHP's elephant

    Oh the humanity! How did we ever get this far without one!?!

  • Yes there are many disadvantages about it but what kind of things should replace it?
    For the record, I think we do need a logo.
    It should be a concave nonagon with a cursive 'C' in it, just to confuse people.

  • ...this is one of those topics that /. posts pretty much on an annual basis.

  • Memory Check (Score:3)

    by AlanObject ( 3603453 ) on Sunday October 27, 2019 @12:06PM (#59352714)

    This related to the topic but I wanted to see if anyone remembered the following:

    Is it true that JavaScript got named that because at the time Java was getting all the media hype so someone thought it would be a good idea to try to hitch onto that hype? This would be the early-to-mid '90s.

    Who was it that said "Javascript is the industry's most feared language?"

Slashdot Top Deals

"The vast majority of successful major crimes against property are perpetrated by individuals abusing positions of trust." -- Lawrence Dalzell

Close