It does not appear to be working for me right now, I get "error loading exercises".

What are your thoughts about the wger project [0]? It is a FLOSS AGPL-licensed self-hosted fitness/workout/nutrition manager that has existed for almost a decade (I think?) It's a django app and has a companion flutter app that runs on android/ios/windows/linux/macos. It supports multiple users and could even be used to run a gym. Body.build [1] is a newer FLOSS project (also browser-based) that is focused around building a weight lifting program. The author of body.build also contributes to wger.

I'm using wger in my homelab and while there are a lot of moving pieces to the self-host process, it works well. I'd say the biggest limitation is the comprehensiveness of their exercise database, but that is something that many people have recognized and are steadily expanding. If anyone is willing to contribute exercises (and exercise media) to this AGPL licensed project, they would definitely appreciate it!

[0]: https://github.com/wger-project

[1]: https://github.com/Dieterbe/body.build

Please, I don't want to come on to HN to see politics injected into everything. Stay on reddit for that.

I logged in to make a comment regarding something within my area of expertise: the technology present in the parent link and how this technology has been accessible to hobbyists for over 10 years.

> Not to make everything political... [proceeds to make a political statement]

For what it's worth, this type of Lidar scanner was possible to make well over a decade ago with ROS1, a Phidgets IMU, a webcam, and a lidar pulled out of a Neato vacuum (the cheapest option at the time). This would be around the difficulty of a course project for an undergraduate robotics class and could be done with less than 200 USD of salvaged parts (not including the computer). Hugin was also around over a decade ago.

It's still a nice little project!

Thank you for the excellent reply! I think I understand now... Once a business starts transacting in things other than a single type of money (say durable goods, consumables, services, or say other types of money) it becomes necessary to reconcile these non-money-denominated accounts. And for that, you need more than a single database, or single spreadsheet. You need a suite of persons or softwares that can __account__ for these stocks and flows, and the rules that come along with them.

And that is called ERP, of which "simple" money accounting is but one component of.

So root commenter's objection was more along the lines of: "those are some bold claims for mere money-accounting program. if you used a _real_ accounting program (as in an ERP) then you'd understand how complex peoples' needs can be". And the tone they phrased it elicited the downmods :)

I guess I understand. I still admire the OP and the frustration that fueled their desire to create a tool that works for them. And the tone of the readme is very endearing, it reminds me of the things my IRC friends would say to kick-off a lively discussion...

And so it has!

Please elaborate more, my friend! Let's say that I was^W am a programmer who is seduced by the plain-text accounting / one-database-is-all-you-need notion and I think my needs will be simple, as I can keep the business of my bodega all in the RAM of my brain... Or at least I think I can.

How can this go wrong? What are some of the needs that compel the bodega owner to move on to more sophisticated tools? Is it because of calculating things like taxes and hourly rates and the like?