Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
wtallis
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
33 ms
·
721.
▲
by
wtallis
1y ago
> A more interesting example might be if each slot in the target array has the next index to go to in addition to the value, then you will introduce a dependency chain preventing this from happening. However, on some processors there
722.
▲
by
wtallis
1y ago
Obviously there's no point in trying to entirely prevent people from DIYing dangerous devices, medical or otherwise. But that's not what's at issue here. The problem here is the absolutely stupid idea of using a desire for da
723.
▲
by
wtallis
1y ago
The point is to have an avenue for recourse/accountability when the developer is not behaving.
724.
▲
by
wtallis
1y ago
Turning your iPhone into an unregulated DIY medical device really does not seem like the kind of use case that any serious business would be swayed by. What you're asking for would be pretty terrifying for the lawyers. You shouldn&#x
725.
▲
by
wtallis
1y ago
PEP 723 was incorporated (with modifications) into the official Python packaging specifications: https://packaging.python.org/en/latest/specifications/inline... I don't think running with uv vs uvx impos
726.
▲
by
wtallis
1y ago
> So your question effectively boils down to "why do people need to compile their own software?". No, the question is why a package would need to decide for its users that the package and its dependencies must be installe
727.
▲
by
wtallis
1y ago
Even using `uv add`, you don't have to limit yourself to declaring exact versions when your intention is to allow newer versions.
728.
▲
by
wtallis
1y ago
Can you elaborate on the reasons why a package would need to declare that its dependencies must be installed from source rather than from pre-built binaries? I'm having trouble imagining a scenario where that capability would be used a
729.
▲
by
wtallis
1y ago
> What I want is, if my project depends on `package1==0.4.0` and there are new version of package1, for uv to try install the newer version. I think you're just specifying your dependency constraints wrong. What you're asking f
730.
▲
by
wtallis
1y ago
Nitpick: the "Platinum" color in question was part of the "Snow White" design language introduced in 1984 (and originally using a different color before switching to Platinum) so this is the wrong filament for emulatin
731.
▲
by
wtallis
1y ago
Yes, we know that floppy disks and drives will wear out, and they have few if any sources for new repair parts. So the fact that the system is still more or less working today doesn't mean it isn't doomed and needs to be replace
732.
▲
by
wtallis
1y ago
The drive in question is a low-end consumer part using QLC NAND and a DRAMless controller. It's hard to conclude much about the scalability of an operating system's IO stack when using a single drive that has such limited performa
733.
▲
by
wtallis
1y ago
You're completely ignoring that there are several distinct market segments that want hardware to do AI/ML. Matrix multiplication is not something you can implement in hardware just once. NVIDIA's biggest weakness right now
734.
▲
by
wtallis
1y ago
> Wondering how you'd classify Gaudi, tenstorrent-stuff, groq, or lightmatter's photonic thing. Completely irrelevant to consumer hardware, in basically the same way as NVIDIA's Hopper (a data center GPU that doesn't
735.
▲
by
wtallis
1y ago
That doesn't really change anything. The use cases for a GPU in any given market segment don't change depending on whether you call it a GPU. And for low-power consumer devices like laptops, "matrix multiplication coprocess
736.
▲
by
wtallis
1y ago
Arithmetic co-processors didn't disappear so much as they moved onto the main CPU die. There were performance advantages to having the FPU on the CPU, and there were no longer significant cost advantages to having the FPU be separate a
737.
▲
by
wtallis
1y ago
The ability for an app to keep running without a window was a godsend back in the days when we were all running on hard drives and large apps had splash screens to amuse you during their multi-second launch process. If you were done with a
738.
▲
by
wtallis
1y ago
There's also the simple fact that shipping an identical UI on multiple operating systems is obviously wrong for a least some of those operating systems (and maybe all of them). You don't have to worry about "platform intr
739.
▲
by
wtallis
1y ago
Yes, only the 32-bit target, and only the gnu toolchain. Compiling on Windows using the Microsoft toolchain to target 32-bit Windows will still be on the Tier 1 list: https://doc.rust-lang.org/rustc/platform-support.htm
740.
▲
by
wtallis
1y ago
Depending on the weather and how much you're cooking, an 8-day trip may be long enough that the low energy density of alcohol fuel outweighs the size advantages of the stove.
741.
▲
by
wtallis
1y ago
Map editors and modding have always been pretty common for both turn-based and realtime strategy games, and the entire MOBA genre originated from RTS mods. Bethesda RPGs have active modding communities in part because they always need commu
742.
▲
by
wtallis
1y ago
Memory usage can vary, but video codecs are designed to make it practical to derive bounds on those memory requirements because hardware implementations don't have the freedom to dynamically allocate more silicon.
743.
▲
by
wtallis
1y ago
Is anyone using EUV for SSDs? I don't think it's economical for NAND manufacturing. I'm not sure if SSD controllers are using EUV yet; they usually aren't on leading-edge process nodes.
744.
▲
by
wtallis
1y ago
It's possible that at this point, a majority of the people who have ever used Excel to calculate anything have done so on a laptop that doesn't even have a numeric keypad. Certainly, that fraction of the cumulative historical Exce
745.
▲
by
wtallis
1y ago
The craziest thing about Intel's AVX-512 story is that from 2015 through 2020 they were shipping consumer CPUs with die space reserved for the AVX-512 register file, but no actual AVX-512 capability. Then they shipped one short-liv
746.
▲
by
wtallis
1y ago
The legal risks were at most the last straw. If Optane had a promising future, Intel could have made the investments necessary to make the legal issues go away. If Optane had a promising future, Micron would have helped Intel secure that
747.
▲
by
wtallis
1y ago
AVX-10 was mostly just a way for Intel to provide an excuse for why they're still a few years out from having AVX-512 in their E cores: they're targeting a standard that's not here yet. But the excuse doesn't really work
748.
▲
by
wtallis
1y ago
If it's pure TFLOPs you're after, you do want a more or less statically scheduled GPU. But for CPU workloads, even the low-power efficiency cores in phones these days are out of order, and the size of reorder buffers in high-perfo
749.
▲
by
wtallis
1y ago
This issue is less about Intel's fab failures and more about their inability to decouple their architecture update cadence from their fab progress. They stopped iterating on their CPU designs while waiting for 10nm to get fixed. That l
750.
▲
by
wtallis
1y ago
> But I think to boot from an unexpected AHCI controller you might need a boot rom? The whole point of AHCI was that you wouldn't need a boot ROM. You already have firmware support for talking to an AHCI controller to find drives
More ›