You can trivially use C libraries in Rust, or any system language that supports the C ABI for that matter, and this includes many hobbyist languages. Zig is not special.
BB_C
joined 3 years ago
You could have searched for some benchmarks yourself, instead of thinking you're winning an argument in such a stupid manner.
Note that Jarred himself (bun creator) wouldn't push against this either. Instead, he will sell you the aggregate performance talking point (as another user did), which is why I made my deliberately facetious comment about webshittery.
can execute TypeScript directly.
Did the word "directly" get the same fate the word "literally" got? As in, it completely lost its real meaning?
Bundling a compiler/transpiler and directing inotify at a source directory (for glorious hot-reloading) doesn't a language "runtime" make. Otherwise, I can create "runtimes" for any language in three lines of code right now.
unless youβre saying that Bun is slower.
Are you saying JavaScriptCore is faster than V8? Or is the majority of time in webshittery operations not spent on actually running code, and that's how bun "wins" ?
First of all. Strictly speaking, there is no such a thing as a TS runtime. TS compiles to JS.
Second of all, bun binds against JavaScriptCore, which is the JS engine used in Safari. Node binds against V8, which is the engine used by Blink (Chromium et al). Both are implemented in C++. And the latter is considered the fastest engine.
Ironically, both engines are mentioned by name in the very bun blog post being discussed, which points to a problem that is almost bigger than mere tech literacy from the pseudo-intellectual OP.
You can interface with a C++ JS engine without
unsafe(which is equivalent to just using C btw), if you just really put a real effort into it.
π
I do love me some internet gantry commentary. Especially when it's super confident and acting knowledgable, with multiple layers of genius on display.
You clearly don't even know what unsafe in rust means. And it's not something you can avoid when FFI is involved, slopping involved or otherwise.
Code viewing was always a part of rustdoc, and thus available via docs.rs. I actually don't like this violation of abstraction separation.
And doing this before doing the most obvious sensible trivial addition, a download link, is doubly ironic in my view.
I don't do Android (or much UI in general), but from what I gather, going with something like flutter_rust_bridge or membrane is probably the best route. The UI is not done in Rust. But it's as close as you can get for non-toy use-cases, and without bringing a JVM language into the fray.
Toyota people apparently developed membrane for serious production use. But I haven't used either, so I don't have first hand experience to share.
Bro forgot to demangle. And now the kids are scared.
view more: next βΊ
π€£ π€£π€£π€£π€£π€£