studio VS QEMU

> Especially a tool like RViz is always missing. And in many many robotics video I see (of a moderately complex robot), there's ROS's RViz on some screen.

I would love the future robotics development stack to be more modular, so that (for example) future middleware solutions don't need to also bundle their own visualization software. This was direct inspiration for creating Foxglove Studio[0] for visualization and MCAP[1] for logging - both work great with ROS, or equally well without it.

[0] https://github.com/foxglove/studio

[1] https://github.com/foxglove/mcap

That's the true strength of combining existing open source solutions. Thanks for the great support of Foxglove Inc. over the past few years.

Foxglove | Remote (US time zones) | Full Time or Contract | https://foxglove.dev/

Foxglove is the leading observability platform for robotics developers. We help robotics and AV companies log, ingest, organize, and visualize multimodal data. Join our small, highly experienced, and fast moving team. Prior experience working in robotics or AV is a bonus but not necessary.

* Senior Frontend Engineer (TypeScript, React, bonus if you have WebGL experience)

* Senior Full Stack Engineer (TypeScript, Go)

* Senior SRE/Infrastructure/DevOps Engineer (GCP, AWS, Azure, Terraform, K8s)

https://foxglove.dev/careers

Email in profile if you have questions.

It's a common misconception that you need a ML or robotics PhD to work in the field. There are plenty of frontend & backend web engineering, data engineering, and infrastructure/devops roles available at robotics companies - you don't need to be a domain expert.

For example, at Foxglove[0] we are building open source web-based visualization and data management for robotics (shameless plug: currently hiring).

[0] https://foxglove.dev/

You can use the rosbag commandline-tool to figure out all of this: http://wiki.ros.org/rosbag/Commandline rosbag info for example can give you some of the type/number of messages information. For more complex stuff, you could use https://foxglove.dev/ to visualize and inspect rosbags

Web-based data visualization for robotics and self-driving. Robotics is such an interesting industry, and we're only scratching the surface of what new tools are needed.

Try it live here (hit "view sample data"): https://studio.foxglove.dev/

And it's open source! https://github.com/foxglove/studio

Shameless plug - we're hiring: https://foxglove.dev/careers

When our team at Foxglove announced MCAP, we wanted to empower teams to spend less time building commodity tools and more time tackling their hardest robotics challenges.

Foxglove | Remote (Americas/Oceania) | Full Time or Contract | https://foxglove.dev/

Dev tools for robotics and autonomous vehicles.

Robotics will have a massive positive impact on the world economy and global human productivity over the coming decade. At Foxglove, we're building powerful web-based open source & commercial tools to accelerate this trend.

We're a small, highly experienced, and fast moving team. We're looking to hire several more people (most roles don't require previous robotics experience, unless specified below):

- Senior Frontend Engineer (react, typescript, some webgl+wasm)

- Senior Full Stack Engineer (typescript, some golang)

- First Product Manager (robotics/AV experience required)

- First Account Executive (infrastructure SaaS experience required)

https://foxglove.dev/

https://foxglove.dev/careers

React + Typescript. Forgot to mention it’s open source so you can see for yourself:

https://github.com/foxglove/studio

My most-wanted QEMU feature: https://github.com/qemu/qemu/commit/a2260983c6553

Using `gic-version=3` on macOS you can now use more than 8 cores on ARM chips.

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.