Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
ROS Alternatives
Similar projects and alternatives to ROS
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Open and cheap DIY IP-KVM based on Raspberry Pi
Open and inexpensive DIY IP-KVM based on Raspberry Pi
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
wireguard-install
WireGuard road warrior installer for Ubuntu, Debian, AlmaLinux, Rocky Linux, CentOS and Fedora (by Nyr)
-
ImageAI
A python library built to empower developers to build applications and systems with self-contained Computer Vision capabilities
-
Robotics Library (RL)
The Robotics Library (RL) is a self-contained C++ library for rigid body kinematics and dynamics, motion planning, and control.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
ROS reviews and mentions
- Google DeepMind's Aloha Unleashed is pushing the boundaries of robot dexterity
-
Linux market share passes 4% for first time; macOS dominance declines
I wonder if this could be related to M1/2/3 Macs being worse for x86 system software development than the old Intel Macs. I work on ROS[1] which runs on x86 Linux platforms, but usually develop on a Mac. I may have to move to a Linux laptop soon because there's not an easy path (that I'm aware of) to running x86 ROS code on an M3: compiling the entire system for arm would be a huge headache while running x86 code in a Linux VM under Rosetta has a lot of unknowns.
Obviously my case is a bit of an outlier, but once you add up enough outliers you might see a real impact.
-
Getting into Robotics as a Software Engineer
Robotics is a broad field and is a confluence of many specialties: mechanical engineering, hardware engineering, software engineering, control, machine learning, computer vision, anything in between is a good entrance.
Coming from software, if you are interested, I would suggest either:
- Backend platform development (Python, C++ as main programming languages with a strong focus on ROS[1]).
- Frontend development (nothing too different from what's out there).
As small projects I would suggest playing with ROS to learn it and getting a running simulation with a simple robot that you can teleoperate, most of the stack already exists, it's just connecting everything together [2].
Another venue is open source contribution [1] to get known within the community and potentially attract interest from companies. ROS has multiple packages, from cloud infrastructure to drivers and simulation, if you see anything there you could contribute to, they will gladly take contributions.
In general robotics greatly benefits of good technologies from other areas, if there is a tool we use you believe could be better or a lack of good tooling in a specific area, it will get noticed.
So this would be my suggested path: learn C++/Python if you're not familiar with, learn ROS and watch which specialties appear more often in robot related jos posts [3]. If you are really invested, maybe go to a robotics conference as ROSCon to meet other enthusiasts, which companies are engaged with the community, etc.
Good luck!
Note: not everything robot related is done in ROS, but it's almost a standard within the field save for a few exceptions.
[1]: https://www.ros.org/
-
How do I start robotics as a teen with no money?
ROS is an operating system designed for robotics (it can be run many different ways) it includes simulations for many robots (including sensors etc) and you can even design your own fully inside the software. https://www.ros.org/
-
C++ Project Ideas?
Robotics with ROS https://www.ros.org/ (You can do a lot with simulators and don't require actual HW)
-
[Career Advice] Transition from Software Engineer to Robotics
Hardware experience is useful, but not needed to get started working with robotics. With your software background, I recommend you look into learning ROS (Robot Operating System) fundamentals on a personal computer, you can simulate a robot using Gazebo. Good luck!
-
Best practices in creating a Rust API for a C++ library? Seeking advice from those who've done it before.
In Robotics, the Open Motion Planning Library (OMPL) is a popular library for multi-dimensional motion planning, and is used by ROS and other robotics-related software. There are no Rust bindings to OMPL (though there is Rust support for software like ROS), and the library is written almost exclusively in C++. There are Python bindings, but those are generated using Py++. The header files throughout OMPL are C++ header files, not C, as they contain namespaces, classes, etc.
-
[ANN] NASA's Ogma 1.0.9
[3] https://www.ros.org/
-
Newbie to Robotics (Question/Discussion)
ALSO - learn ROS. If you are interested in robotics as a career, this is one of the better things to have good experience for on your resume. There are also good tutorials on using ROS with simulated robots, so if you just want to focus on the software that's a good option :)
-
Real-time C++ on Linux
Roboticist here, have you heard of ROS?
-
A note from our sponsor - InfluxDB
www.influxdata.com | 19 Apr 2024
Stats
ros/ros is an open source project licensed under BSD 3-clause "New" or "Revised" License which is an OSI approved license.
The primary programming language of ROS is Python.