bkolobara

22 ms·

91.
by bkolobara 4y ago
There is no C API, but it would be a great addition. I assume that it would be just a thin wrapper around the host functions and the host functions are fairly good documented (e.g. https://github.com/lunatic-solutions/l
92.
by bkolobara 4y ago
I'm one of the creators of lunatic and it's great to see it on HN again. We have been working on a Rust web framework that builds on top of lunatic, called submillisecond[0]. It's still in alpha and there is a lot to be figur
93.
Submillisecond – A Rust Web Framework(github.com)
6 points by bkolobara 4y ago|0 comments
94.
by bkolobara 4y ago
> Async Rust is hard - and Rust in general is hard - because they don’t compromise performance for abstraction and encapsulation. I love Rust, but this is not completely true. Async Rust is hard because many nice features from Rust are n
95.
by bkolobara 4y ago
Almost all async Rust runtimes use a multithreaded work stealing schedulers by default, to equally utilise all available cores.
96.
by bkolobara 4y ago
Hi, author here. All examples should have used `lunatic::net`, I fixed it now. The reason why we provide `lunatic::net` and you can't just use `std::net` is that WASI (system interface for WebAssembly) still doesn't have support f
97.
by bkolobara 4y ago
I see a lot of people here saying something like "Just use Arc<Mutex>, it will be plenty fast". As someone who does it all the time, I noticed that code becomes less readable and hard to comprehend that way. Important types
98.
by bkolobara 4y ago
Lunatic Inc.| Rust Engineer | Remote We are building the next-generation distributed application platform inspired by Erlang’s principles: massive concurrency, soft real-time & fault tolerance. At the heart of it is lunatic, an open-sou
99.
by bkolobara 4y ago
With lunatic [0] we are trying to bring this to all languages that compile to WebAssembly. A few days ago I wrote about our journey of bringing it to Rust: https://lunatic.solutions/blog/writing-rust-the-elixir-way-1...
100.
Writing Rust the Elixir way – 18 months later(lunatic.solutions)
1 points by bkolobara 4y ago|0 comments
101.
Lunatic v0.9(github.com)
6 points by bkolobara 4y ago|0 comments
102.
by bkolobara 5y ago
I'm the author of a Wasm on the server side runtime[0] that focuses primarily on rust compiled to Wasm, and this question comes up quite often. Why compile to Wasm if you can compile to native code directly? To add to Radu's answe
103.
by bkolobara 5y ago
Yes, but if there are close to 0 games that don't require Rosetta, what's the point? Disclosing a theoretical emulation overhead that can't be proven would even be worse. It's either this or no comparison at all. And it&
104.
Complexity Has to Live Somewhere (2020)(ferd.ca)
3 points by bkolobara 5y ago|0 comments
105.
by bkolobara 5y ago
> Can you give some specific examples of the math and physics that you think are beyond the capabilities of a bright high school graduate (that seems like a reasonable minimum bar to expect for someone picking up a book targeted at fresh
106.
by bkolobara 5y ago
TUIs over ssh/telnet can be a lot of fun. Especially in cases where multiple people can interact with each other on the server. It simplifies the programming model as you only have one state on the backend that you render to multiple c
107.
Advent of Code '21 in hand written WebAssembly(wasm.builders)
2 points by bkolobara 5y ago|0 comments
108.
Lunatic 0.7 adds support for distributed process spawning and messaging(github.com)
2 points by bkolobara 5y ago|0 comments
109.
by bkolobara 5y ago
Fibers are usually implemented with stack switching. It should be the same approach.
110.
by bkolobara 5y ago
It's on the embedder (Wasm VM) to provide this functionality. I'm working on a Wasm runtime [0] that is written in Rust and uses stack switching to allow you to call Rust async functions as if they were blocking. This keeps the Wa
111.
by bkolobara 5y ago
I don't think that the red and blue teams are that much behind. A high end AMD mobile processor like the Ryzen 7 5800HS easily beats the current M1 in most CPU bound multithreaded workloads, like compile times. Even if the numbers are
112.
What if everything was a process?(github.com)
2 points by bkolobara 5y ago|0 comments
113.
Lunatic v0.6(github.com)
2 points by bkolobara 5y ago|0 comments
114.
by bkolobara 5y ago
Hi! Author of lunatic here. We are working on a distributed lunatic implementation built on top of nats.io.
115.
by bkolobara 5y ago
Thanks! Author of lunatic here. Processes don't share any memory, so the message will need to be copied from one process to another. This should be the biggest overhead involved when sending them. Erlang uses a trick for big binary dat
116.
Lunatic 0.5(github.com)
2 points by bkolobara 5y ago|0 comments
117.
Oracle Cloud Free Tier(oracle.com)
4 points by bkolobara 5y ago|0 comments
118.
What Makes Apex Tick: A Developer Deep Dive into Servers and Netcode(ea.com)
1 points by bkolobara 5y ago|0 comments
119.
Lunatic – Erlang-inspired runtime for WebAssembly(lunatic.solutions)
2 points by bkolobara 6y ago|0 comments
120.
by bkolobara 6y ago
You can find our recent HN Launch here: https://news.ycombinator.com/item?id=26367029

More ›