Comments URL: https://news.ycombinator.com/item?id=49512511

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=49397537

Points: 1

# Comments: 0

Peppy: https://peppy.bot

Quickstart (about 5 minutes): https://docs.peppy.bot/quickstart/

OpenArm: https://openarm.dev

My team and I have been working hard on this project: https://peppy.bot

It's a direct replacement for ROS 2. We already have the OpenArm robot (https://openarm.dev) working on the platform, both v1.0 and v2.0, plus Isaac Sim and MuJoCo integration.

If you're in a hurry, head over to https://docs.peppy.bot/quickstart/ and get started in 5min.

Our long term vision is to allow anyone (even non-devs) to go from a prompt to real humanoid robot actions, first in simulation, then on the physical robot.

Happy to answer any question.

Comments URL: https://news.ycombinator.com/item?id=49058956

Points: 22

# Comments: 7

https://peppy.bot/

Coding as someone without experience in coding? Most probably yes, but from someone with some kind of expertise who can act as a guardrail for bad code piling up? Probably not.

Over the past six months, there hasn’t been a single day where I’ve checked the HN Best RSS feed without seeing a post about how AI “writes bad code,” “introduces bugs,” “creates technical debt,” or something along those lines.

I’ll probably make a lot of enemies by saying this, but do people realize that code is just a means to an end?

Users don’t care whether the code was written by AI or by hand, or which framework you used. They care that the product works.

I say this as someone who has spent more than 20 years honing their craft as a software engineer.

Let’s face it: by the time I manually ship version 1.0 of a product, the AI-assisted version could have been deployed 10x faster. By then, enough real-world feedback would have surfaced to identify the major issues, and tools like Claude Code would make it possible to fix and ship version 2.0 at an incredible pace.

At some point, execution speed starts to matter more than the elegance of the code.

Comments URL: https://news.ycombinator.com/item?id=48420827

Points: 463

# Comments: 765

The goal is to enable devs from all fields (embedded devs/AI engineers/vibe coders) to work on their own stack without ever having to worry about the other parts of the robot stack.

> I notice you don't have shared memory transport, nor do you support runtime composability (I think?)

We're using Zenoh in the backend, we didn't try to reinvent the wheel on that front.

> I'm also a little confused on what serialization format you support - is it an entirely custom one?

It's cap'n proto, but abstracted away for the user so he doesn't have to think about it.

> BSL feels great, but I found it scared off some people

Agreed, but we're building a SaaS in parallel, PeppyOS will be 100% free and open source but we don't want another company to build a SaaS on top of it, that will be the only restriction of the BSL license, otherwise it's the same as Apache 2.0.

This is just example cases but in fact it can go as high as you want as long as your hardware allows it

At the moment it's pretty raw, but we'll eventually turn it into a "no fuss entry into robotics".