> So it turns out this is not "unlike Rust", it's pretty much the same thing: if everything was built in safe rust, then it would be as safe. The communication of this point is not great at all, so much so I don't think it's purely informative.
Safe Rust still basically always links against unsafe C libraries though. Fil-C will only link against libraries compiled with Fil-C which makes for a vastly stronger guarantee.
Also, plenty of code written in Rust is not safe so "if everything was built in safe rust, then it would be as safe" does not hold. There's definitely no way to write safe inline assembly in Rust.
You should try RWX! You can trigger runs from the CLI for way faster feedback loops. The automatic caching is surprisingly good too. https://www.rwx.com/
We using Tonic.ai. Although I am interested in writing something myself; I suspect there are a lot of ways it could be improved such as generating the anonymized version more quickly.
At work we have anonymized dumps of our production data that we use for local development. This is extremely helpful as it allows testing things locally that would be completely unrealistic to setup otherwise. Your whole dataset might not be able to fit on a dev machine, but I'd guess in most cases you could create a subset of it that would be large enough to be useful for local performance work.
There are also an enormous number of ways to build insecure apps on AWS. I think the difficulty of setting up your own server is massively overblown. And that should be unsurprising given that there are so many companies that benefit from developers thinking it's too hard.
Here's the contents of a. Let me know if there are any other commands you'd like me to type.
```
handleCommandInput 1, buffer "" c 'j'
handleCommandInput 2, buffer "" c 'j'
after handleCommandInput, buffer 0x104c5b780"j" c 'j'
handleCommandInput 1, buffer "" c 'k'
handleCommandInput 2, buffer "" c 'k'
after handleCommandInput, buffer 0x104ca8b70"k" c 'k'
handleCommandInput 1, buffer "" c 'l'
handleCommandInput 2, buffer "" c 'l'
after handleCommandInput, buffer 0x104c5bab0"l" c 'l'
handleCommandInput 1, buffer "" c 'k'
handleCommandInput 2, buffer "" c 'k'
after handleCommandInput, buffer 0x104ca8d20"k" c 'k'
handleCommandInput 1, buffer "" c 'j'
handleCommandInput 2, buffer "" c 'j'
after handleCommandInput, buffer 0x104c5b480"j" c 'j'
handleCommandInput 1, buffer "" c 'h'
handleCommandInput 2, buffer "" c 'h'
after handleCommandInput, buffer 0x104ca89c0"h" c 'h'
handleCommandInput 1, buffer "" c 'g'
handleCommandInput 2, buffer "" c 'g'
after handleCommandInput, buffer 0x104cae780"g" c 'g'
handleCommandInput 1, buffer "" c '1'
after handleCommandInput, buffer "" c '1'
handleCommandInput 1, buffer "" c '2'
after handleCommandInput, buffer "" c '2'
handleCommandInput 1, buffer "" c '3'
after handleCommandInput, buffer "" c '3'
handleCommandInput 1, buffer "" c '1'
after handleCommandInput, buffer "" c '1'
handleCommandInput 1, buffer "" c '2'
after handleCommandInput, buffer "" c '2'
handleCommandInput 1, buffer "" c '2'
after handleCommandInput, buffer "" c '2'
handleCommandInput 1, buffer "" c '3'
after handleCommandInput, buffer "" c '3'
handleCommandInput 1, buffer "" c '\3'
handleCommandInput 2, buffer "" c '\3'
after handleCommandInput, buffer 0x104cae690"\3" c '\3'
handleCommandInput 1, buffer "" c '\3'
handleCommandInput 2, buffer "" c '\3'
after handleCommandInput, buffer 0x104adaed0"\3" c '\3'
handleCommandInput 1, buffer "" c '\3'
handleCommandInput 2, buffer "" c '\3'
after handleCommandInput, buffer 0x104ca8720"\3" c '\3'
handleCommandInput 1, buffer "" c '\4'
handleCommandInput 2, buffer "" c '\4'
after handleCommandInput, buffer 0x104bf8d80"\4" c '\4'
handleCommandInput 1, buffer "" c '\3'
handleCommandInput 2, buffer "" c '\3'
after handleCommandInput, buffer 0x104caaa80"\3" c '\3'
handleCommandInput 1, buffer "" c '\4'
handleCommandInput 2, buffer "" c '\4'
after handleCommandInput, buffer 0x104ca8e40"\4" c '\4'
```
This is super cool! Bravo. Awesome to see it written in Nim too.
When I do `cha example.com` I can't figure out how to use any of the commands (hjkl, etc). The only keys I've found that have any effect are typing numbers which show up in the bottom left. Haven't figured out how to do anything with those. Am I missing something obvious about how to use this or could this be a bug?
I built from source on MacOS Sequoia 15.5 Apple Silicon using Nim 2.24. Pages load correctly, I just can't get the commands to work. Thanks!
Not necessarily! Each Roc app runs on a particular platform which is built in a host language for a specific domain. That host language could be Rust, Zig, C, C++, Go, Swift, etc. It's possible the basic-webserver platform will be rewritten to Zig but it doesn't need to be.
Roc couldn't be optimized for writing the Roc compiler without sacrificing some of its own goals. For example, Roc is completely memory-safe, but the compiler needs to do memory-unsafe things. Introducing memory-unsafety into Roc would just make it worse. Roc has excellent performance, but it will never be as fast as a systems language that allows you to do manual memory management. This is by design and is what you want for the vast majority of applications.
There are a number of new imperative features that have been (or will be) added to the language that capture a lot of the convenience of imperative languages without losing functional guarantees. Richard gave a talk about it here: https://youtu.be/42TUAKhzlRI?feature=shared.
Safe Rust still basically always links against unsafe C libraries though. Fil-C will only link against libraries compiled with Fil-C which makes for a vastly stronger guarantee.
Also, plenty of code written in Rust is not safe so "if everything was built in safe rust, then it would be as safe" does not hold. There's definitely no way to write safe inline assembly in Rust.