News for hackers. Stuff that matters.

A comment on We replaced our React front end with Go and WebAssembly. Parent comment

Re:We replaced our React front end with Go and WebAssembly by dtquad on Monday February 10, 2025 @11:34PM (#43009003)
Definitely. Although Go is the simplest language with sane/good concurrency support so it's a good fit for Node.js/TS and Python shops that have run into a use case where they feel limited by their main language or runtime and need a concurrent backend service to implement a feature.
[ Parent | on HN ]
Re:We replaced our React front end with Go and WebAssembly by jilles on Monday February 10, 2025 @11:38PM (#43009023)
Kotlin also has amazing concurrency support. Plus you get the additional benefit of the entire Java ecosystem.

I wish it got more love.

[ Parent | on HN ]
Re:We replaced our React front end with Go and WebAssembly by teg4n_ on Tuesday February 11, 2025 @12:05AM (#43009178)
Kotlin is not simple. it has like every language feature in existence
[ Parent | on HN ]
Re:We replaced our React front end with Go and WebAssembly by have-a-break on Tuesday February 11, 2025 @12:20AM (#43009265)
Why do people always mention kotlin, but not Scala?

Scala is more similar to traditional Java while letting functional programming shine.

[ Parent | on HN ]
Re:We replaced our React front end with Go and WebAssembly by valenterry on Tuesday February 11, 2025 @12:35AM (#43009345)
Scala is way superb for concurrency than what Go or Kotlin have to offer. But it is a complex language with a high learning curve.
[ Parent | on HN ]
Re:We replaced our React front end with Go and WebAssembly by pclowes on Tuesday February 11, 2025 @12:27AM (#43009300)
Honestly, I think it is because the Scala community was/is/can be so pedantic and bickering and often combative and toxic that it lost all momentum and appeal.

Nobody wants that culture in their workplace. Also the dysfunction is visible in the technical fragmentation of the ecosystem

[ Parent | on HN ]
Re:We replaced our React front end with Go and WebAssembly by re-thc on Tuesday February 11, 2025 @12:55AM (#43009437)
> Why do people always mention kotlin

It's backed by $$$ that have promoted it that way - a "better" Java.

[ Parent | on HN ]
Re:We replaced our React front end with Go and WebAssembly by MarkMarine on Tuesday February 11, 2025 @12:38AM (#43009359)
Kotlin’s structured concurrency and coroutines as a library are remarkable pieces of software engineering. It’s a great language and ecosystem… but

Modern java has been grabbing features from all the “better Java” languages at such a pace that the big gap right now that I see is the question mark operator.

[ Parent | on HN ]
Re:We replaced our React front end with Go and WebAssembly by neonsunset on Tuesday February 11, 2025 @01:16AM (#43009568)
> I wish it got more love.

.NET is in the same predicament. Very convenient and highly efficient concurrency primitives.

[ Parent | on HN ]
Re:We replaced our React front end with Go and WebAssembly by hedora on Tuesday February 11, 2025 @01:18AM (#43009582)
Typescript’s concurrency story is much stronger than go’s.

Unlike Go, but like Rust, it has a reasonable type system, and is data race free (since JS is single threaded).

Anyway, I come from a C++/Rust background, but have been using TS recently, and it’s a much nicer language than I’d have guessed.

[ Parent | on HN ]