Earlier quoted context omitted.
Quoted post unavailable.
Methinks someone lacks the courage of their convictions.
No post body was provided.
Serving a high-performance blog solely from memory, using Rust
111–120 of 143 posts
Re: Serving a high-performance blog solely from memory, using Rust
#112The tech is cool, but some of the language is so cringy. For example, the statement "websites are social constructs" makes zero sense. You could say that websites are material objects of a symbolic network of computer languages, like physical paper money is a material, fetishized object of the social construct of money. Websites themselves are not constructed socially. Maybe the author means how websites are perceive…
A website is a social construct because it can only function by the agreement of everyone involved (i.e., we all agree on how to parse HTML). The individual site may be constructed individually ( maybe ) but it can only work if the society of people-who-use-the-internet all agree to follow a series of conventions about how websites work; you can't start using \ instead of \ and expect everything to work as normal, be…
Hey mate, you need to try a web browser. I found my experience using the Internet greatly improved when I stopped trying to parse the html documents myself.
Re: Serving a high-performance blog solely from memory, using Rust
#113The tech is cool, but some of the language is so cringy. For example, the statement "websites are social constructs" makes zero sense. You could say that websites are material objects of a symbolic network of computer languages, like physical paper money is a material, fetishized object of the social construct of money. Websites themselves are not constructed socially. Maybe the author means how websites are perceive…
Talking about cringe, the furry stuff does in my opinion also negatively impact impression of the article. Also I distinctly remembered extremely similar blog written by someone with different name, but apparently author changed it yet again.
Re: Serving a high-performance blog solely from memory, using Rust
#114I want to see this taken to the logical extreme. A real OS with actual drivers (no unikernel, no virtio) for a small set of hardware that only serves static pages. No need for virtual memory. Just hardcode the blog posts right into the OS and use the most minimal TCP stack you can make.
It already exists in the embedded device word
I remember working in 2008 on a project for some geothermal devices that were spitting some IoT data on a "hardcoded" html page directly in the C code of the program, the device was using a chinese 8051-like CPU so you had no OS-per se
Re: Serving a high-performance blog solely from memory, using Rust
#115cppcms was (is?) using something similar , you write in a template language, and it get compiled into c++ code
http://cppcms.com/wikipp/en/page/main
https://github.com/Tatoeba/tatowiki the wiki of tatoeba.org ( https://en.wiki.tatoeba.org/articles/show/main# ) is written in it
Re: Serving a high-performance blog solely from memory, using Rust
#116I want to see this taken to the logical extreme. A real OS with actual drivers (no unikernel, no virtio) for a small set of hardware that only serves static pages. No need for virtual memory. Just hardcode the blog posts right into the OS and use the most minimal TCP stack you can make.
Why stop there? Bake your blog to hardware.
Re: Serving a high-performance blog solely from memory, using Rust
#117Can you use more rust to serve the 7 readers of a blog? You know what: use caching or something that compiles to plain html (hugo, jekyll etc.). No need for hardcore memory optimization.
Re: Serving a high-performance blog solely from memory, using Rust
#118Is this the same author that made the talk about PAM recently? I really like his articles.
Re: Serving a high-performance blog solely from memory, using Rust
#119You don't need Rust for this -- you can do the same in Go, Node, etc. In 2012 my cheap VPS had a crappy HDD share but fairly acceptable memory, so I rendered the Markdown files and stored them in a little structure, returning them directly from memory. Everyone thought it was amazing even though it was just a dumb http server returning pages[req.path] :-) Latency was under 10ms which was pretty amazing for a 2012 KVM…
I don't think OP was implying that Rust was a requirement, just what was actually used in this case. And, indeed, OP gives some reasons that Rust might be preferable: > And when I say fast, I mean that I have tried so hard to find some static file server that could beat what my site does. I tried really hard. I compared my site to Nginx, openresty, tengine, Apache, Go's standard library, Warp in Rust, Axum in Rust, a…
Rust is preferable in this case since there is no manager shoving more requirements on the project every week.
In the real world, use Go, Node, etc.
Re: Serving a high-performance blog solely from memory, using Rust
#120Earlier quoted context omitted.
Fiber optics are also about 2/3rds the speed of light. One of the interesting things about Starlink is that when they have laser links between satellites they should be able to beat terrestrial latencies over very long distances like California to London.
would a satellite to satellite laser in low earth orbit be faster than a radio link between the same satellites?
only bandwidth wise. latency would be the same assuming that the transmitters and receivers in both cases can process the signal just as fast.