Recent submissions

Comment · 2 years ago
I too was surprised to read that they were syncing what reads, at a glance, to be their entire database into the data lake. IIUC the reason that Snowflake prioritizes inserts over updates is because you're supposed to stream events derived from your data, not the data itself.
Comment · 2 years ago
I was hoping to open this and see screenshots of what the OS looked like—I have never had a sense of what the OS for Meta's headsets is, only what individual games look like.

Instead, we get five (5) "Not an actual product render" illustrations.

Comment · 3 years ago
This article barely describes why the mushrooms did _not_ eat Luke Perry, despite acknowledging that up top. All it suggests is that autolysis enzymes kill the mushrooms?
Comment · 3 years ago
Also Swift!
Comment · 3 years ago
This reflects astonishingly poorly on Brex. What customer wants to hear that Brex is using "a non-deterministic model" for "production use cases" like "staying on top of your expenses"? I don't see them acknowledge the downsides of that non-determinism anywhere, let alone hallucination, even though they mention the latter. Hallucinating an extra expense, or missing one, could have serious consequences.

This is also potentially terrible from a privacy standpoint. That "staying on top of your expenses" example suggests that you upload "a list of the entire [receipts] inbox" to the model. It _seems_ like they're using OpenAI's API, which doesn’t use customer data for training (unlike ChatGPT), but they should be crystal clear about this. Even if OpenAI doesn't retain/reuse the data, would Brex's customers be happy with this 3rd-party sharing?

The expenses example seems like sloppy engineering too—there's no reason to share expense amounts with the model if you just want it to count the number of expenses. Merchant names could be redacted too, replaced with identifiers that Brex would map back to the real data. These suggestions would save on tokens too.

Despite Brex saying they're using this in production, I suspect it's mostly a recruiting exercise. It's still a very bad look for their engineering.

Comment · 4 years ago
Comment · 5 years ago
The best thing to do would be to plow this money back into vaccine production and distribution, since that's the reason that the wealthy shouldn't be able to shortcut the process in the first place—it needing to work well for everyone.
Comment · 6 years ago
What’s the timeline for Phase III trials? The article doesn’t seem to say. I don’t feel reassured that those won’t be rushed.
Comment · 6 years ago
Yeah I do not understand why the author waited so long to disclose and also feels that Google deserves a "stellar job" here. Sure, Google patched the bug very quickly after disclosure. But given that Google waited so long, it sure looks like they only prioritized the fix once disclosure was a risk. If anything, I think that the author should have scheduled disclosure sooner.
Comment · 6 years ago
What’s MCN?
Comment · 6 years ago
It's crazy to me that the EU is wasting their time making Apple use the same ports as other smartphones (https://appleinsider.com/articles/20/02/02/what-the-eu-manda...) when they could make it easier to replace _any_ Apple component with an equivalent. I see the other comments saying that this guy deserved to lose this specific case since he was calling the parts "refurbished" but it's not clear that there's any way for him to use aftermarket parts legally.
Comment · 6 years ago
Folks should know that this approach will not accommodate upcoming changes to Chrome extensions, which will disallow all remotely-hosted code: https://groups.google.com/a/chromium.org/d/msg/chromium-exte.... More up-to-date guide here https://developer.chrome.com/extensions/migrating_to_manifes..., with a timeline of 2020. I understand why

> one thing we wanted to prevent was developers including the stock SDK directly in the extension

(and I feel for Streak, having worked on a Gmail extension (Mixmax) until recently), but this seems to be exactly what manifest v3 will require. Curious if you have another strategy, @alooPotato.

Comment · 7 years ago
Hey Venkat! Thanks for replying in good humor.

Now that you explain your reasoning a bit, and upon re-reading https://en.wikipedia.org/wiki/Serverless_computing, I think using "serverless" in this context makes sense. I see "serverless" used so much more often to describe compute runtimes like AWS Lambda than databases that, I confess, I thought you might be trying to ride that wave's popularity; and/or that you might be using "serverless" _just_ because the servers were managed by you not the users, whereas you allocate capacity on a more granular level than the server.

I do still recommend you take out the "cloud hardware" bit ;D

Thanks for the explanation, and best of luck! Cool model.

Comment · 7 years ago
Calling a hosted database "serverless" is the most brazen branding I have seen in a long time. For extra hilarity, their pricing page says "pricing is inclusive of cloud hardware".

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton