Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
aseipp
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
35 ms
·
361.
▲
by
aseipp
3y ago
Yes, really. There were other reservations about shader compilation in particular from other participants, Apple wasn't alone in that department (e.g. asset sizes and needing to fork the format to maintain compatibility guarantees). Th
362.
▲
by
aseipp
3y ago
Can't you have that today by using Dawn (used by Chrome) or wgpu (used by Firefox) as a dependency? That said, a third implementation would be nice, too!
363.
▲
by
aseipp
3y ago
Yeah, right now for auth, if you want to use e.g. OIDC I think the best you can do is to essentially shove everything in the square hole using very short-lived SSH certificates and OOB auth flow; e.g. "open this browser link to get a c
364.
▲
by
aseipp
3y ago
My best friend does this and it both drives me insane sometimes but also blows my mind. It's how he has always used Google search. He does not use keywords at all, he simply states the generalized phrase out loud. Like if we're ta
365.
▲
by
aseipp
3y ago
To be clear, you can probably make a 1000 core x86 machine, and those 1000 cores can probably even be pretty powerful. I don't doubt that. I think Azure even has crazy 8-socket multi-sled systems doing hundreds of cores, today. But thi
366.
▲
by
aseipp
3y ago
Some observations: - Very bad performance at existing x86 workloads, so a major selling point was basically not there in practice, because extracting any meaningful performance required a software rewrite anyway. This was an important adopt
367.
▲
by
aseipp
3y ago
It doesn't work if you're going against GPUs. All the nice goodies we are accustomed to on large desktop x86 machines with gigantic caches and huge branch predictor area and OOO execution engines -- the features that yield the per
368.
▲
by
aseipp
3y ago
It would just be a nice way to turn your standalone WASM game into an .exe (or whatever equivalent) without needing too much extra stuff, like if you wanted to distribute a version on Steam, or offer multiple downloads like itch.io does. It
369.
▲
by
aseipp
3y ago
This whole thread is confusing. The blog in the OP, the comments section of which are you posting in right now, is literally about adding WebGPU support to a headless JavaScript interpreter Deno, that includes no HTML/CSS/DOM/
370.
▲
by
aseipp
3y ago
Many systems take various kinds of performance hits in return for things all the time; reliability, observability, safety, etc. Many systems can be run at higher peak throughput in return for various instabilities, even. Performance is not
371.
▲
by
aseipp
3y ago
You could build Software Fault Isolation into an existing compiler toolchain, and people have done it, but WebAssembly comes with an existing constraint which is why it's designed the way it is: a WASM file may be generated by an unkno
372.
▲
by
aseipp
3y ago
There are other advantages aside from the static types debate in the other replies. The need for efficient version control systems is a constant and ongoing battle; you can pick the right data structures (for example, Git's issues with
373.
▲
by
aseipp
3y ago
Just echoing Martin, but: if you can show the repository that is causing this, or at least a screenshot (or something) showing what you're seeing and post it on GitHub, one of us should at least be able to help figure out what's g
374.
▲
by
aseipp
3y ago
They don't require really expensive and power-hungry components to run, i.e. a mid-range GPU can run a (4-or-5-bit quantized) 7B model at +50 tokens/second, so it's completely feasible to run on a small budget. They are easie
375.
▲
by
aseipp
3y ago
WSL1 did not use the NT codepath in order to spawn processes. WSL1 had its own direct support in the kernel for its own process type ("nanoprocess" is what they called it IIRC) managed independently from NT processes; and it even
376.
▲
by
aseipp
3y ago
No, but I spat out a vague answer rather quickly and was too flippant ("maybe you could do something"), so it's a fair question. Realistically, even the motherboard design, including landing pad on the PCB and boot sequence o
377.
▲
by
aseipp
3y ago
Yes, that's my point. The M1 Pro is also 5nm, would you say that the M1 losing badly to the M3 means 3nm is way better than 5nm? No, the architectural differences mean that trying to derive or compare performance characteristics of the
378.
▲
by
aseipp
3y ago
Maybe I'm misunderstanding you but: no, you can allocate terabytes of address space on modern 64-bit Linux on a machine with only 8GB of RAM with overcommit. Try it; you can allocate 2^46 bytes of space (~= 100TB) today, with no proble
379.
▲
by
aseipp
3y ago
That is Chromium doing it, and yes, it is using mmap to create a very large, (almost certainly) contiguous range of memory. Many runtimes do this, because it's useful (on 64-bit systems) to create a ridiculously large virtually mapped
380.
▲
by
aseipp
3y ago
You can only meaningfully determine that if you assume the die is more-or-less the same between the two versions. It is not; the M3 Pro has many changes, the perf/efficiency core ratio is different, they have different amounts of per-c
381.
▲
by
aseipp
3y ago
They don't sell these. They reuse them and perform maintenance on them until their last breath and part them out once they die. Hyperscalers design their own datacenter "SKUs" for storage/compute, all the way from power
382.
▲
by
aseipp
3y ago
Neoverse V2, so this will be probably be the first widely available ARMv9 server with SVE2, a server-class SKU you can actually get your hands on (i.e. not a mobile phone/Grace/Fugaku.) It's about damn time!
383.
▲
by
aseipp
3y ago
There are third party tools like Graphite, CodeApprove, and Reviewable that will basically add these workflows on top of the existing GitHub API. There's a much more detailed and complex answer to this question (TL;DR you can kind of f
384.
▲
by
aseipp
3y ago
> why don't version control systems (especially ones that can change history) have undo/redo functionality out of the box? It's true. And Jujutsu has undo functionality out of the box, too. It's not just Sapling. :)
385.
▲
by
aseipp
3y ago
Like the parent said, you typically let the "automatic working copy commit" take the place of the staging area. Really, the staging area still exists in some sense, but it's not a distinct "thing" in the UX; rather
386.
▲
by
aseipp
3y ago
Yes, it's long-winded, and unfortunately, it's really hard to get across with the above description that the workflow described therein actually is quite simple with the correct tools, and (at least in my opinion) also results
387.
▲
by
aseipp
3y ago
I completely rewrote the README recently to be more "user friendly"; does it address some of your question? I'm not trying to be snarky, I'm genuinely interested in if the README is now tantalizing enough to make you int
388.
▲
by
aseipp
3y ago
Most of the projects that dislike GitHub's review UI want the functional equivalent of `git range-diff`. Code review systems like Phabricator and Gerrit basically revolve around this as basis of thinking about diffs, their evolution, a
389.
▲
by
aseipp
3y ago
Google currently uses a fork of Mercurial as the frontend to Piper, but there is work to replace it wholesale, eventually: https://github.com/martinvonz/jj (As a disclosure, I'm involved with and contribute to jj,
390.
▲
by
aseipp
3y ago
Sapling can use Mononoke, but it can also use Git repositories as the underlying storage layer with no server at all, and it does so by default in the OSS build. You can use it just fine with GitHub today, but there are rough edges. My unde
More ›