jeswin

I know, but looking at how quickly people got it running on a few other phones (I've seen pixel 1, 4 and 6, a samsung, and another), I'm thinking that codex or claude code is exceptionally good at this class of work.

I'm saying the hobbyist community for phones is massive - this is not for regular phone users. And they all have older (but fast enough) phones lying around to try something like this on.

Looking at the comments, I get the feeling that HN has no idea how big this is going to get.

Agents are going to move this project into acceptable usability and performance in 6-12 months, across a broad set of Android phones. You're going to see people loading iOS on $299 phones, with grey zone marketplaces for app packages (like Android has had for ever).

Hackintosh was a small hobbyist community. Phones will be 100x that. There's going to be very little money in it, but I'll be surprised if this doesn't explode.

You're on a website called "hacker" news. Inclined to downvote so that this doesn't take up conversation space.

> Separately would say it is a bad assumption to make that a product is vibe coded without trying it out.

You've put it behind a very typical AI-generated UI; like the many that come up every day. In your case, it's an auth product and it matters more. Besides, It's difficult to try your product without handing you the keys to the kingdom.

> We are currently in the process being fully SOC2 compliant

You're getting a Type I attestation first, I presume? That is of limited value in itself, and is mostly about getting to Type II. If you already have Type I complted, you could mention that on the website. "Regulated industries" have long sales cycles and evaluations, and you'll find it difficult to start those conversations without a more reassuring website.

This might seem like an aggressive question. But it's one to be asked of products dealing with auth.

For a security-centric product, how would I trust your fully vibe-coded product if I can't see the source code?

> You can't run C# without the .NET runtime

With NativeAOT, same a golang then. NativeAOT has worked wonderfully for us, and in some specific situations faster than Rust.

> That's because there's no such thing as a "performant language".

That's not true. Many languages make tradeoffs for performance. There are many things in JS (or Python) which make optimizations difficult and sometimes impossible. For example - obj[key] = "haha".

Not a lawyer, but what if someone did this:

- Find examples of content that will constitute infringement. Then send Meta legal a notice saying here are examples where the publisher does not own the content, and their scraping is not legal. Our current/future clients will be damaged by Meta's planned actions.

This might elevate it to willful infringement.

I've seen prion disease up close with someone dear. I couldn't sleep thinking about what could have been going through their minds. It was 6 months of torture, and if I were in the same situation I'd have preferred someone switch me off.

I remember reading about Sonia Vallabh (and their race against time) - I'm so glad they're getting somewhere. Kudos.

Dynamic memory hot-plugging is still not as efficient. So if you don't want strict isolation between containers or individual sandboxes around each one of them, avoid VMs to achieve the highest density per box.