3 ms·

Yea - but that's offered by all modern languages, and they're not tied to one particular IDE since LSP took off.

masklinn 4y ago
> that's offered by all modern languages I see you've yet to meet Scala. > they're not tied to one particular IDE since LSP took off. There's at least one language server for Kotlin. I'm not even a interested in (let alone a user of) Kotlin, but you seem to have a very not-objective view of it for some reason.
- the_gipsy 4y ago
  Are you saying Scala has bad code analysis? I recall it being as good as Java's. Anyway, that's just a matter of defining "modern languages" then. > There's at least one language server for Kotlin. I didn't say there is none, I said that any modern language has one. An IDE is not a selling point anymore, in my humble opinion. > you seem to have a very not-objective view of it for some reason I just think that shoehorning Kotlin into "the go niche" is absurd , and that the "good code analysis" argument is moot.
  - shakow 4y ago
    > I just think that shoehorning Kotlin into "the go niche" is absurd That's what you say, but you don't really tell us why.
    - the_gipsy 4y ago
      It's not my burden of proof. If you think something like compiling kotlin instead of running a JVM is akin to compiling with go tooling, then at this point anything that somehow compiles to native (and beyond) is in the "go niche".
      - masklinn 4y ago
        > It's not my burden of proof. You're the one asserting that it's unsuitable. So it very much is. > If you think something like compiling kotlin instead of running a JVM is akin to compiling with go tooling, then at this point anything that somehow compiles to native (and beyond) is in the "go niche". I don't know about the other commenters, but that's literally the only criteria you've deigned offer so far, aside from some sort of conspiratorial implications.
        the_gipsy 4y ago
        So if I say <any language> is in go's niche, it's your burden to disprove it? Look, this is getting ridiculous. Go offers easy+fast tooling out of the box. Any JVM language, compiled or not, will never be anywhere NEAR go's tooling in those terms. The extra compilation layer just makes it actually much worse. And I don't even find go particularly appealing.

> that's offered by all modern languages I see you've yet to meet Scala. > they're not tied to one particular IDE since LSP took off. There's at least one language server for Kotlin. I'm not even a interested in (let alone a user of) Kotlin, but you seem to have a very not-objective view of it for some reason.

the_gipsy 4y ago
Are you saying Scala has bad code analysis? I recall it being as good as Java's. Anyway, that's just a matter of defining "modern languages" then. > There's at least one language server for Kotlin. I didn't say there is none, I said that any modern language has one. An IDE is not a selling point anymore, in my humble opinion. > you seem to have a very not-objective view of it for some reason I just think that shoehorning Kotlin into "the go niche" is absurd , and that the "good code analysis" argument is moot.
- shakow 4y ago
  > I just think that shoehorning Kotlin into "the go niche" is absurd That's what you say, but you don't really tell us why.
  - the_gipsy 4y ago
    It's not my burden of proof. If you think something like compiling kotlin instead of running a JVM is akin to compiling with go tooling, then at this point anything that somehow compiles to native (and beyond) is in the "go niche".
    - masklinn 4y ago
      > It's not my burden of proof. You're the one asserting that it's unsuitable. So it very much is. > If you think something like compiling kotlin instead of running a JVM is akin to compiling with go tooling, then at this point anything that somehow compiles to native (and beyond) is in the "go niche". I don't know about the other commenters, but that's literally the only criteria you've deigned offer so far, aside from some sort of conspiratorial implications.
      - the_gipsy 4y ago
        So if I say <any language> is in go's niche, it's your burden to disprove it? Look, this is getting ridiculous. Go offers easy+fast tooling out of the box. Any JVM language, compiled or not, will never be anywhere NEAR go's tooling in those terms. The extra compilation layer just makes it actually much worse. And I don't even find go particularly appealing.