sam_perez

This is a bit topical for me. Game performance seems to be a real problem as of late... It’s not uncommon for me to play “retro” games that run poorly on my 4-series Nvidia gpu. Not a game developer myself but this is definitely still a problem in 2025.

My first thought/question as well.

How do you ensure this? Are you suggesting more analysis pre-building the product, or doing things like increasing the price until you've effectively filtered out enough of the people you don't "want to deal with", assuming that works.

To be fair, it seems like the cloud development environment choice was driven by the scale of Stripe's organization.

Any other Simon Lizotte and/or disc golf fans here? :D

Hah, that is much fewer than I would have expected.

Too bad you can't do the same with phone numbers.

How would you rate the quality of the dubs?

Do you think it's usable for learning? Seems like you could end up with some quirky learnings.

Oh cool, how would you compare this to DuckDB?

+1 for a reference to The Culture series :D

Lol no not generally ;)

Just did not expect to be gazing into the windows of someone's soul immediately. The widescreen monitor may have contributed.

Clicking on the link without knowing what it was ahead of time was jarring, even not actively participating.

Beautiful.

----------------------------

This controller is intentionally written in a very verbose style. You will notice:

1. Every 'if' statement has a matching 'else' (exception: simple error checks for a client API call)

2. Things that may seem obvious are commented explicitly We call this style 'space shuttle style'. Space shuttle style is meant to ensure that every branch and condition is considered and accounted for - the same way code is written at NASA for applications like the space shuttle.

----------------------------

^^^^

This bit reminds me of exhaustive checks in typescript code. I try to use them all the time.

https://www.typescriptlang.org/docs/handbook/2/narrowing.htm...

Reminds me of some scenes from the first book of the three body problem.

I think the fact that a human can mostly just read csvs is an important part of their adoption, too.

Yeah, this does seem like an odd middle ground.

But I suppose it's more about what you're tracking? For example, instead of tracking reference counts to variable, they're tracking reference counts to each scope. Then, if a scope has no more references, the variables it owns are cleaned up.

Very cool, are you one of the paying users or are you on the free version?

This tool seems really cool, want to play with it for sure.

Just in general, semantic search across text seems like a much better ux for many applications. Wish it was more prevalent.

Yeah, it's a bit clunky. Maybe plays better on mobile?

That's really cool. One of the benefits of the JS ecosystem is the ability to step through code and crack open your dependencies. Not sure if this would directly make this possible when running your projects/tests, but it at least sounds like a step in that direction.

Yeah, I can already feel the prompts for scripts being entered into an LLM...

The name is so close to being truly perfect, but I guess being just a little bit off is a perk here?

Really cool. I couldn't find it documented anywhere, but if you save the unique (guid) url generated, how long is that available for? "Forever"?

Hi HN!

I want to share a service we’ve been working on called 2Secured and ask for feedback. It's a tool to send sensitive information using end-to-end encryption.

Here's a link to our landing page: https://2secured.link/

I’ve worked at several companies where the standard for sending or receiving secrets inside and outside the company (passwords, api credentials, documents, ...) was to send/receive them in an email or in slack. Secrets not only lived in their final destination, but were also persisted in many different third party communication services in clear text. It was a common practice and a compliance nightmare.

2Secured ensures that the secrets you send and collect remain private and secure. We’ve abstracted away the pipes for sending and collecting secrets, allowing you to collect and send e2ee data with simple secure links, user friendly customizable forms, and in the future, easy integrations with your backends via SDKs and APIs. We’re also layering in features such as customizable link expiration and email confirmation to view the secrets.

You can share confidential documents, personal data, and other sensitive information without worrying about leaving plain text secrets in intermediate services. You also don’t have to worry about implementing your own internal tools or pages for fulfilling common data requests from clients or partners. It's made for companies or professionals who need handle private information regularly, such as legal documents, medical records, financial data, API keys, pass-phrases, etc.

Has anybody else come across this issue in any of the organizations you've worked in? How have you approached solving the problem?

Please ask any questions or share your experiences! Any feedback on the tool would be greatly appreciated!

Cheers!