4 ms·

Yeah i really don't understand the advantage of go over c#. Async maybe?

kjeetgill 4y ago
I'd argue goroutines are a mostly better alternative to async. Maybe a bit less optimal for a vast improvement of ergonomics and applicability.
- quixoticelixer- 4y ago
  Yeah goroutines is what i meant by better async. I've used the clojure async stuff a fair bit which was heavily inspired by goroutines and it is quite nice.
- jpgvm 4y ago
  Goroutines are better than C# async/await but C# is still a better language than Go. When Java 19 lands you can have best of both worlds. Virtual Threads are equivalent to goroutines but you have access to better languages like Java, Kotlin and Clojure.
  - deleted 4y ago
    [deleted]
  - morelisp 4y ago
    I don't think virtual threads will be fully baked in time for production use at Java 19. IMO we'll be waiting at least one and probably two more releases. Valhalla has also produced an amount of language machinery that results in most of the same issues as Go. (E.g. "is this function receiving an interface or concrete value?" becomes "do I have a class, value class, or primitive class?") The performance ripples of requiring value objects to be immutable also remains to be seen.
    - jpgvm 4y ago
      True. I intend to start using them the moment they land in preview but there is still some caveats (namely how they interact with synchronized). I think by Java 21 they will be rock solid though which isn't really that far away in Java timescales.
      - kaba0 4y ago
        Aren’t they in preview in 19 already?
        jpgvm 4y ago
        Yes technically as they have been merged but 19 isn't out until September, you can download early-access builds today but we won't see a release build until the official release date.
      - morelisp 4y ago
        Sure, but by Java 21 we'll have Go 1.21 with a couple release cycles to push generics into stdlib, and we're back to more or less useless debates about aesthetic preferences and tooling priorities again.
    - kaba0 4y ago
      > The performance ripples of requiring value objects to be immutable also remains to be seen Immutability is trivial to optimize away.
  - zija 4y ago
    C# team began experimenting with green threads: https://twitter.com/davidfowl/status/1532880744732758018?t=PxcziaKHh84Ig5y3PP-45g&s=19 https://twitter.com/davidfowl/status/1532880744732758018?t=P...
    - jpgvm 4y ago
      Well that is very cool!
deleted 4y ago
[deleted]

I'd argue goroutines are a mostly better alternative to async. Maybe a bit less optimal for a vast improvement of ergonomics and applicability.

quixoticelixer- 4y ago
Yeah goroutines is what i meant by better async. I've used the clojure async stuff a fair bit which was heavily inspired by goroutines and it is quite nice.
jpgvm 4y ago
Goroutines are better than C# async/await but C# is still a better language than Go. When Java 19 lands you can have best of both worlds. Virtual Threads are equivalent to goroutines but you have access to better languages like Java, Kotlin and Clojure.
- deleted 4y ago
  [deleted]
- morelisp 4y ago
  I don't think virtual threads will be fully baked in time for production use at Java 19. IMO we'll be waiting at least one and probably two more releases. Valhalla has also produced an amount of language machinery that results in most of the same issues as Go. (E.g. "is this function receiving an interface or concrete value?" becomes "do I have a class, value class, or primitive class?") The performance ripples of requiring value objects to be immutable also remains to be seen.
  - jpgvm 4y ago
    True. I intend to start using them the moment they land in preview but there is still some caveats (namely how they interact with synchronized). I think by Java 21 they will be rock solid though which isn't really that far away in Java timescales.
    - kaba0 4y ago
      Aren’t they in preview in 19 already?
      - jpgvm 4y ago
        Yes technically as they have been merged but 19 isn't out until September, you can download early-access builds today but we won't see a release build until the official release date.
    - morelisp 4y ago
      Sure, but by Java 21 we'll have Go 1.21 with a couple release cycles to push generics into stdlib, and we're back to more or less useless debates about aesthetic preferences and tooling priorities again.
  - kaba0 4y ago
    > The performance ripples of requiring value objects to be immutable also remains to be seen Immutability is trivial to optimize away.
- zija 4y ago
  C# team began experimenting with green threads: https://twitter.com/davidfowl/status/1532880744732758018?t=PxcziaKHh84Ig5y3PP-45g&s=19 https://twitter.com/davidfowl/status/1532880744732758018?t=P...
  - jpgvm 4y ago
    Well that is very cool!

deleted 4y ago

[deleted]