https://kotlinlang.org logo
Channels
Powered by
#javascript
  • d

    danfma

    06/06/2016, 12:41 PM
    @hoang: Sorry, hoan! I'm not the soccer player and that was just a js dev environment question! 🙂
  • d

    danfma

    06/06/2016, 12:42 PM
    @bashor: yes, it's with maven and the kotlin2js. I'll create the issue.
  • s

    scottmmjackson

    06/07/2016, 2:40 PM
    Using JS Modules is a good call. The last thing client-side JS needs is another module/dependency injection standard.
  • s

    scottmmjackson

    06/07/2016, 2:41 PM
    Also opens the door to frameworks that lean a lot harder on >=ES2015 modules like Aurelia.
  • k

    konsoletyper

    06/07/2016, 2:41 PM
    @scottmmjackson: why another standard? There are Maven and Gradle
  • s

    scottmmjackson

    06/07/2016, 2:42 PM
    Maven and Gradle are build systems? It's not the same thing.
  • k

    konsoletyper

    06/07/2016, 2:45 PM
    Maven is not only a build system. It includes its own repository, dependency system and term called 
    artifacts
    which means roughly the same thing as 
    module
    in terms of ES
  • s

    scottmmjackson

    06/07/2016, 2:51 PM
    I'm not sure what the argument is. Sure, Maven is aware of artifacts and their dependencies, but anyone who consumes those artifacts and dependencies will expect them in RJS, CJS, or AMD format- for example, Webpack.
  • s

    scottmmjackson

    06/07/2016, 2:53 PM
    Either you're going way over my head or we're misunderstanding each other
  • k

    konsoletyper

    06/07/2016, 2:54 PM
    When I've been using GWT for front-end development for 3 years, I've never botherd myself with all these "webpack", "grunt", "AMD", etc things. Everything worked fine for me, and I didn't have to touch this ugly JS stack
  • k

    konsoletyper

    06/07/2016, 2:55 PM
    And I had a single stack and single ecosystem for both front-end and back-end, and even re-used some code between them
  • s

    scottmmjackson

    06/07/2016, 2:57 PM
    Very "get off my lawn" 😛
  • s

    scottmmjackson

    06/07/2016, 2:58 PM
    Not that it's not legitimate to talk about the tried-and-true
  • k

    konsoletyper

    06/07/2016, 2:58 PM
    And I was very happy, comparing to Angular, to refactor my code, since most of breaking changes could be reported by IDE. With Angular I was usually afraid to "touch this", since I could not predict what damage I can cause
  • s

    scottmmjackson

    06/07/2016, 2:59 PM
    Angular made a lot of mistakes. I'll be the first one behind you on the Angular hate train.
  • s

    scottmmjackson

    06/07/2016, 3:00 PM
    Though a lot of these new "ugly JS stack" things you talk about are really recognizing that Angular did kind of a mediocre job filling some legitimate needs
  • k

    konsoletyper

    06/07/2016, 3:01 PM
    Anyway, any JS stack is ugly for me as a Java developer
  • k

    konsoletyper

    06/07/2016, 3:02 PM
    It's like a schizophrenia, when you have to think in both of terms JS and Java, Maven and npm/grunt, checkstyle and jsLint, etc.
    😀 1
  • s

    scottmmjackson

    06/07/2016, 3:04 PM
    Only insofar as they're different languages for different platforms
  • s

    scottmmjackson

    06/07/2016, 3:04 PM
    And with entirely different demands on robustness for entirely different purposes
  • k

    konsoletyper

    06/07/2016, 3:05 PM
    They are not "for different purposes". They are because of "not invented here" syndrome
  • k

    konsoletyper

    06/07/2016, 3:06 PM
    I can see no advantages in using JavaScript for web instead of Java
  • s

    scottmmjackson

    06/07/2016, 3:08 PM
    Can you see no advantages in using interpreted languages over compiled languages in general? Or do you think that difference disappears with Moore's Law.
  • s

    scottmmjackson

    06/07/2016, 3:11 PM
    You may also have a point insofar as JS is transitioning to being essentially a compiled language now. A great deal of enterprise FE is being done in TypeScript targeting a minified artifact.
  • s

    scottmmjackson

    06/07/2016, 3:17 PM
    That having been said, I feel like a lot of the discussion leaves a huge gap between an All-Java-Everything Utopia the hordes of FE prototypers who want to connect module A to module B to API C in a way that preserves the validity of the documentation of each with a minimum of caveat.
  • s

    scottmmjackson

    06/07/2016, 3:19 PM
    I know, "oh no, app developers might have to do work"- but there's a reason frontend framework teams make so much money babysitting people.
  • p

    pabl0rg

    06/08/2016, 10:14 PM
    @konsoletyper: i am a GWT user, and also react, JS. I like GWT though it took getting used to, coming from a web world. Why do you think Google abandoned it? Because Java is boring?
  • p

    pabl0rg

    06/08/2016, 10:15 PM
    A lot of folks complained about the compile times, but grunt is just as bad and you get less-optimised output
  • t

    Tristan Caron

    06/09/2016, 11:17 AM
    @pabl0rg: When Google did it ? I thought they were still working on it, and they were using it with Inbox :O
  • p

    pabl0rg

    06/09/2016, 12:55 PM
    @Tristan Caron: yeah, but there hasn't been a release in 1.5 yrs and basically it's abandoned
1...144145146...306Latest