nballerina VS SSVM

oh boy -- lot's of work ahead for you folks, best of luck! I'll be watching this project. We do a ton with GCP so when this matures we'll be looking at it more.

How do you compete with -- if at all -- with Ballerina lang? https://ballerina.io/

PS: This advice stems from my personal experience while building BallerinaLang. We spent the first two to three years working with our own bytecode interpreter before we transitioned to JVM bytecode. Our LLVM backend is still under development and has a long way to go.

Considering your rich background in C++ and Haskell, along with your interest in functional programming paradigms, I wouldn't necessarily predict that Ballerina will "blow your mind." However, you might find certain familiar syntax while encountering numerous "why?" questions.

Ballerina actually showed some innovative ways to do it and is an interesting language to keep an eye on... finally, Unison decided to focus on its cloud offering and seamless distributed functional programming. Also a really cool language.

Last week I found Ballerina (https://ballerina.io/) via a comment here on HN, which got me thinking that I've gotten a bit out of touch with newer/up and coming languages in development. My guess is that, if I missed Ballerina before a week ago, I've probably missed quite a bit more.

What have I missed? And it would be cool to see where people are finding these types of things too.

https://ballerina.io/ and https://www.asyncapi.com/ seem like two efforts to move in this direction a bit for web APIs.

Reminds me of https://ballerina.io/

... which looks actually pretty nice, but I suspect the name of the project is a terrible marketing decision that will hold adoption back ¯\_(ツ)_/¯

WasmEdge GitHub address: https://github.com/WasmEdge/WasmEdge.

I see that they recently changed the intro of WasmEdge on Github [1] to " WasmEdge is the easiest and fastest way to run LLMs on your own devices. "

Since it's a wasm runtime capable of many things I find bizarre that they now start describing it with a ultra-specific use case

- [1] https://github.com/WasmEdge/WasmEdge

Mmm…

The wasm-nn that this relies on (https://github.com/WebAssembly/wasi-nn) is a proposal that relies of arbitrary plugin backends sending arbitrarily chunks to some vendor implementation. The api is literally like set input, compute, set output.

…and that is totally non portable.

The reason this works, is because it’s relying on the abstraction already implemented in llama.cpp that allows it to take a gguf model and map it to multiple hardware targets,which you can see has been lifted here: https://github.com/WasmEdge/WasmEdge/tree/master/plugins/was...

So..

> Developers can refer to this project to write their machine learning application in a high-level language using the bindings, compile it to WebAssembly, and run it with a WebAssembly runtime that supports the wasi-nn proposal, such as WasmEdge.

Is total rubbish; no, you can’t.

This isn’t portable.

It’s not sandboxed.

If you have a wasm binary you might be able to run it if the version of the runtime you’re using happens to implement the specific ggml backend you need, which it probably doesn’t… because there’s literally no requirement for it to do so.

There’s a lot of “so portable” talk in this article which really seems misplaced.

WasmEdge isn't there yet: https://github.com/WasmEdge/WasmEdge/issues/1122#issuecommen...

Example 1: Analyze the content and risks of each commit in the PR. Then make a summary. https://github.com/WasmEdge/WasmEdge/pull/2394#issuecomment-...

There has also been a few "cloud-native" runtimes based on WASM, like WasmEdge but there's a few others (can't remember their names!)...