Kategory VS coffeescript

Yeah, it has nice funcional capabilities and libraries (like Arrow[0]).

[0]: https://arrow-kt.io

Last but not least, Scala is currently the language with one of the best effect systems in my opinion (https://zio.dev/). Kotlin for example has copied the approach with https://arrow-kt.io/ which I think is great actually. But when comparing Scala and Kotlin here, Scala wins by a large margin, it is a completely different world. It's like building a highly concurrent system in Erlang vs C.

Of course, if you don't want to learn things like union types, traits/typeclasses and effects (similar to async/await but more powerful) you will be annoyed by Scala. But once you learned them, you can never go back.

In my own code, I started to use explicit error handling. I'm currently experimenting with Result (from https://github.com/michaelbull/kotlin-result) and Raise (from https://arrow-kt.io/).

Are there any more-or-less established functional crates in Rust (similar to Kotlin’s Arrow)?

I wonder how the community sees adding Arrow besides standard Kotlin language features. Is it something that's still considered useful or just redundant and causing more confusion?

You can define a function like context(EitherEffect) suspend fun MyType.bind(path: String)like the ones in https://github.com/arrow-kt/arrow/blob/b608a054a5318fe57d7055c35bb64a5effb053b6/arrow-libs/core/arrow-core/src/commonMain/kotlin/arrow/core/computations/either.kt

That said, there are ways to embrace the JS ecosystem without actually using JavaScript. Many popular languages have transpilers that will convert code written in that particular language into something that will run natively in a web browser (in other words, JavaScript). Even TypeScript is a language that gets transpiled into JavaScript, so it's not that outrageous of a concept, it just gets more difficult to do the further you get away from languages that don't already look like JavaScript.

As a front-end web developer, do you still use CoffeeScript or jQuery? Unlikely, as TypeScript, ES/TC39 and Babel (and the retirement of Internet Explorer thanks to @codepo8 and his EDGE team) have helped to transform JavaScript into some kind of a modern programming language.

CoffeeScript

On the other hand, companies choose React because that's where all the developers are. If you want to build something that can be maintained years from now, you better not choose the next hype train that goes straight to nowhere (remember CoffeeScript ?). You want something battle tested that has stood the test of time, where you won't have trouble finding developers to scale once you need to. And nobody ever got fired for choosing React.