Comments URL: https://news.ycombinator.com/item?id=48575655

Points: 3

# Comments: 1

If you want to run as another user, you need to manually add an /etc/group & /etc/password (or generate them in a stage before that and copy them over).

If you need ca-certificates, you need to install ca-certificates in a stage before that and copy over /etc/ssl/certs/ca-certificates.crt from that stage to your current one.

QuickBooks has annoying suggestions that shift the whole UI and cannot be disabled. Misclicks now happen.

The AI in my robot vacuum is... just a label? I don't want to talk to it. I want it to deterministically clean my stuff.

My TV got an upgrade to Gemini. Why? I don't talk to the TV, and it's in my face. (I'm think about getting a device that can do Plex->Atmos streaming).

But when Docker scans my image and notices that there is a CVE in one of those binaries, my image is currently out of compliance.

FROM scratch just reduces the surface.

So we start at compiling the codebase (Rust) against MUSL. That way we can run it with FROM scratch images.

If we need more tooling available at runtime, then we look at alpine, but still using MUSL.

If MUSL itself is proving problematic, or if some of the libraries we use need glibc then we can look at using some locked down image.

The cool part about FROM scratch images is that you'll never have to update your base image to address CVEs. Only your software and its (compiled) dependencies.

Does Mozilla have a contract with Google to not build one in as part of the search contract?

I myself have never worked with C++/CX or C++/WinRT. My Rust journey has been exclusively on POSIX systems, so seeing windows-reactor and getting a UI in a couple of lines is pretty cool.

I would never (at least not in its current state) recommend it for production though, as the crate containing reactor isn't even on crates.io.

Could you share some of the promises made that were abandoned? (I just realized that question sounds like AI... I promise you it's not).

https://github.com/microsoft/windows-rs/tree/master/crates/s...

It's a react-style API for WinUI3 apps, meaning it's not trying to mimic the Windows LAF. It's merely a binding.

But the problem is that for many people they now believe it's ok to present a 10k line vibe-coded PR that only has been verified against external behavior, and some Senior Engineer needs to review it, in time, under pressure, without too much push-back, and lastly, it's the Senior Engineer that gets paged at 2am because something has fallen over.

Also, those scripts tend to start a life of their own, and because it looks good enough, people don't look at them again.

I recall a bug of someone vibe-coding a cleanup script for folders older than $x (on Windows).

Get the CreationDate, and sort. Delete older than $x. Except CreationDate can be null and null is always smaller than $x.

Oops.