4 ms·

Usually said by Java developer not understanding JavaScript.

penprog 12y ago
You see, I barely need to "understand" Java to use it and get decent and performant code but I need to be a javascript expert to be able to do anything not horrible. Please stop trying to act like the state of web and javascript is good because it's shit. Web development is basically a bunch of people suffering from stockholm syndrome.
- woah 12y ago
  You've coded a lot in languages very similar to Java and that is an argument for Java's ease of use?
  - penprog 12y ago
    My argument was that the idea of having to work on a javascript project with >10,000 lines of code makes me want to vomit while the idea of working on a java project with >1,000,000 lines of code doesn't make me feel anything special. People that complain about verbosity really don't have their priorities in line
    - woah 12y ago
      The point of Javascript is that projects don't get to 10,000 lines. If a project is this big, you have failed. Bragging about LOC is one of the most ridiculous things ever, since it is a bad thing.
      - pjmlp 12y ago
        Have you ever gotten to review enterprise code done by multiple teams with offshoring?
      - deleted 12y ago
        [deleted]
- jekrb 12y ago
  Really? I feel js gives way more freedom and is much more forgiving to writing in your own particular style. I've had the exact opposite experience with Java. I write JavaScript all the time for work and hobby and it's always rewarding. Also, I'm in college for computer science and the school will only teach Java courses. It's dreadful and maddening. Classical inheritance is complete shit. Compiler error messages suck. The language itself is just too bloated for me to want use. Whatever I can write in Java I can do in a fraction of the time with js with much more modular and maintainable code. I think java interfaces are a clear sign of stockholm syndrome, as every time I asked the professor why they are necessary I never got an answer other than "to hide part of your code from the outside world", "to use as a blueprint for your classes", or my personal favorite "Because in Java you write interfaces." I tried shifting my question to "Why don't I have to write an interface in js?" That one never got answered. Maybe someone here who is crafty with Java could explain and justify for me the reason for writing what feels like more code for no obvious benefit. Also, sorry if Java is your thing and I sound like I'm bashing it. It's just been really frustrating for me compared to literally every other language I've used, especially since my degree depends solely on the language.
  - Dewie 12y ago
    > Also, I'm in college for computer science and the school will only teach Java courses. It's dreadful and maddening. Classical inheritance is complete shit. Compiler error messages suck. The language itself is just too bloated for me to want use. Whatever I can write in Java I can do in a fraction of the time with js with much more modular and maintainable code. Whoever likes writing Java in CS courses? > I think java interfaces are a clear sign of stockholm syndrome, as every time I asked the professor why they are necessary I never got an answer other than "to hide part of your code from the outside world", "to use as a blueprint for your classes", or my personal favorite "Because in Java you write interfaces." I tried shifting my question to "Why don't I have to write an interface in js?" That one never got answered. Maybe someone here who is crafty with Java could explain and justify for me the reason for writing what feels like more code for no obvious benefit. Almost all modern, statically typed languages have some equivalent of Java interfaces. Inheritance a la Java is controversial, but the concept of interfaces/signatures/typeclasses/traits is a very accepted language feature[1]. Maybe the benefit of it will become apparent to you once you have to write a project with more than 7 Java classes - or when you don't have to answer to lecturers that profess that you have to make all your throwaway course work super modular and generic. [1] Litmus test: even Go has it.
Dewie 12y ago
Can't I just take your glib statement and just reverse the roles (JS developer not understanding Java)? What makes JS development more misunderstood than Java development?
- mateuszf 12y ago
  Maybe the fact that Java developers expect "typical" object model in JavaScript which doesn't exist, and JavaScript developers can use lot of their constructs in Java just fine (with the exception of functions which are not very different in Java, just more tedious).
pjmlp 12y ago
Usually said by a JavaScript developer lacking a CS degree.
- mateuszf 12y ago
  Maybe, though in this case I'm a Java developer with CS degree.

You see, I barely need to "understand" Java to use it and get decent and performant code but I need to be a javascript expert to be able to do anything not horrible. Please stop trying to act like the state of web and javascript is good because it's shit. Web development is basically a bunch of people suffering from stockholm syndrome.

woah 12y ago
You've coded a lot in languages very similar to Java and that is an argument for Java's ease of use?
- penprog 12y ago
  My argument was that the idea of having to work on a javascript project with >10,000 lines of code makes me want to vomit while the idea of working on a java project with >1,000,000 lines of code doesn't make me feel anything special. People that complain about verbosity really don't have their priorities in line
  - woah 12y ago
    The point of Javascript is that projects don't get to 10,000 lines. If a project is this big, you have failed. Bragging about LOC is one of the most ridiculous things ever, since it is a bad thing.
    - pjmlp 12y ago
      Have you ever gotten to review enterprise code done by multiple teams with offshoring?
    - deleted 12y ago
      [deleted]
jekrb 12y ago
Really? I feel js gives way more freedom and is much more forgiving to writing in your own particular style. I've had the exact opposite experience with Java. I write JavaScript all the time for work and hobby and it's always rewarding. Also, I'm in college for computer science and the school will only teach Java courses. It's dreadful and maddening. Classical inheritance is complete shit. Compiler error messages suck. The language itself is just too bloated for me to want use. Whatever I can write in Java I can do in a fraction of the time with js with much more modular and maintainable code. I think java interfaces are a clear sign of stockholm syndrome, as every time I asked the professor why they are necessary I never got an answer other than "to hide part of your code from the outside world", "to use as a blueprint for your classes", or my personal favorite "Because in Java you write interfaces." I tried shifting my question to "Why don't I have to write an interface in js?" That one never got answered. Maybe someone here who is crafty with Java could explain and justify for me the reason for writing what feels like more code for no obvious benefit. Also, sorry if Java is your thing and I sound like I'm bashing it. It's just been really frustrating for me compared to literally every other language I've used, especially since my degree depends solely on the language.
- Dewie 12y ago
  > Also, I'm in college for computer science and the school will only teach Java courses. It's dreadful and maddening. Classical inheritance is complete shit. Compiler error messages suck. The language itself is just too bloated for me to want use. Whatever I can write in Java I can do in a fraction of the time with js with much more modular and maintainable code. Whoever likes writing Java in CS courses? > I think java interfaces are a clear sign of stockholm syndrome, as every time I asked the professor why they are necessary I never got an answer other than "to hide part of your code from the outside world", "to use as a blueprint for your classes", or my personal favorite "Because in Java you write interfaces." I tried shifting my question to "Why don't I have to write an interface in js?" That one never got answered. Maybe someone here who is crafty with Java could explain and justify for me the reason for writing what feels like more code for no obvious benefit. Almost all modern, statically typed languages have some equivalent of Java interfaces. Inheritance a la Java is controversial, but the concept of interfaces/signatures/typeclasses/traits is a very accepted language feature[1]. Maybe the benefit of it will become apparent to you once you have to write a project with more than 7 Java classes - or when you don't have to answer to lecturers that profess that you have to make all your throwaway course work super modular and generic. [1] Litmus test: even Go has it.

Dewie 12y ago

Can't I just take your glib statement and just reverse the roles (JS developer not understanding Java)? What makes JS development more misunderstood than Java development?

mateuszf 12y ago
Maybe the fact that Java developers expect "typical" object model in JavaScript which doesn't exist, and JavaScript developers can use lot of their constructs in Java just fine (with the exception of functions which are not very different in Java, just more tedious).

pjmlp 12y ago

Usually said by a JavaScript developer lacking a CS degree.

mateuszf 12y ago
Maybe, though in this case I'm a Java developer with CS degree.