Recent submissions

Comment · 3 years ago
It was fixed.
Comment · 3 years ago
Duplicate, which also got on the front page without a working link: https://news.ycombinator.com/item?id=36881510

What's your secret for getting 1 upvote per minute even when the link doesn't work?

Comment · 3 years ago
Same. Interesting that a broken link can get so many upvotes so quickly.
Comment · 3 years ago
The lede is that 2 orders of magnitude more of injury exists than previously detected. 1 in 35 showed signs of heart damage.
Comment · 3 years ago
Why be secretive about abusing a loophole with a company you might have a relationship with?
Comment · 3 years ago
To go back to my original post, my main beef is with turning an imperative language into a declarative one. If you've seen enough of these types of languages degrade, you start to see a pattern.
Comment · 3 years ago
I don't really know what you're saying, can you say it another way? "Most realistic evolution"... why is that needed? If the problem is different database engines implementing the SQL spec differently, that's not something that can be papered over with another abstraction without a lot of wrinkles.
Comment · 3 years ago
This is the closest example I could find https://www.pulumi.com/docs/concepts/how-pulumi-works/

Pulumi serves as the strongest contender to Terraform when doing IaC (infrastructure as code). Terraform attempts to be a declarative markup language (HCL) but it has a lot of weird imperative quirks due to (understandably) trying to support common complex use cases. In the end they have a clunky custom language that tries to do what general programming languages have done well forever. Pulumi doesn't re-invent the wheel, and lets programming languages do what they do best. Pulumi only really cares that the programming language generates a declarative spec that can be used to compare with your infrastructure. It's the best of both worlds.

Comment · 3 years ago
>declarative

An admirable ideal, but declarative languages always seem to devolve towards some frankenstein imperative/declarative hybrid. We need to stop going down this path and embrace Pulumi's pattern: use existing general purpose imperative languages to generate a declarative structure. Instead, people try to take their not-mature declarative language and fit a weird general purpose language inside it.

EDIT>> I'm not suggesting that SQL needs to be declarative, only that if a problem space would benefit from declarative structures, generate them imperatively instead.

Comment · 3 years ago
Comment · 3 years ago
>And yet we know perfectly well that there were many people who were vaccinated who did get breakthrough infections and some of those have gone on to get long Covid, but we know that in those breakthrough cases in the vaccinated people, your chance of long Covid is further reduced perhaps by another 50 percent.

As far as I see, they aren't referencing a specific study. But they are clearly making a connection between your long covid chances and vaccination. Does anyone have a link off hand to this data?

Comment · 3 years ago
How do you do science on LLMs? I would imagine that is super important, given their broad impact on the social fabric. But they're non-deterministic, very expensive to train, and subjective. I understand we have some benchmarks for roughly understanding a model's competence. But is there any work in the area of understanding, through repeatable experiments, why LLMs behave how they do?

Do we care?

Comment · 3 years ago
"I don't think about you at all."

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton