native-messaging-c VS Scala.js

Ultimately what I am trying to do is test the simplicity and efficiency of using a local server versus using Native Messaging, which I have working https://github.com/guest271314/native-messaging-c, https://github.com/guest271314/captureSystemAudio/blob/master/native_messaging/capture_system_audio/capture_system_audio.c.

Yes. I use Native Messaging to do that as well https://github.com/guest271314/native-messaging-c. Far less overhead cf. HTTP. Nonetheless I am trying to improve the implementation.

I would suggest sending valid JSON. Here is a Native Messaging host written in C which sends JSON to the client https://github.com/guest271314/native-messaging-c.

I will probably adjust the variable names in your code and publish here https://github.com/guest271314/native-messaging-c including link to your answer.

For the C version which is now just an echo of input https://github.com/guest271314/native-messaging-c/tree/main repeat steps 1.-6. Instead of pinning the icon to address bar, navigate back to chrome://extensions, click "service worker" which will open a DevTools window for the background MV3 ServiceWorker context, then run this code in the console

`$` does mean end of input in Java, unless you explicitly ask for multiline mode. In the latter case it means `(?=$|\n)` if also in Unix-lines mode, and the horrible `(?=$|(?I wrote a compiler from Java regex to JavaScript RegExp, in which you'll find that particular compilation scheme [1].

[1] https://github.com/scala-js/scala-js/blob/eb160f1ef113794999...

Links: - https://dotty.epfl.ch/ - https://scala-native.org/en/stable/ - https://www.scala-js.org/ - https://typelevel.org/ - https://zio.dev/ - https://github.com/scala-native/scala-native/pull/3120 - https://github.com/lampepfl/dotty/pull/16517 - https://dotty.epfl.ch/docs/reference/experimental/index.html - https://scala-cli.virtuslab.org/ - https://scalameta.org/metals/ - https://docs.scala-lang.org/scala3/guides/migration/compatibility-intro.html - https://www.scala-lang.org/blog/2023/04/18/faster-scalajs-development-with-frontend-tooling.html - https://www.scala-lang.org/blog/2022/08/17/long-term-compatibility-plans.html

> Scala choices were directly dictated by JVM

Initially, yes. But Scala has evolved beyond the JVM, with Scala.js [1] being rock-solid, and Scala Native [2] under development. Neither are truly hampered by the initial JVM roots of Scala.

> Scala gives you a better horse

Weird analogy ;)

[1] https://www.scala-js.org/

Have you had a look at Scala.js yet? Also see "Scala.js for JavaScript developers." and "Tour of Scala."

What does that have to do with language size? It also compiles to js https://www.scala-js.org/ and native https://scala-native.org/en/stable/

Here's a hybrid option: Scala.js. Yes, it is about building web applications but in Scala. You can retain the HTML/CSS/JS knowledge you have but build web applications from a typesafe and powerful language: Scala

The compiler crash in question affects another feature that we would like to merge for the benefit of all users, namely https://github.com/scala-js/scala-js/pull/4735. Keeping 2.11 means that testing and shipping that feature is much more difficult, even for 2.12+ users only. It's not just "to fix a compiler crash".

TS is more in the "mixed feelings" department, imho.

I would take Scala.js anytime instead. (If I would need to do front-end ever again).

https://www.scala-js.org/