1,704 karma · joined February 6, 2018
meet.hn/city/us-Conshohocken
Interests: Data Science, Art, AR/VR, AI/ML, Fintech, Gaming, Hacking, Hardware, Philosophy, Programming, Science, Space Tech, Web Development
---
1. Stairs. Roomba's can't vacuum stairs, so you still need to do those yourself.
2. Stairs, Roomba's can't traverse stairs, so you need one for each floor.
3. Doors. If you want the Roomba to vacuum the whole house, you have to have all the doors open for it.
4. Can't have anything on the floor, the Roomba will either get stuck or avoid it. But I shouldn't have to never leave a backpack on my floor if I want it vacuumed.
5. Corners. Roomba's can't vacuum in corners or in tight areas between furniture and walls. or any other weird geometry. ie: I have a wire shelf. Roomba doesn't fit under it but its easy to use a stick vacuum to get between the wires and to the floor.
And this is before we get to the limit on suction and capacity in that form factor.
var playerX_input = Input.GetHorizontal(); // float in range -1 to 1
var playerY_input = Input.GetVertical(); // float in range -1 to 1
var playerVelocity = new Vector2(playerX_input, playerY_input);
// The player can now move 1 unit/frame in X and 1 unit/frame in Y, which means that if they're moving diagonally, the length of their velocity vector is the length of the vector (1,1) which is sqrt(2) (~1.41)
// This can be corrected by doing something like
if(playerVelocity.length > 1)
{
playerVelocity = playerVelocity.normalized();
}https://www.thestar.com/news/insight/when-u-s-air-force-disc...
just some quick things that jumped out at me:
- of homes actually built, hides that there's a lot of demand for smaller starter homes or housing in cities
- the average household can get smaller if there's a bimodal distribution, ie poorer households growing in size. or people not having kids because they don't have and can't feasibly afford a spare bedroom.
- "the average individual living in a newly built home" im leaving this one as an exercise for the reader
afaik the patent was basically expiring in the next couple years anyway, even the small ancillary ones. They've been making and selling SawStop saws for the last 20 years and already made their bag. So, since SawStop has the experience designing and building the systems they want to wring out some good will and see which Big Saw manufacturer wants to pay them to get ahead of their competition.
When you use an LLM, you provide it context. Where do you usually get that context from? Some service, JIRA, whatever, in your browser.
You have to do it in real time, from a video feed, and make sure that you're tracking the same unique instance of that object between frames.
I read a comment here on HN recently, wish I could find it now (I think it was in one of the threads on the 'missing datatype (graphs)'). The gist was that we do large things pretty well: Operating Systems, standard libraries, etc and small things pretty well: single header file libs, specific open source projects, etc, but medium size things are missing. This seems to be the same kind of thing: you have enough complexity that coordination is hard(tm) but you don't have enough scale to build up an institutional inertia to overcome the bus-factor-of-one-ness that--- uhhh
What I'm trying to say is that the support system around that project, like if you have a medium sized project, its going to have individual experts for the parts that make it up, but they're all single points of failure.
If I had more time I would have written a shorter more coherent comment.
Why would you do age verification on login? It only needs to happen once on account creation.