aper VS studio

The relevance here is that this post mentions their new Rust library Aper (https://aper.dev/). In addition, CRDTs are a favorite topic of Raph Levien, AKA the Rust GUI guy, and featured in the Xi editor, his first major Rust project (retrospective here: https://raphlinus.github.io/xi/2020/06/27/xi-retrospective.html).

It's also super refreshing to see the work on Aper [1] [2] (a Rust library implementing state machine synchronization across a trusted network). Looking forward next series of articles here!

[1]: https://aper.dev/

[2]: https://github.com/drifting-in-space/aper

Our Aper (https://aper.dev) implements a number of similar concepts (state machine replication with optimistic local transitions + rollback). I 100% agree that it’s an easier model to reason about.

Your approach with cursors is clever, that part I haven’t seen elsewhere.

Drifting in Space | Full-time | NYC | https://driftingin.space

We make Jamsocket (https://jamsocket.com/), which allows application developers to spin up and connect to server-side compute. This allows browser-based applications to do computationally-intensive things that are otherwise impossible in the browser.

We went through YC and just raised a seed round and are looking to build up our team. We are based in NYC but are open to remote for experience candidates.

Our tech stack includes Rust, NATS, Docker, Postgres, TypeScript.

We have lots of fun technical problems that get into the nitty-gritty of networking and operating systems, plus fun open-source stuff like Aper (https://aper.dev/). We are excited to build a diverse team and encourage non-traditional candidates to apply.

Email [email protected] or see more details here: https://www.ycombinator.com/companies/drifting-in-space/jobs...

> 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