Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kllrnohj
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
91.
▲
by
kllrnohj
4mo ago
> Nor if one of the soundness holes in the Rust programming language itself is encountered. imo one of those soundness holes is caused directly from trying to prevent UB - integer overflows. It is inconsistent in Rust what happens in t
92.
▲
by
kllrnohj
4mo ago
I use Firefox mobile pretty much exclusively. I haven't noticed any meaningful performance difference between it & Chrome. It also seems to perform fine on my Fedora laptop.
93.
▲
by
kllrnohj
4mo ago
regardless of whether that's true or not, US companies doing hosted inference of the models coming out of China are also significantly cheaper than those from OpenAI or Anthropic
94.
▲
by
kllrnohj
4mo ago
Every build system ever says hello.
95.
▲
by
kllrnohj
4mo ago
> But if someone told me to write C++ myself, I'd cry. There's too much to memorize, and the standards are too varied If someone tells you to write a web app, do you also cry? Surely there's more JavaScript frameworks than
96.
▲
by
kllrnohj
4mo ago
> I really recommend against using C++ for safety-certified embedded software. Stick to C. You're almost certainly better off with Rust at this point or, if you must have C-like development, Zig.
97.
▲
by
kllrnohj
4mo ago
they are talking about the scenario of having a discreet GPU in addition to the GPU on the CPU. So there's 2 GPUs, and the nvidia one has its own VRAM (typically of the GDDR variety even) that isn't shared with system RAM (hence
98.
▲
by
kllrnohj
4mo ago
The problem isn't how bright should 1023 be. The problem is how bright should diffuse white be (aka graphics white or SDR white)? None of HDR10, HDR10+, or DoblyVision ever attemped to address that question. Which is a pretty important
99.
▲
by
kllrnohj
4mo ago
Bit depth is precision. HDR or SDR are the range . They are orthogonal concepts. But at a high level you're basically asking "why doesn't scRGB exist" and, well, it does :) https://en.wikipedia.org/wiki&
100.
▲
by
kllrnohj
4mo ago
Wouldn't this prevent the nvidia GPU from being power gated since it's never "idle"? So like your battery life regresses?
101.
▲
by
kllrnohj
4mo ago
MediaTek's press release pretty clearly indicates the CPU came from MediaTek, and so far Nvidia doesn't have any custom CPU core they've called "Grace". Seeing as the DGX Spark has what seems to be the same core chi
102.
▲
by
kllrnohj
4mo ago
> tbh, I always read this as Intel doing some sales magic here. Possibly, but Apple choosing a new, thicker chassis the same generation that they introduce their more power efficient replacement is certainly a thing. Even if Intel fail
103.
▲
by
kllrnohj
4mo ago
The DGX Spark doesn't have a battery. If it comes with 200W delivery (actually 240W), it's because it plans on consuming close to that amount. Although I'm kinda surprised the DGX Spark used USB-C at all for power instead of
104.
▲
by
kllrnohj
4mo ago
USB 4 v2 has the same display capabilities as TB5. In fact, TB5 gets its display capabilities from USB 4 v2
105.
▲
by
kllrnohj
4mo ago
Doesn't it come with Nvidia's blend of Ubuntu with a custom kernel? Do other distros work as well as "DGX OS" or are nvidia's kernel changes pretty important to have?
106.
▲
by
kllrnohj
4mo ago
MediaTek said MediaTek made the CPU: https://www.mediatek.com/press-room/mediatek-collaborates-wi... Well, MediaTek actually said they made most of the SoC in fact. But the actual CPU cores themselves are all but cer
107.
▲
by
kllrnohj
4mo ago
For Apple it worked because they waited until they had a really, really good ARM ISA CPU (combined with arguably sandbagging their x86 offering for a few years prior but I digress). Qualcomm is also working on a really good ARM ISA CPU with
108.
▲
by
kllrnohj
5mo ago
> no. GC pauses turn any serious systems work into hell. did you miss the context I was responding to? They were comparing against JS & Python and rapid iteration speeds. That's obviously not "serious systems work" whe
109.
▲
by
kllrnohj
5mo ago
> that will let me iterate at the speed of JS or Python with performance of C or Rust. Didn't Go already do that? > I am so used to thinking that Zig, Rust, and the likes are only viable in niches where C is viable, but no. not a
110.
▲
by
kllrnohj
5mo ago
> The fact of the matter is one of the biggest projects that used Zig thought that the devX was so bad It's unlikely to be just a devex issue. The fact of the matter is that a memory unsafe language is an extremely tough sell today,
111.
▲
by
kllrnohj
5mo ago
so a single 3 year old errata for the n100 that was long since patched?
112.
▲
by
kllrnohj
5mo ago
An iPhone will absolutely draw more than 2.5w under load.
113.
▲
by
kllrnohj
5mo ago
I used Uber for the first time in like 8 years recently, and near as I can tell it's the exact same thing it was. What features are they even adding at all much less that anyone cares about? You ask for a ride to a place, a driver show
114.
▲
by
kllrnohj
5mo ago
> Now they are about 4-5 years behind Intel/AMD. [..] the LA664 almost entirely fixed that issue. I think a big part of performance issues is that they are working domestic 5 to 7nm processes, so a good 5-7 years behind. I'm no
115.
▲
by
kllrnohj
5mo ago
> Of course, like literally every other time this has played out in computing history, the companies focused on price performance will end up with more economic resources, and get to turn the upgrade crank more often and for longer. Eh?
116.
▲
by
kllrnohj
5mo ago
That thumbnail is for grid-size, it's generally 50kb or less in size which ends up being around 300x240 or up to 500x500 on newer codecs. It'll be visibly low-res and blurry until the full size decodes for full screen. Hence why I
117.
▲
by
kllrnohj
5mo ago
> I think that's sufficiently fast. (Keep in mind that a 4k screen is about 8.5mp.) How fast do you want your slideshow to be? A modern iPhone can capture at up to 48MP. If the performance scales linearly with pixel count, that woul
118.
▲
by
kllrnohj
5mo ago
> Why is the NN-only portion almost as fast on an iPhone 17 compared to a V100 when the V100 has 4x the FP throughput? Might have some sequential section or a block size that struggles to fill a V100 or a large chunk of CPU-only work or
119.
▲
by
kllrnohj
5mo ago
I find it very curious that their new image codec did not really compare itself against other image codecs, but instead primarily video codecs pretending to do images. As in, no JPEG or JPEG-XL. 150ms to decode 12mp is also incredibly slo
120.
▲
by
kllrnohj
5mo ago
No, not really. Mythos found 3 CVEs, not 271. https://www.flyingpenguin.com/mythos-mystery-in-mozilla-numb...
More ›