Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sfink
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
51 ms
·
631.
▲
by
sfink
2y ago
Dumb question: it seems like this assumes that once you have allocated a spot within an atlas, you can't move it. But wouldn't it be a within-GPU transfer to garbage collect a fragmented atlas into a new texture? If so, then could
632.
▲
by
sfink
2y ago
Yes, it would be nice to see what organizational roadblocks they're putting in place to avoid an OpenAI repeat. OpenAI took a pretty decent swing at a believable setup, better than I would have expected, and it failed when it was calle
633.
▲
by
sfink
2y ago
That doesn't necessarily imply that chat logs are not valuable for creating AGI. You can think of LLMs as devices to trigger humans to process input with their meat brains and produce machine-readable output. The fact that the input wa
634.
▲
by
sfink
2y ago
How so? If you have a pile of explanations, you now have a way of dividing up the pile into ones you may want to keep and ones you should discard. That way is by asking whether an expert would understand what you're talking about. Occa
635.
▲
by
sfink
2y ago
First, if your extraction method is at all efficient, then much of the energy you extract is going to end up as heat again. Sure, it'll be somewhere it can more easily radiate to space, but rock is a pretty good thermal conductor too.
636.
▲
by
sfink
2y ago
It sounds like by default the slag is in the form of ash. That's actually the main advantage I was thinking of; current long tunnels require mixing it with water to make muck and transporting it all the way back out. I don't know
637.
▲
by
sfink
2y ago
Dumb question: is there any use for this for horizontal drilling? I'm imagining scaling up the size of the drill head to the size of a car-carrying bore hole, vaporizing the rock (or whatever gets in your way) and using some of it to r
638.
▲
by
sfink
2y ago
A witness reported observing the accused shaking the baby, therefore you find it safe enough to assume that the baby was killed by shaking. Safe enough that you would murder him with the legal system? Despite knowing that the baby had sev
639.
▲
by
sfink
2y ago
That's not exactly right. I believe you're mixing up bytecode generation with compilation. The source code will indeed be compiled down to bytecode, but that doesn't count since it does not change the generality. As in, bytec
640.
▲
by
sfink
2y ago
It's interesting to see the parallels between this and an engine for a dynamic programming language. The one I'm most familiar with is JavaScript. When you first need to run something, you run it on the interpreter (JS) / ube
641.
▲
by
sfink
2y ago
The limited time duration is a big deal, I agree. It's an extrapolation from insufficient data. (Though the studies were evidently powerful enough to come up with a number, so the probability is not that near 0.) But that also means
642.
▲
by
sfink
2y ago
I think you're reading it backwards. If you look closely at how medicine is done today, you will see that there are many areas where it is wildly divorced from reality. So, the point was not "we'll be vastly better soon"
643.
▲
by
sfink
2y ago
That's quite the evisceration of a strawman that you've got there. He certainly won't be walking to Oz with Dorothy anytime soon. My counterpoint: - Most code reviews of my code don't find bugs. - At least half of the bu
644.
▲
by
sfink
2y ago
I disagree. I found it to be a very nice approachable high-level walkthrough of what CE can do. I've used CE for various things, but still learned about several capabilities that I didn't know about and can make use of. And callin
645.
▲
by
sfink
2y ago
> You can very much have a single vector owning the memory, and do all other ordering over auxiliary vectors of indices. Should be cheaper and faster than holding more linked lists. Cheaper in space depends on the percentage of elements
646.
▲
by
sfink
2y ago
Intrusive linked lists eliminate the allocation entirely. With a vector<Obj>, you have the Obj allocation and then potential vector-related reallocations. With an intrusive linked list, you only have the Obj allocation. So your code t
647.
▲
by
sfink
2y ago
First, my only guess is that everyone's guesses are going to be wildly wrong. People who work in such spaces will greatly overestimate. People who don't will greatly underestimate. (This is mostly due to how many comments I'v
648.
▲
by
sfink
2y ago
Linked lists get a bum rap. Yes, if you have a simple choice between a vector and a linked list, then the vector is vastly superior due to locality and (for non-intrusive linked lists) allocations. So much so that vectors often win even whe
649.
▲
by
sfink
2y ago
> How are you doing? I am a large language model and currently have no state. This is the beginning of a new conversation. > But how are you? I apologize. When I previously stated that I have no state, I was answering based on my stat
650.
▲
by
sfink
2y ago
It's a fine phrase, evocative, that I agree has become cliché. But that's not the problem here. The problem here is that it's being misused. It works when there's something that is problematic for taking up space in your
651.
▲
by
sfink
2y ago
If that's their point, then they should say that, instead of saying something else. "Shot on an iPhone" is a lie in context.
652.
▲
by
sfink
2y ago
A Sony A7iv has threads for attaching lenses. An iPhone does not. It's like if I feed you a six-course gourmet meal and tell you "I made it on a camping stove", when in fact the camping stove was just used to keep one of the
653.
▲
by
sfink
2y ago
As a nerd, I love to see carefully maintained illusions that give a convincing impression of something much more grand going on than is actually happening. Games that push for more and more realism make me wonder why I don't just wande
654.
▲
by
sfink
2y ago
Because the machine is a physics simulation. Where users can set up simulated physical objects like barriers and bumpers, and you want the animation to display a simulation of what happens according to the laws of physics. I think you may b
655.
▲
by
sfink
2y ago
Not exactly related to the article, but reading it triggered a sudden realization: vampires are just big capacitors. If you put a stake through their heart, you connect all the plates (possibly many layers of them) and they are vaporized in
656.
▲
by
sfink
2y ago
> Those same phishing emails can just ask you to install some random non-browser software or activate any number of other insecure things. Yes, because those native apps have access to a much larger attack surface. (As in, they already h
657.
▲
by
sfink
2y ago
I largely agree with the thrust of the article, but wow is it one-sided. Which is fine, I'd just like to read another article that discusses some of the issues as well. Like air quality—the mention of smoke being thick enough to drop s
658.
▲
by
sfink
2y ago
> Users aren't presented with a "barrage" of consent dialogs. There's not even that many of them And that is the result of a lot of hard work and pushing back on... well, on things like this. There are already enoug
659.
▲
by
sfink
2y ago
Those are the easiest tests to write, and probably pretty unlikely to find anything unless the feature you're adding is exposed via SQL pretty directly. I was thinking more like lots of concurrent operations, and backups/restores
660.
▲
by
sfink
2y ago
There are some striking similarities to working on another large OSS codebase: Mozilla. (I am employed there.) We have struggled with all of these things for years, and we have a much larger pool of committers (and thus much higher variance
More ›