It would actually be pretty easy to do with regular robotics (well, compared to a humanoid robot anyways). The reason nobody does it is that it takes up a ton of space which is at a huge premium in pretty much every kitchen ever.
Also like, loading and unloading the dishwasher is not that hard or time consuming.
> Also like, loading and unloading the dishwasher is not that hard or time consuming.
For a me a robot to do the dishwasher would be the number 1 reason for me to buy one.
My dishwasher is basically going at least twice sometimes three times a day (household with small kids). If I "miss" a slot to get everything washed before the next meal time then two things happen:
- the unwashed things begin to build up so there are too many things to fit in the next round and its hard to catch up.
- the things to need to use for meal-Y were still dirty from meal-X so you cant use foo etc.
Its "not much effort" true - perhaps 10-15 mins to unload then reload, but you need to do it 3 or 4 or more times a day AND you need to be there to do it on time so that there is time for it to finish it's load before meal-X etc.
If you are exhausted and its already 11pm and you've got to do your 3rd go at the dishwasher for the day so dirty things from dinner are getting washed and things are put away and ready for breakfast in the morning etc its really annoying. Its the last thing you want to do before going to bed. Or its morning and you're trying to get everyone out the door to school/work and the like, and you need to get the dishes going so that they're clean and ready to unload at lunch time (so that you can get the dirty lunch dishes in at lunch time etc).... you can see how this builds up into quite a pain in the ass hamster wheel.
I would 110% buy a humanoid robot for the cost of a decent second-hand car (so lets say about GBP10-15K) that was able to reliably do three or four 1 hour shifts per day doing basic house-keeper duties autonomously. So aforementioned dishes, cleaning down the dinner table, wiping down the kitchen worktops/countertops, picking up toys and cushions and shoes etc, then it can just go fold itself back into a cupboard in the kitchen to recharge for its next shift. Doesn't have to cook or play the violin or anything, basically just pick up crap off the floor and do the dishes every few hours so I don't have to. Bonus points if it can do it while I am working and/or it can do it silently at night
You have a house with small kids and you want a 600 pound autonomous robot walking around? These aren’t funny tech products, they’re industrial equipment.
Figure 03 is 134 pounds. 1x NEO (the only one really designed for household usage) is 66 pounds. Unitree R1 is 55 pounds. None of these are ready for real work yet but probably at some point in the future we will have practical humanoids.
All of these are more than enough weight to kill a toddler by falling on them. That, of course, ignores all the other hazards presented by (presumably) titanium limbs attached to actuators able to exert enough force to crush any extremity you care to name.
The first person who has their child injured by one of these things will have a hell of a lawsuit on their hands.
A human on average weighs anywhere from ~110 - ~250 pounds (very broad guess). A human can also fall on and injure a child. And you can be sure that, similar to how bones are covered by layers of tissue and skin, robots designated for household use will be built with materials that improve safety during physical interaction. There isn't much difference.
Also the customer will very likely be asked to sign damage waivers and whatnot as part of the sale/rental agreement.
Maybe not human form, but my house is designed for humans. It needs to be able to handle stairs. It needs to handle my doors and halls. It needs to reach upper shelves that are human height (my wife is short and constantly complains about things on a top shelf she cannot reach). I have corners in my house that a large dog can only manage because their spine bends. Human form in many ways is a constraint.
It is ideal insofar as the world has been created with humans in mind. And it’s easier to acquire training data for human shaped entities than for some hypothetical better shape.
The "port" terminology is misleading; this is real SQLite, compiled from C to Go using https://gitlab.com/cznic/ccgo/-/tree/master/v4 (by the same author; this library is its most widely used application). The use case is that a lot of Go codebases prefer to completely eschew FFI because a lot of the nice properties of Go's tooling and whatnot (cross-compilation is trivial, binaries are automatically static on Linux, etc.) only hold if the entire build is pure Go.
No. A mistake is unintentional. Go's rejection of a C runtime dependency is a deliberate trade off, and one that has served it well for its design goals.
Exactly. Even though your m5 max laptop will run the x86 binary just fine, if you don't compile it for arm, your m5 max laptop drops most of its speed and only has the same performance as an x86 server ...
If your codebase is pure golang it’s trivial to cross compile for different OSs (aside from binary signing on macOS). If you add some kind of C code you have to jump through a bunch of hoops to get a binary. Funny enough, I was looking for this exact project for that reason last week.
It's not just about overhead/performance. cgo-free means no need to set up a cross-compiler if targeting other devices. Just "go build" with the right GOARCH and GOOS will let you compile a binary that will run on most devices.
The following go flags let you build statically-linked cgo binaries, provided that all the C libraries that you're using support static linking and don't call the NSS functions in glibc:
Absolutely not. Maybe runtime overheads are minimal, but builds are so much harder to do. And yes, you need to figure it out maybe once, but it is still a lot more effort than just pulling in a new dependency. Now repeat that same effort for every new application, vs pulling that into every new application.
that’s really not true when the database is all in memory, statements are prepared, and so on.
but the overheads also stack up, the database/sql api is fairly allocation heavy too unless you do a lot of work and that friction increases quite a bit with the ffi boundary.
this is not to suggest “modernc is faster” - it’s not for a lot a workloads.
there are opportunities for optimization all over both approaches.
Which only supports my belief that with the proliferation of contraception tying sex and long-term partnership together is becoming a useless anachronism
Sparta was built on slavery, their obsession with war was necessary to keep their slaves in check and deal with constant uprisings, it was very practical for their way of life.
> came to Netherlands for a short visit and oh my god how much better the food is
I really don't want to know what the food is like where you came from, but it may be a WMD test or something. You should get human rights activists and lawyers working on it.
Run by Apple where? Do they really have enough hardware to run it in-house?
reply