schmichael

People with motor disabilities seems like a great use case! Cooking and watching TV are two activities that benefit from voice control (due to dirty hands and remotes going missing). Nursing mothers often literally have their hands full.

Lots of folks in safety critical situations rely on multitasking and voice commands: law enforcement, firefighters, pilots, heavy equipment operators, armed forces, etc. Many of them are in situations in which not multitasking isn't an option and receive special training to minimize risks. That being said now you're entering heavily regulated industries where the stakes couldn't be higher... not exactly an easy place for LLMs and startups to play.

On the other end of the spectrum there is a tried and true industry for tech innovations where the stakes couldn't be lower: adult entertainment. There's millions of adults wishing they could operate screens without needing a hand free. Might not be as glamorous as helping firefighters and people with motor disabilities, but we all need to make a living.

Best wishes!

Please stop multitasking while driving.

The tech seems neat and all but please stop multitasking while driving, encouraging others to multitask while driving, and building products specifically designed to encourage multitasking while driving.

If you want to work while you're in transit: take public transit.

> So there’s really nothing meaningful here.

If it’s not meaningful it should be trivial to beat right? ;)

This seems like a super fun game to find the upper bound on IPv4 addresses someone can open a socket from!

Hey Mitchell! Leave it to me to bait the comments. :)

Thanks for validating my assumption that once you introduce a big blob o' C all bets are off and you're back to Valgrind (or similar tooling).

> One argument is that the richer, more proven ecosystem of wrapper libraries may have prevented it

Yeah but where's the fun in that? ;)

Indeed, but I'm curious about the second class of memory correctness issue he mentions:

> 2. All other memory issues revolved around C API boundaries.

Is this something Rust, or any other language, has the ability to prevent any more than any other language? Or once you introduce a C API boundary is it back to tools like Valgrind?

I'm curious if Rust would have prevented the memory correctness errors assuming it replaced Zig in this scenario. It sounds like the vast majority were due to Zig/C interactions which makes me believe Rust would have had the same issues, but as a Go developer I am only guessing. I'm curious if there is a language that provides more tools to ensure correctness even when you're interacting with a huge amount of C.

Oregon at least makes it 50% IIRC. Anything less than 100% seems useless though. Usually when taking a new job in the same industry you expect a pay bump, so even a 100% rate is likely leaving money on the table.

Pushing a malicious app update creates an inspectable artifact. Researchers can discover exactly when it happened and therefore who is vulnerable and which messages.

This is a much much much better situation than handing someone your keys and letting them MITM you at any time with no hope of knowing.

> Writing forces you

I agree entirely with you except for the word "forces." Writing can cause synthesis. It should. It should be graded to encourage that...

...but all of that is a whole lot of work for everyone involved: student and teacher alike.

And that kind of synthesis is in no way unique to essays! All of the other mediums I mention can make synthesis more readily apparent then paragraphs of (often very low quality) prose. A clever meme lampooning the "mere merchant" status of the Medici family could demonstrate a level of understanding that would take paragraphs of prose to convey.

> I really don’t think there’s a coherent pro-genAI case to be made in the education context.

I think it’s simple: the reign of the essay is over. Educators must find a new way to judge a student’s understanding.

Presentations, artwork, in class writing, media, discussions and debates, skits, even good old fashioned quizzes all still work fine for getting students to demonstrate understanding.

As the son of two teachers I remember my parents spending hours in the evenings grading essays. While writing is a critical skill, and essays contain a good bit of information, I’m not sure education wasn’t overindexing on them already. They’re easy to assign and grade, but there’s so much toil on both ends unrelated to the core subject matter.

My unprofessional nutritional advice is: do what works for you! So if that’s calorie counting: great! No need to give it a second thought.

But if you are interested in critiques, a fair summary might be: calorie counting is at best extremely imprecise, both on how we measure the calories in food and how we estimate energy expenditure by activities. A little googling should lead to numerous discussions. I really enjoy the podcast maintenance phase, and even if you don’t want to listen to the episode they helpfully include tons of links: https://maintenancephase.buzzsprout.com/1411126/episodes/106...

Same! Mark Rober is what changed my mind about YouTube for kids. He's a wildly popular creator that's even shilling a product and yet... I'm ok with all of it? He seems to very legitimately care about sharing getting kids excited about STEM, and if he gets rich doing it: great! The product is less offensive than the sugary cereal I watched commercials for while watching Saturday morning cartoons as a kid. Definitely one of the few YouTube channels I let my kids watch unattended.

[Citation needed]

The concert/bar example allows stalking without knowing someone’s name.

That’s perfect for finding out where someone lives. Drop it in their bag or jacket at a concert/bar/work/whatever-in-the-evening, and the place they’re likely at in 4 hours is their home.

Not trying to be creepy, I’m just trying to demonstrate how we all need to think like adversaries (eg creeps) when designing products.

A great point! All of the libraries I mentioned are created and maintained by corporations. Hobbyists, as always, are free to do as they please without judgement from me. :)

I will say I get great satisfaction from the little envparse library I wrote needing near-0 maintenance. It’s a rare treat to be able to consider any project truly done.

We need a term like “Mature” or similar for dependencies that are done. Mature dependencies have two characteristics:

1. Well defined scope

2. Infrequent changes

Nomad has many of these (msgpack, envparse, cli, etc). These dependencies go years without changing so the dependency management burden rapidly approaches zero. This is an especially useful property for “leaf” dependencies with no dependencies of their own.

I wish libraries could advertise their intent to be Mature. I’d choose a Mature protobuf library over one that constantly tweaked its ergonomics and performance. Continual iterative improvement is often a boon, but sometimes it’s not worth the cost.

> You're not supposed to trust the tool

This is just an incredible statement. I can't think of another development tool we'd say this about. I'm not saying you're wrong, or that it's wrong to have tools we can't just, just... wow... what a sea change.

I need glasses to see and still find sight invigorating.

I love cycling. Even without electric assist I find using mechanical advantage invigorating.

No one is forcing an exoskeleton or ebike on you. Why can’t you be happy for the people whose mobility it improves? What have you lost by their gain?

I don't think you have to be paraplegic to have a condition that prevents you from enjoying an invigorating hike. If this gets more people who aren't in perfect health out and exercising, what an incredible win.

Lots of HN are not US Citizens who frequently visit the US for work, school, and/or vacation.

Thanks for supporting us!

Thanks! I think this is a really insightful comment because Nomad is more opinionated than I think we let on. The subtle interactions between signals, service discovery, health checks, templates, etc. all have a big impact on the reliability of the system as a whole. I've always wanted to do a "HashiCorp Validated Nomad App Design" kind of doc to outline these best practices, but it's always proved too big of a lift. Maybe now is the time!

> I am sad to see you go.

I'm not going anywhere! My grammar isn't always the best, so I apologize for the confusion.

<3

> Nomad allowed us to build out a large fleet of servers with a small team

I really love these stories. Our customers constantly shock me with how large of clusters they're able to manage with just a few people. >10k nodes by <10 people isn't uncommon although we are not good at rigorously collecting data on this.

Nomad is far from perfect, but we really strive to ease the pains of managing your compute substrate.

Thanks! We have kept an explicit community rotation and issue triage policy for Nomad's entire life. Definitely one of my hard lines.

I know we aren't perfect. In fact it's my turn this week, and I've utterly failed at keeping up with triage!!

We get tremendous joy and value from engaging with our community. Thanks for your patience (with me in particular!)

Glad to hear Nomad is working well for you! It always means a lot. We as the dev team spend all day staring at bugs and missing features, so it's nice to be reminded of what's working well! No one files an issue for a happy cluster. :)

I joined HashiCorp in 2016 to work on Nomad and have been on the product ever since. Definitely a lot of feelings today. When I joined HashiCorp was maybe 50 people. Armon Dadgar personally onboarded us one at a time, and showed me how to use the coffee maker (remember to wash your own dishes!). There have been a lot of ups (IPO) and downs (BUSL), but the Nomad team and users have been the best I've ever gotten to work with.

I've only ever worked at startups before, but HashiCorp itself left that category when it IPO'd. Each phase is definitely different, but then again I don't want go back to roadmapping on a ridiculously small whiteboard in a terrible sub-leased office and building release binaries on my laptop. That was fun once, but I'm ready for a new phase in my own life. I've heard the horror stories of being acquired by IBM, but I've also heard from people who have reveled in the resources and opportunities. I'm hoping for the best for Nomad, our users, and our team. I'd like to think there's room in the world for multiple schedulers, and if not, it won't be for lack of trying.

Don’t worry: we’re indirectly thinking about Rome by thinking about their perception of ancient Sparta. Rome is the Kevin Bacon of western historical thought: we’re never more than 6 hops away.