Live data from Hacker News

Nvidia NemoClaw

github.com

41–50 of 291 posts

Re: Nvidia NemoClaw

#41
post #32

Earlier quoted context omitted.

Like with any new tool/technology, you have to try it. And even then the benefits won't be obvious to you until you've played with it for a few days/weeks. With LLMs in general, it took me months before I found real good use cases. Simple example: I tell (with my voice) my OpenClaw instance to monitor a given web site daily and ping me whenever a key piece of information shows up there. The real problem is that it is…

> Simple example: I tell (with my voice) my OpenClaw instance to monitor a given web site daily and ping me whenever a key piece of information shows up there. Maybe i'm just old -- a cron job can fetch the info and push it to some notification service too, without also being a chaos agent. It seems I spend the security cost here, and in return i can save 15 minutes writing a script. Juice doesn't seem to be worth th…

But they don't just want the text of the website pushed as a notification every day. They want the bot to load the site, likely perform some kind of interaction, decide if the thing they're looking for is there, and then notify them.

Re: Nvidia NemoClaw

#43

It’s impressive someone early in their career shipped this. There seems to be a stark increase in high-quality AI/data projects from early-career engineers lately and I'm super curious what’s driving that (and honestly speaking: a little jealous).

Should be obvious that its tools like Claude Code. If you are a junior dev not experienced in delivering entire products but with good ideas you have incredible leverage now...

Re: Nvidia NemoClaw

#44

Earlier quoted context omitted.

Running OpenClaw is the nerd equivalent of rolling coal

OpenClaw can be useful, in theory, unlike rolling coal. OpenClaw is what people always hoped Siri, Alexa and/or Google Assistant would be, and now it's really here. It may be expensive, has a chance to become your local Skynet and might randomly delete or leak everything that's valuable for you..but I guess this counts as growing pains.

Rolling coal can be useful in theory, for pissing people off. As intended.

Re: Nvidia NemoClaw

#45
post #7

what about just using an unprivileged container and mounting a host folder to run open claw?

OpenClaw is so bad with Docker. I spent hours on it and hit road block after road block trying to get the most basic things working. The last one was inability to install dependencies on the docker container to enable plugins. The existing scripts and instructions don’t work (at least I couldn’t get them to work. Maybe a me problem). So I gave up and moved on. What was supposed to be a helpful assistant became a nigh…

Absolutely this. I finally got it working, but the instructions and scripts for setting it up with Docker absolutely do not work.

Re: Nvidia NemoClaw

#46
post #7

what about just using an unprivileged container and mounting a host folder to run open claw?

OpenClaw is so bad with Docker. I spent hours on it and hit road block after road block trying to get the most basic things working. The last one was inability to install dependencies on the docker container to enable plugins. The existing scripts and instructions don’t work (at least I couldn’t get them to work. Maybe a me problem). So I gave up and moved on. What was supposed to be a helpful assistant became a nigh…

I’m not an engineer and now I realise why I’ve been struggling getting OpenClaw setup in docker. I just can’t get it to work. Makes sense that it needs access to the underlying OS

Re: Nvidia NemoClaw

#47
post #8

Earlier quoted context omitted.

I'm trying to put together what you could possibly mean by this -- rolling coal is fundamentally about spite. In isolation, nobody _wants_ their vehicle to spew black smoke. It only comes close to making sense in the context of another population (EV owners, typically, or more generally "the libs"). OpenClaw lets people live a bit dangerously, but fundamentally gives them something that they actually wanted. They wan…

> OpenClaw lets people live a bit dangerously, but fundamentally gives them something that they actually wanted. They wanted it so badly that they're willing to take what seem like insane risks to get it. For the first time in my career I feel so incredibly behind on this: What is open claw giving people that they want so badly? It just seems like Russian Roulette, I honestly don't see the upside

OpenClaw has a persistent memory, stored to disk, and an efficient way of accessing it. ChatGPT and Claude both added a rudimentary "memory" feature in March but it's nowhwere as extensible or vendor neutral.

Re: Nvidia NemoClaw

#48

Earlier quoted context omitted.

> OpenClaw lets people live a bit dangerously, but fundamentally gives them something that they actually wanted. They wanted it so badly that they're willing to take what seem like insane risks to get it. For the first time in my career I feel so incredibly behind on this: What is open claw giving people that they want so badly? It just seems like Russian Roulette, I honestly don't see the upside

I can give you, as an example, what is driving me towards trying it. I work as a contractor for 2 companies, not out of necessity, but greed. I also have a personal project with a friend that is dangerously close to becoming a business that needs attention. I also have other responsibilities and believe it or not - friends. Also the ADHD on top of that. I yearn for a personal assistant. Something or somebody that wil…

How much would a real personal assistant cost?

Re: Nvidia NemoClaw

#49
post #23

Earlier quoted context omitted.

A lot of senior engineering problems aren't gated by experience but by being trusted to coordinate large numbers of juniors. Now that as a junior, I can spin up a team of AIs and delegate, I can tackle a bunch of senior level tasks if I'm good at coordination.

I think this is a fundamentally flawed perspective on the role and experience of a senior. It's a managers role to coordinate junior engineers. The difference between junior and senior is knowing where and when to do what at an increasing scale as you gain experience.

> It's a managers role to coordinate junior engineers.

Due to AI this is now my job. My company is hiring less juniors, but the ones we do hire are given more scope and coordination responsibilities since otherwise we'd just be LLM wrappers.

> The difference between junior and senior is knowing where and when to do what at an increasing scale as you gain experience.

Many juniors believe they know what to do. And want to immediately take on yuge projects.

e.g. I decided I want to rewrite my whole codebase in C++20 modules for compile time.

Prior to AI, I wouldn't be given help for this refactor so it wouldn't happen.

Now I just delegate to AI and convert my codebase to modules in just a few days!

At that point I discovered Clang 18 wasn't really optimized for modules and they actually increased build time. If I had more experience I could've predicted using half-baked C++ features is a bad idea.

That being said, every once in a while one of my stupid ideas actually pays off.

e.g. I made a parallel AI agent code review workflow a few months ago back when everyone was doing single agent reviews. The seniors thought it was a dumb idea to reinvent the wheel when we had AI code review already, but it only took a day or two to make the prototype.

Turns out reinventing the wheel was extremely effective for our team. It reduced mean time-to-merge by 20%!

This was because we had too many rules (several hundred, due to cooperative multitasking) for traditional AI code reviewers. Parallel agents prevented the rules from overwhelming the context.

But at the time, I just thought parallel agents were cool because I read the Gas Town blog and wasn't thinking about "do we have any unique circumstances that require us to build something internally?"

Re: Nvidia NemoClaw

#50

It’s impressive someone early in their career shipped this. There seems to be a stark increase in high-quality AI/data projects from early-career engineers lately and I'm super curious what’s driving that (and honestly speaking: a little jealous).

There are four "people" that contributes ( https://github.com/NVIDIA/NemoClaw/graphs/contributors ) judging by the git commits and the GitHub authors, none of them seem to be novices at programming, what made you write what you wrote here?

I think he's talking about the original claw, Open Claw
Post reply on HN