scala VS rust

Scala - Popular in the data-science world, particularly when working with distributed data processing (e.g. Spark). Lots of large companies have dedicated data teams that process the huge amount of analytics and other data the games produce.

The definition of List is three lines of code and all the methods can be implemented in terms of foldLeft and prenend, and foldLeft itself can be implemented in terms of a simple tail-recursion. How can that not be simpler than Vector which has a lot of subclasses, casting, overrides, etc: https://github.com/scala/scala/blob/2.13.x/src/library/scala/collection/immutable/Vector.scala

It says: "Scala stairs at cole polytechnique fdrale de Lausanne inspired the Scala logo (http://www.scala-lang.org) designed by Gilles Dubochet."

www.scala-lang.org

I took a look at some Haskell; like I said, I never actually learned it, but I have seen some. And I briefly dipped my toes in Scala awhile back, and it seemed like a good thing. And then came the Phoenix web framework drawing heavily on the general concepts of Rails but with the slightly different philosophy of making things more explicit rather than the infamous Rails magic, which is so helpful when you're doing things the Rails way. But if you try to fight it at all, no, no, no, that magic is a plus-five sword against you. [laughter]

It's not that I'm forced directly, but, well, there is a reason why Android apps are in very big part done in Java and Kotlin. The Android virtual machine, ARM, is not 100% compatible with standard JDK - and it looks like a deliberate decision that Google didn't put effort into making it compatible. With this in place - and with Kotlin being the one language backed up by Google for writing apps on Android - if you use anything else, you may run into some problems sooner or later. They are not unfixable, but it is an uphill battle, while in the same time everywhere you turn you will find comments along the lines of "why bother, just switch to Kotlin". And since Google is so big, this pressure is big enough to demotivate people from working on other solutions. Instead, they work on solutions supported by Google. Which creates an avalanche effect - it gets even easier to work in what Google backs up, and even harder to work in something else.

One of the new features in the recently released Selenium 4 is support for new event-driven listeners which will be powered by the currently-in-draft BiDirectional (or BiDi) protocol (though the current Selenium implementation has some limitations, which we'll discuss later). In this article we'll discuss some of these new capabilities and demonstrate how to use them in Scala to inspect console logs and network requests made from the browser.

Go to the scala homepage: https://www.scala-lang.org/

Sure. Espressif maintains a fork which adds support for their microcontrollers.

I am trying to make a vaccine passport validation for my country using the ESP32 for my micro controller. I have gotten the std rust library to compile using (esp-rs)[https://github.com/esp-rs/rust], but the actual validation library that I use needs openssl which refuses to compile.

Xtensa. They've got a fork of LLVM that supports it that they're working toward getting upstreamed. The community has a fork of rustc that uses it (and a quickstart crate) while we wait for it to get upstreamed.

It only works if you have an Xtensa compiler which takes hours to compile, here: Rust Xtensa (if you don't have it). The network driver is just a function that sets the name of the driver so the Esp32 does something other that blinking.