siad VS QEMU

For example, decentralized data storage projects like Filecoin, Arweave, and Sia posted 50-100% user growth, providing blockchain-powered alternatives to AWS, Google Cloud, and Dropbox for distributed app data security.

Sia - A decentralized data storage platform where the proof of work helps maintain the network and provide storage services.

Our site: https://sia.tech/ Blockchain explorer: https://explore.sia.tech/ How to get Siacoins: https://sia.tech/community-ecosystem?software=exchanges#software The Sia Foundation team: https://sia.tech/about-sia-foundation The Sia Grants Program: https://forum.sia.tech/c/foundation/grants/8 Sia docs: https://docs.sia.tech

Sia

If I'm following correctly, I believe this is basically what Sia does, although not optimized to be used directly as a media server (or maybe it could?).

https://sia.tech/

Not sure what you aught to do, but I will say the 2 projects Im paying attention to are https://www.helium.com/mine and https://sia.tech/

For consumer storage, Sia, Storj, and Vult (on Züs) can be good options since they are architecturally lower cost because of the erasure code technology. But for enterprise storage, among the available platforms, there isn’t a direct competitor to AWS S3 except for Zus, and archive storage, Filecoin is the best alternative, and for consumer storage, Storj, Sia, and Züs offer better options for fast retrieval times.

As long as your needs are not beyond a TB, you can always consider something that does not require an actual "login" or a national currency, such as using SIAcoin (https://sia.tech). The cost for a terabyte hosted in two places often will cost you under the equivalent of $6-8 per month. It takes getting used to, but since it is blockchain based, it might even be possible for you to mine the means of paying for your cloud storage if what you actually need hosted is low enough.

SiaCoin which is the utility token for the Sia ecosystem https://sia.tech/

A better solution is just to write a plain ass shell script that tests if various C snippets compile.

https://github.com/oilshell/oil/blob/master/configure

https://github.com/oilshell/oil/blob/master/build/detect-pwe...

Not an unholy mix of m4, shell, and C, all in the same file.

---

These are the same style as a the configure scripts that Fabrice Bellard wrote for tcc and QEMU.

They are plain ass shell scripts, because he actually understands the code he writes.

https://github.com/qemu/qemu/blob/master/configure

https://github.com/TinyCC/tinycc/blob/mob/configure

OCaml’s configure script is also “normal”.

You don’t have to copy and paste thousands of lines of GNU stuff that you don’t understand.

(copy of lobste.rs comment)

Related:

A fast Pascal (Delphi) WebAssembly interpreter:

https://github.com/marat1961/wasm

WASM-4:

https://github.com/aduros/wasm4

Curated list of awesome things regarding WebAssembly (wasm) ecosystem:

https://github.com/mbasso/awesome-wasm

Also, it would be nice if there was a WASM (soft) CPU for QEMU, which (if it existed!) would go here:

https://github.com/qemu/qemu/tree/master/target

> architectural registers are always updated

In tiny code, the guest registers (global TCG variables) are stored in the host's registers until you either call an helper which can access the CPU state or you return (`git grep la_global_sync`). This is the reason why QEMU is not so terribly slow.

But after a check, this also happens when you access the guest memory address space! https://github.com/qemu/qemu/blob/master/include/tcg/tcg-opc... (TCG_OPF_SIDE_EFFECTS is what matters)

But still, in the end, it's the same problem. What QEMU does, can be done in LLVM too. You could probably be more efficient in LLVM by using the exception handling mechanism (invoke and friends) to only serialize back to memory when there's an actual exception, at the cost of higher register pressure. More or less what we do here: https://rev.ng/downloads/bar-2019-paper.pdf

Um, in case you don't know, UTM (based on QEMU) is out for quite a while.

Some of these tools include Oracle VM VirtualBox (that I've used since before the acquisition of Sun Microsystems by Oracle), VMWare Workstation Player, and QEMU, but last year, I found out about Multipass.

For C/C++ projects that use meson as the build system, there is an excellent way to manage dependencies:

https://mesonbuild.com/Wrapdb-projects.html

https://mesonbuild.com/Wrap-dependency-system-manual.html

meson will download and build the libraries automatically and give you a variable which you pass as a regular dependency into the built target:

https://github.com/qemu/qemu/tree/005ad32358f12fe9313a4a0191...

https://github.com/harfbuzz/harfbuzz/tree/main/subprojects

https://github.com/harfbuzz/harfbuzz/blob/37457412b3212463c5...

Or, if you're using proper operating systems, they're managed by the usual package manager, just like everything else.

For all the users of the Linux platform, QEMU is the VM that you should go for. This software comes without any price tag and works as an emulator of various machines with utmost ease and completion; the software uses dynamic translations to emulate hardware peripherals and enhances its overall performance. If you are using QEMU as a virtualizer, then it will function exactly like the host system (provided you have the right set of hardware).

In this tutorial, we set up macOS and Windows virtual machines on UTM, a macOS application that provides a GUI wrapper for QEMU, a powerful open-source emulator and virtualizer. UTM allows you to easily manage and run virtual machines without memorizing complex commands. It also has special handling for macOS, making it simpler to install compared to other virtual machine software.

I think you will need to build it yourself which you can do so by: Checkout the qemu repo and its submodules using the steps here: https://en.wikibooks.org/wiki/QEMU/Installing_QEMU in 'Building from Source' except for step 1 use the 'git clone https://github.com/qemu/qemu.git' Step 9 is where you enable the features, the build system does this by checking if you have the dev and or lib packages for the feature installed i.e. spice development packages will enable spice functionality, use the output from configure to help you with this then continue to step 10