Slashdot Mirror


Java and JavaScript Remain the Top Enterprise Developer Languages For the Cloud, Survey Finds (zdnet.com)

Programmers may love hot newer languages like Kotlin and Rust, but according to a Cloud Foundry Foundation (CFF) recent survey of global enterprise developers and IT decision makers, Java and Javascript are the top enterprise languages. ZDNet: That said, the CFF also found [PDF] that, "More and more, businesses are employing a polyglot and a multi-platform strategy to meet their exact needs." The CFF discovered 77 percent of enterprises are using or evaluating Platforms-as-a-Service (PaaS); 72 percent are using or considering containers; and 46 percent are using or thinking about serverless computing. Simultaneously, more than a third (39 percent) are using all three technologies together. For companies this "flexibility of cloud-native practices enables [companies to move] away from a monolithic approach and towards a world of computing that is flexible, portable and interoperable." That means, while Java and JavaScript are only growing ever more popular, the larger the company, the more languages are used. After the Java twins, C++, C#, Python, and PHP are the most popular languages.

101 comments

  1. Enterprisey enterprise things top enterprise. Duh. by Anonymous Coward · · Score: 0

    The title alone could have won at the buzzword bingo.

    I recommend reading thedailywtf.com to anyone who wants to know what "enterprise" means.
    That "cloud" stands for "clueslees luddite’s offshore unprotected disks" is already clear, so I don't have to explain it.

  2. Java twins by Anonymous Coward · · Score: 0

    If they're twins they're definitely not identical, and one's good and the other is evil.

    1. Re:Java twins by Megol · · Score: 1

      Which is which?

    2. Re:Java twins by bobbied · · Score: 1

      If they're twins they're definitely not identical, and one's good and the other is evil.

      They don't share common DNA, other than being programming languages from the distant ancestor known as great, great grand daddy "C". They are not even close to twins, they are not even siblings. They are more like 2nd cousins twice removed and then only by marriage.

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    3. Re:Java twins by Anonymous Coward · · Score: 2, Insightful

      [Disclaimer: I'm not the GP AC, but the subject of his message should have given you a clue.]

      Java is good. In an A/B comparison, the best feature of Java vs Javascript are: static type, and it's shipped as a binary instead of text. On a wish-list of language features, Java's biggest flaw is the lack of value types and references.

      Javascript is pure evil. It has dynamic type w/ surprising/evil implicit conversions. Furthermore, it has whitespace-sensitive parsing that requires the careful use of dangling curly braces if you want to avoid being a victim of the 2nd worst form of parser-evil ever inflicted on developers (the worst being Python).

      tl;dr: Java is almost a great language. Javascript is a burning turd that we only tolerate because it's available in all web browsers.

    4. Re:Java twins by Anonymous Coward · · Score: 0

      The trick to using JavaScript (node.js) in an enterprise setting is not to use Javascript directly, but rather to use TypeScript. It eliminates (almost) all the evils of JavaScript.

    5. Re:Java twins by Anonymous Coward · · Score: 0

      Javascript is absolutely not whitespace-sensitive. Where the hell did you get this stupid idea? Are you a first-year "full-stack" barista with no knowledge of how software works? The only meaningful whitespace in Javascript is a newline, and that can only matter in very specific cases where some clueless moron has split a return statement across two lines like

      function f(x) {
          return
              x+1;
      }

      Also, Java is garbage. I shouldn't have to run a bloated goddamn virtual machine just to perform some console tasks.

    6. Re:Java twins by Oligonicella · · Score: 1

      Furthermore, it has whitespace-sensitive parsing

      So, you admit you don't use or understand JavaScript.

    7. Re:Java twins by Gr8Apes · · Score: 1

      Furthermore, it has whitespace-sensitive parsing

      So, you admit you don't use or understand JavaScript.

      My guess is he's using TypeScript or a similar bastardized mauling of JS.

      --
      The cesspool just got a check and balance.
  3. Re: Fuck Javascript by Megol · · Score: 0

    I admit to being a gay (happy) computer illiterate moron - but even I dislike Javascript.

  4. Java and Java Script? Really? by bobbied · · Score: 5, Interesting

    I wonder how many people polled didn't know that Java and Java Script are totally different things and if that skewed the results?

    --
    "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
  5. I would rather play jiggly ball with the orderlies by Anonymous Coward · · Score: 0

    Than read another goddamn slashdot post about which programming language is popular. Seriously this is getting old editors. It is not interesting and nobody cares about surveys. And you have posted at least five or six of these this year alone.

  6. Re:Java and Java Script? Really? by Anonymous Coward · · Score: 0

    To perhaps clarify: JavaScript in enterprise generally means Node.js.

  7. Really? by Anonymous Coward · · Score: 0

    You mean the language that's open source, standard, works as a base logic language interpreted within all browsers on planet earth and runs the client side, server side and database all in a singular easy to use syntax is popular?

    Well blow me down. Next you'll tell me water is wet and linux is better than windows

    1. Re:Really? by MobyDisk · · Score: 1, Insightful

      You mean the language that's open source, standard, works as a base logic language interpreted within all browsers on planet earth and runs the client side, server side and database all in a singular easy to use syntax is popular?

      Unfortunately no, the survey said JavaScript.

  8. "Enterprise", the cesspool for the unqualified. by Anonymous Coward · · Score: 0

    Can we stop with the buzzwords please? capcha: excrete...

  9. Legacy decision by Dunkirk · · Score: 3, Insightful

    I wonder how much of this is driven by a lack of vision, and simple inertia. I've used Rails as my main tool for 10-11 years, since the 2.x days. In the company I work for now, the one app I had written has been mothballed, and I was told I could no longer use it.* My choices were either .NET or Java, and that's simply because we had been an "IBM/Oracle shop" for 25 years, until we became a "Microsoft shop" since transitioning to O365. Because what I'm integrating with is all Java, I chose Java, but these days, to even try to compete against modern stacks, that implies Spring, and either Angular or React.

    My theory is that old, manufacturing-based companies are just locked into a mindset of "this is what we do," and that comes from an answer from 20-30 years ago. They don't care to optimize for IT tools, because it's not their expertise, and they're throwing money down the drain because the C-levels just play the game of hiring consultants to implement whatever Microsoft pays to put in the trade magazines. So we get H1-B's with, and outsource for, that skillset. And then the consulting industry educates and trains for this skillset, and it becomes a self-perpetuating legacy situation, a little like Cobol and mainframes. We just can't get away from it, because it's too hard to switch everything to something else.

    * The person responsible for the decision told me, "You're the only person in the company who knows it." I asked, "Rails is the most productive thing I've seen in 15 years; why wouldn't we hire for that?" I didn't get a response.

    I've come to the conclusion that I hate using Java for web apps.

    --
    Acts 17:28, "For in Him we live, and move, and have our being."
    1. Re:Legacy decision by Anonymous Coward · · Score: 0

      Should have gone with .NET. If you ignore the lousy built-in controls (datagrids and whatnot) it's surprisingly quick to develop with. You don't even need Visual Studio, you can compile your backend into DLLs with the Windows compiler and a short batch file.

    2. Re:Legacy decision by Anonymous Coward · · Score: 1

      Come to the dark side...server-side JavaScript!

      It will make you want to drop both Java and .NET cold turkey.

      It may even make you happy you stepped away from Rails.

      And JavaScript will not die not matter how many stakes you drive through its heart.

      It has taken over the UI/UX (Angular, React).

      It's making inroads to take over all the service layers (node.js).

      It is also taking over the data layers (NoSQL, such as MongoDB and CouchDB).

      One language to rule them all, and in the dorkness bind them!

    3. Re:Legacy decision by Tough+Love · · Score: 1

      I wonder how much of this is driven by a lack of vision, and simple inertia.

      How about idiocracy? The same effects make PHP popular, and keeps Perl around long past its expiry date. Not to mention Visual Basic, thankfully nearly dead now, but after causing how much damage?

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    4. Re:Legacy decision by Anonymous Coward · · Score: 0

      Almost nobody gives a shit what languages they use, ya weenie. People need to get paid and feed their families. I'll gladly use Visual Dipshit from MicroPenis if it puts food on the table.

    5. Re: Legacy decision by Anonymous Coward · · Score: 0

      Eh same thing at my company. I really don't care what I write something in but was shot down hard when I did something non-javascript, as we didn't want to have to hire people that could also write in anything.

      It's a fair point.

    6. Re:Legacy decision by Billly+Gates · · Score: 2

      I remember back in the good old days of yore on slashdot where Perl was the coolest thing ever and would be the all new king of all languages like C++. It died out of nowhere as you would be modded -1 faster than you could say goatse 15 years ago on here if you dared say anything bad about Perl.

    7. Re:Legacy decision by loufoque · · Score: 1

      There is no good use of Java for anything.

    8. Re:Legacy decision by angel'o'sphere · · Score: 1

      But nevertheless many big internet companies completely run on Java or other languages running on the Java Virtual Machine.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    9. Re:Legacy decision by Anonymous Coward · · Score: 0

      yup, i would never hire you. any tool can be useful for any job. your opinions obviously prevent you from seeing reality from your predisposed beliefs.

    10. Re:Legacy decision by Oligonicella · · Score: 1

      Language "expiry date" = I want to play with a new toy, I'm bored with this one.

      Company systems are not the programmer's play toys regardless of the current collective outlook. They are something to develop and keep running for years. And that means boredom.

      If a system is working, it's working. The desire to redo the damn thing in a newer language is simply wanting to play with new toys. You build it and run it until it *actually* cannot handle either volume or speed, not until a newer language comes out.

    11. Re:Legacy decision by Gr8Apes · · Score: 1

      I wonder how much of this is driven by a lack of vision, and simple inertia.

      How about idiocracy? The same effects make PHP popular, and keeps Perl around long past its expiry date. Not to mention Visual Basic, thankfully nearly dead now, but after causing how much damage?

      Well, you can look at it as all those PHP, Perl, and VB projects as being potential clients for you to upgrade at some point in the future when they creak and fail or become unmaintainable for various reasons such as cost, stability issues, or merely time to get new features out to market.

      --
      The cesspool just got a check and balance.
    12. Re:Legacy decision by Gr8Apes · · Score: 1

      I wonder how much of this is driven by a lack of vision, and simple inertia. I've used Rails as my main tool for 10-11 years, since the 2.x days. In the company I work for now, the one app I had written has been mothballed, and I was told I could no longer use it.* My choices were either .NET or Java, and that's simply because we had been an "IBM/Oracle shop" for 25 years, until we became a "Microsoft shop" since transitioning to O365. Because what I'm integrating with is all Java, I chose Java, but these days, to even try to compete against modern stacks, that implies Spring, and either Angular or React.

      Well, your first problem is you're running Spring and Angular/React. Both of the latter are highly volatile toys of the moment (or at least were two years ago, I know, I know, ancient in web time but my current projects were all started prior to that) and Spring is COBOL for java apps. There are 1 or 2 useful things in Spring, but you need to be careful how you use it and quarantine it in your development.

      * The person responsible for the decision told me, "You're the only person in the company who knows it." I asked, "Rails is the most productive thing I've seen in 15 years; why wouldn't we hire for that?" I didn't get a response.

      I've come to the conclusion that I hate using Java for web apps.

      You know why Rails sucks and you can't find anyone in the corporate environment to run it? You can start with performance, security and maintainability over time. Corporate environments, at least the ones I work for, run upwards of thousands of transactions a second with millions upon millions of rows of data, hence the long project timelines, you don't turn the titanic in a couple of minutes. Those kinds of project timelines also attracts the interests of coders because of the relative job security. So you get lots of people interested in Java, and very few interested in the gee-whiz Rails thrown together in a week by 1 or 2 people project. Don't get me wrong, Rails has a place in the world - primarily quick POCs for basic workflows. But anything large-scale with reasonable throughput? Not a chance, and I'd double down on that since security will be a concern in any system I work with.

      --
      The cesspool just got a check and balance.
    13. Re:Legacy decision by PmanAce · · Score: 1

      Blazor for .Net will make javascript obsolete and build directly into WebAssembly and eliminating hundreds of js files needed for a clean angular site for example...bye bye loading all those files or making tons of needless requests per "page load".

      --
      Tired of my customary (Score:1)
    14. Re:Legacy decision by Tough+Love · · Score: 1

      So you're the guy who starts all those Node.js projects.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    15. Re:Legacy decision by Tough+Love · · Score: 1

      Have you ever tried to maintain a Perl script? A big one?

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    16. Re:Legacy decision by Tough+Love · · Score: 1

      Well, you can look at it as all those PHP, Perl, and VB projects as being potential clients for you to upgrade at some point in the future when they creak and fail or become unmaintainable for various reasons such as cost, stability issues, or merely time to get new features out to market.

      You could say the same about badly engineered bridges. How much damage will they cause in the process of falling apart?

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    17. Re: Legacy decision by Anonymous Coward · · Score: 0

      No good use... except for reliable, scalable, maintainable systems.
      But I will give you this, it is old, and I am restless, so I need a new toy to figure out. Oh wait, that's not me, it's you!

    18. Re:Legacy decision by Anonymous Coward · · Score: 0

      "Have you ever tried to maintain a C file? A big one?"

      You're supposed to split programs up into modules, you know. Perl can do that too. It's a fine language.

    19. Re:Legacy decision by Gr8Apes · · Score: 1

      You could say the same about badly engineered bridges. How much damage will they cause in the process of falling apart?

      There's lots of badly engineered bridges. Fortunately for us, most are designed with factors of safety and conservative enough assumptions that make them unlikely to fail during their intended lifespans. The problem occurs when someone stretches those numbers to achieve something for aesthetics or to go slightly further than before and slashes the factor of safety to something that can be corroded away with poor maintenance.

      --
      The cesspool just got a check and balance.
    20. Re:Legacy decision by sydbarrett74 · · Score: 1

      I watched a presentation on it and have been playing with the Github repo. It looks very promising.

      --
      'He who has to break a thing to find out what it is, has left the path of wisdom.' -- Gandalf to Saruman
  10. These surveys are stupid by MobyDisk · · Score: 3, Insightful

    The survey analysis seems to be written by people who don't understand programming at all. The conclusions are completely idiotic.

    First complaint: JavaScript is not a darling language everyone loves. It's the only language that runs on a web browser (*). So stop acting impressed or surprised at it's popularity! Duhhh!

    Check out some of these gems:

    But enterprise-sized companies are now using multiple languages for their projects. That's new. Historically, larger companies have practiced tighter control over production projects.

    Historically, we had the ability to use a single language. But we can't any more, because every project must be JavaScript + something + probably SQL. Yes, the "something" could be JavaScript, but that isn't usually the best choice on the server side. This isn't what we *want* it is what we are stuck with because of the browser. This conclusion would only seem meaningful if you were looking at the statistics over time, but had no idea what you were talking about.

    For students and programmers looking for a corporate job, it's clear the older languages are the way to go. The future is in the cloud, but its languages are decades old. At the same time, they'd be wise to pick up containers, cloud, and container manager

    I don't even know what this is saying. How can the future be old? Or the cloud, which is new, be using old languages? Then they confuse languages with containers. It almost looks like a Markov generator wrote this paragraph.

    the larger the company, the more languages are used.

    Wait, you mean having more projects means more languages? Well it cannot possibly mean LESS languages, so this conclusion is completely mindless!

    (*) Even if a developer codes in TypeScript, they would still answer "JavaScript" for survey purposes since it is never totally hidden.

    1. Re:These surveys are stupid by loufoque · · Score: 1

      I only write UIs for myself and I still use JavaScript for them. I don't care about using a web browser for ease of access.
      It has become the lingua franca of UI design. UIs are so fucking messy only a messy language can deal with them.

    2. Re:These surveys are stupid by angel'o'sphere · · Score: 1

      For the frontend you always could use something like GWT, Vaadin, Sencha. Yes, it gets compiled to HTML + JavaScript, but you develop, debug and test all in Java.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    3. Re:These surveys are stupid by MobyDisk · · Score: 1

      Just bear in mind that in this case, a developer will likely still answer "JavaScript" in a survey, since JavaScript is involved. So from a statistical standpoint it would still look like JavaScript was king. Maybe one day it will be treated more like machine code, and developers won't bother to learn it.

    4. Re:These surveys are stupid by PmanAce · · Score: 1

      Blazor (.Net) runs .Net in any browser through WebAssembly and removes the 100s of js files needed in angular/js frameworks. Welcome to the future.

      --
      Tired of my customary (Score:1)
  11. Shaggy says by Hognoxious · · Score: 1

    I am not Scottish, but if I were this would merit at least one jing. perhaps even a criven.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  12. Re:Fuck Javascript by Tough+Love · · Score: 1, Informative

    Only computer illiterate retards use Javascript.

    On server side, you mean. Choosing Javascript on server side really should be a firing offense when superior alternatives such as Go are available. Client side is an entirely different story, seeing as there is no alternative. But that doesn't make it right.

    While I'm in here: when the hell is Javascript going to get real integers? The fact that this has been treated as zero priority by the standards group shows you what level of talent goes into the Javascript ecosystem.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  13. Re:Fuck Javascript by h33t+l4x0r · · Score: 1

    There's some things that Javascript does better than anything else. Like asynchronous IO. If you don't think that might be important server side, then you're doing things that are very different from what I'm doing.

    Now, if I were doing math or science-y stuff, obviously I would choose something else.

  14. Re:Fuck Javascript by Anonymous Coward · · Score: 0

    I think the trade-off for dynamic typing should be automatically managed typing.

    Why do I need to worry about "actual integers" at all? If the expression only requires an integer, the language interpreter should use the smallest integer type necessary to store it. If the result of a calculation would overflow the type, double the size.

    If the expression requires promotion to floating point, just do it automatically. Why are we insisting on controlling things the computer is entirely capable of handling for us?

  15. Re:Fuck Javascript by Tough+Love · · Score: 2

    There's some things that Javascript does better than anything else. Like asynchronous IO

    Really? You need to read this. Average 1 microsecond per request. Let's see you do that in Node. (And this is supposed to be Node's strongest point, I just don't buy it.)

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  16. Re:Java and Java Script? Really? by Anonymous Coward · · Score: 0

    Haven't you heard yet? That is who businesses want to employ.
    All that complicated time-consuming 'software' stuff is outdated.
    Bring on the script kiddies.

  17. Re:Fuck Javascript by h33t+l4x0r · · Score: 1

    That's actually kind of impressive, the fact that he's comparing it to ruby performance notwithstanding.

  18. Re:Java and Java Script? Really? by Anonymous Coward · · Score: 0

    I wonder how many people polled didn't know that Java and Java Script are totally different things and if that skewed the results?

    Which of those being used most frequently for application development among enterprise developers worldwide is surprising?

    The one used for almost all enterprise software development worldwide , or the one used for almost all websites worldwide? It's a rhetorical question, Farley.

  19. Re:Java and Java Script? Really? by Anonymous Coward · · Score: 0

    To perhaps clarify: JavaScript in enterprise generally means Node.js.

    Java Script in the enterprise means Java Script written by an enterprise software developer
    vs.
    Java Script written by a web browser

    The survey was about languages in use, not where they execute.

  20. JavaScript or ECMAScript by Anonymous Coward · · Score: 0

    Did they pay off the Oracle lawyers to use the name?

  21. Node.js by Billly+Gates · · Score: 2

    The complexity of assembler with the efficiency of javascript.

  22. The significance of Javascript... by Larsen+E+Whipsnade · · Score: 1

    is that it's a proxy measurement for Web based applications. PHBs love their Web apps.

    And the real significance of this article is that what programmers want doesn't matter. Just take the money and write the code, code monkey. And try to forget why you went into software in the first place, because none of that matters anymore.

    1. Re:The significance of Javascript... by Oligonicella · · Score: 1

      And the real significance of this article is that what programmers want doesn't matter.

      Unless, of course, they are the ones shoveling money into the project. If I hire you, you do what I want and, yes, your desires don't enter into it. Software is not a friggin' "calling".

    2. Re:The significance of Javascript... by Anonymous Coward · · Score: 0

      This is a perpetual thorn in my side.

      When interviewing, employers see JavaScript on my resume and they take it to mean "this programmer likes/endorses/promotes JavaScript" as if I had a choice.

      It really means "I have worked jobs that required JavaScript."

  23. Re:Fuck Javascript by Anonymous Coward · · Score: 0

    Thats what a javascript guy did to me when i was a new programmer. i put up with it cause i needed a job and knew i couldnt get another on just yet. it hurts heaps especially when he just really needed to do it to me hard which was a lot. i dont know what his wife was doing as she was supposed to take care of his urges, but she acknowledged he was doing me as she didnt want his inside her apparently. she thanked me for it after i quit and had enough of his member in me. she said to cum back as soon as possible as she cant do it anymore with his member. he appareently just had one too big and it hurt her as well. he did push extremely hard but. he had a very hard member.

  24. Re:Fuck Javascript by loufoque · · Score: 1

    Serious people use C++.

  25. Re:Fuck Javascript by K.+S.+Kyosuke · · Score: 1

    There's some things that Javascript does better than anything else. Like asynchronous IO.

    ...what? If they're so good at that, why are they hiding it and forcing you into shitty half-baked hand-written continuations instead?

    --
    Ezekiel 23:20
  26. "Java twins"? by Anonymous Coward · · Score: 1

    The author of this article has never touched a line of code in his life.

  27. Node, Angular, React = garbage by Anonymous Coward · · Score: 0

    JS frameworks are for diploma mills churning out clueless Dunning-Kruger case studies as "full-stack", uh..."developers", who have no idea how software works and couldn't write a simple goddamn xmlhttprequest if their lives depended on it. Congratulations, your minimal website with a couple of buttons and an input form is now a 10-megabyte text "engine" that makes you write giant scope-sensitive statements just to get access to your own data. Oh wait, sorry, you can't actually get your own data, that's handled automatically by the conjunctivized transcleddled scopemagnet attridirective.

    1. Re:Node, Angular, React = garbage by micahraleigh · · Score: 1

      What kind of edge does a low level knowledge of underlying AJAX give you?

    2. Re:Node, Angular, React = garbage by Anonymous Coward · · Score: 0

      Not having to pull in several megabytes of backend just to make server requests. A faster and vastly slimmer frontend.

    3. Re:Node, Angular, React = garbage by Anonymous Coward · · Score: 0

      And there's barely anything to making an AJAX request. Even calling it it "low-level" is probably overstating its complexity on the JS side. It's a few fairly intuitive lines of code you can wrap yourself as necessary after spending a few minutes reading about online.

  28. Re:Fuck Javascript by Anonymous Coward · · Score: 1
  29. UIs are so messy that what? by Larsen+E+Whipsnade · · Score: 1

    I write my own GUI stuff and I use Python. I used to use Perl, which is a very, very messy language. I got fed up with that and switched.

    No regrets. A reasonably clean object-oriented language is what you want to tame the mess.

    Can't really defend the lambdas, but the rest of it... oh yeah.

    I've also done C++ with MFC, because PHBs. It's a bit of of a mess, but at least it's a fast mess.

  30. Re:Fuck Javascript by h33t+l4x0r · · Score: 1

    Hnm, bible sig. I better tiptoe around you.

  31. Toy languages not used for real work by guruevi · · Score: 1

    As much as Rust has its fanboys, the issue remain that it doesn’t offer many benefits over C and to get any real work done you have to write bindings in C anyway. And then you’re offered to write major issues into RFC where they get endlessly debated between Poettering-style purists and practicalists.

    A language should work, not ideally but practically. If I can’t write things natively because some idealistic thread or type safety issues that don’t agree with the real world (where we have things like OpenGL, interrupts and DMA) then the language is good for theoretical work only.

    --
    Custom electronics and digital signage for your business: www.evcircuits.com
  32. Re:Fuck Javascript by jellomizer · · Score: 1

    Except for the fact you really don't have alternatives if you need a Web Based Application of any complexity.
    JavaScript has its issues. But dealing with Javascript is better then trying to figure out how to deploy an application to hundreds of people. With different systems and security levels.

    Being that most applications are a form that you fill out, check to make sure the data is required is filled in correctly and then saved on a database somewhere else. Web Based Applications makes sense.

    Now JavaScript is the only common language that works across browsers.

     

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  33. Re:Fuck Javascript by jellomizer · · Score: 1

    The problem on the server side. If you are a company you need to be sure you can find staff to support your project. And not recode it every few years.

    Java Has been around for over 20 years now. There are a lot of Java Programmers out there.
    Go may be a better Language. But Google has a history of dropping technologies. And it may sometime be tricky to find a Go programmer in all areas.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  34. my favorite part of language popularity articles by pezpunk · · Score: 1

    ... is the impotent anger of the pedantic, whiny, irrelevant failures who can't stop complaining about the fact that they learned the wrong set of tools but refuse to admit it.

    --
    i could live a little longer in this prison
  35. Re: Fuck Javascript by phantomfive · · Score: 1

    Go is a fun language, and it's great for writing custom servers and deployment tools. That said, it just doesn't have the library support that Java has, and I would not recommend using it for standard enterprise software for that reason. It also has backwards compatibility problems when compared to Java.

    --
    "First they came for the slanderers and i said nothing."
  36. Re:Java and Java Script? Really? by bobbied · · Score: 1

    I once had a job interview where they asked me if I knew Java script. After discussing the job with them it became clear to me that they where looking for a Java programmer, not a Java Script jockey, but the interviewer didn't know the difference. I didn't figure it was my place to educate the guy. A couple of days later they wanted to discuss making me an offer, but I told them I didn't think the situation was a good fit for me.

    --
    "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
  37. Re:Fuck Javascript by K.+S.+Kyosuke · · Score: 1

    If you're of them theist crazies, do that.

    --
    Ezekiel 23:20
  38. Re:Fuck Javascript by Anonymous Coward · · Score: 0

    Convenience != Security. If you want more convenient, then prepare to be hit with security vulnerability.

  39. I use artisanly brewed languages. by FilmedInNoir · · Score: 1

    You've probably never heard of them.

    --
    Sig. Sig. Sputnik
  40. Re: Fuck Javascript by reanjr · · Score: 1

    Two words: Promise and await.

  41. Re: Fuck Javascript by K.+S.+Kyosuke · · Score: 1

    Seven words: Out of the frying pan, into the fire.

    (Scheme had promises around 1990, BTW. So JS is "only" a quarter century behind or so...)

    --
    Ezekiel 23:20
  42. Sponsored by your good friends at Oracle.. by Anonymous Coward · · Score: 0

    Sponsored by your good friends at Oracle..

  43. Let's Be Candid About This by Anonymous Coward · · Score: 0

    These languages are abysmal and truly disgusting.

    And there's no way, no waaay, I would be posting that to reduce competition in a field where I am making $125k + in a low cost of living state.

    None whatsoever !!

  44. Re:Fuck Javascript by Tough+Love · · Score: 1

    Go may be a better Language. But Google has a history of dropping technologies.

    Go is widely used outside Google both by individuals and enterprises. Go is entirely open source.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  45. Re: Fuck Javascript by Tough+Love · · Score: 1

    Go is a fun language, and it's great for writing custom servers...

    Right, like web backends. My point.

    it just doesn't have the library support that Java has

    Go's FFI (foreign function interface) gives efficient access to C libraries, which is to say, pretty much everything you need.

    I would not recommend using it for standard enterprise software for that reason..

    I was comparing Go to Node.js, remember? Anybody who chooses Node.js for a web server backend should be fired before they spread, I stand by that.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  46. Re: Fuck Javascript by phantomfive · · Score: 1

    I think you replied to the wrong comment.

    --
    "First they came for the slanderers and i said nothing."
  47. Re: Fuck Javascript by Tough+Love · · Score: 1

    That would be another flaw in your thinking.

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  48. Serverless by Anonymous Coward · · Score: 0

    Can we please agree not to use that word in a "technical" article unless we ACTUALLY mean software that runs on brains or something? It's stupid marketing babble like Salesforce "no software" slogan. Uh, they are a SaaS company of course they use software. Ugh

  49. Re: Fuck Javascript by phantomfive · · Score: 1

    You should go reply to the guy who was talking about JavaScript. I was replying to someone who was talking about Java.

    --
    "First they came for the slanderers and i said nothing."
  50. Re: Fuck Javascript by Tough+Love · · Score: 1

    Four posts back: "Choosing Javascript on server side really should be a firing offense". Two posts back: "I was comparing Go to Node.js, remember?" Did you really just do what you did? Are you really that wrapped up in yourself?

    --
    When all you have is a hammer, every problem starts to look like a thumb.
  51. Re: Fuck Javascript by reanjr · · Score: 1

    Most of us use tech based on what it does today, not on what the tech landscape looked like 25 years ago.

    If you prefer to use state of the art 90s tech, go ahead.

  52. Re: Fuck Javascript by K.+S.+Kyosuke · · Score: 1

    Fortunately my state-of-the-art 90's tech is a decade or two ahead of yours "today's tech", so I'm rather happy with it.

    --
    Ezekiel 23:20