Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kllrnohj
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
36 ms
·
541.
▲
by
kllrnohj
2y ago
> For non AI uses the 5080 is infinitely better positioned ...and also slower than a 4090. Only the 5090 got a gen/gen upgrade in shader counts. Will have to wait for benchmarks of course, but the rest of the 5xxx lineup looks like
542.
▲
by
kllrnohj
2y ago
it's actually a lot worse than it sounds even. The 5070 is like a 4090 is when the 5070 has multi frame generation on and the 4090 doesn't. So it's not even comparable levels of DLSS, the 5070 is hallucinating 2x+ more frames
543.
▲
by
kllrnohj
2y ago
You can also save tons of money by combining used GPUs from two generations ago with a patientgamer lifestyle without needing to resort to suffering 30fps
544.
▲
by
kllrnohj
2y ago
I mean I can get a Snapdragon X Elite laptop for $1200 that'll have a faster CPU than the one in the Digits, too...
545.
▲
by
kllrnohj
2y ago
> Case in point Cyberpunk and Indiana Jones with path tracing don't get anywhere near 100FPS with native resolution. Cyberpunk native 4k + path tracing gets sub-20fps on a 4090 for anyone unfamiliar with how demanding this is. Nvidi
546.
▲
by
kllrnohj
2y ago
> but I do wonder how much fundamental rasterisation + shaders performance gain there is in this generation in practice on the majority of actual games. likely 10-30% going off of both the cuda core specs (nearly unchanged gen/gen f
547.
▲
by
kllrnohj
2y ago
> It’s 3 extrapolated frames not interpolated. So would be reduced lag at the expense of greater pop-in. it's certainly not reduced lag relative to native rendering. It might be reduced relative to dlss3 frame gen though.
548.
▲
by
kllrnohj
2y ago
It's a dual flow-through design, so some SFF cases will work OK but the typical sandwich style ones probably won't even though it'll physically fit
549.
▲
by
kllrnohj
2y ago
> There are plenty of AAA games released last years that you can do 4K at 60fps with a RTX 3090 for example. Not when you turn on ray tracing. Also 60fps is pretty low, certainly isn't "high fps" anyway
550.
▲
by
kllrnohj
2y ago
> At $3,000, it will be considerably cheaper than alternatives available today $3000 gets me a 64-core Altra Q64-22 from a major-enough SI today: https://system76.com/desktops/thelio-astra-a1-n1/configure And o
551.
▲
by
kllrnohj
2y ago
Bullshit. Overturning decades old decisions is activism, plain and simple. He's taking a steaming dump all over the very idea of precedent and star decisis, it sure as hell isn't his philosophy to maintain it. If it was then Roe v
552.
▲
by
kllrnohj
2y ago
You kinda said it yourself already - ctags is fast because it's producing almost nothing of value. Being fast at doing nothing isn't impressive. Try doing the same with C++ and more indexing options enabled, such as with something
553.
▲
by
kllrnohj
2y ago
There's approximately a 0% chance of Zig seeing non-trivial adoption anywhere other than maybe the embedded world. It otherwise solves basically nobodies problems in the real world and is just a love letter to C. It's cute, kinda,
554.
▲
by
kllrnohj
2y ago
> Noticing the error, and being affected by the error, are two entirely different things. Only somewhat true. Take any consumer usage here for example. If you're playing a game and it hits this incorrect output but you don't no
555.
▲
by
kllrnohj
2y ago
if anyone else had done this then yes probably it's reasonable feature done reasonably. The problem is Apple has spent tens if not hundreds of millions of dollars advertising that they don't do things like this. That stuff stays o
556.
▲
by
kllrnohj
2y ago
> Investment of cash without profits to make those investments is still a burn… there was, though? That's why net income averaged zero, and cash on hand is flat the last 4 years. He didn't run Intel at a loss.
557.
▲
by
kllrnohj
2y ago
> but in 3.5 years couldn't do the actual goal ...which means he was allowed to release maybe 1 if even that of Intel's bread and butter, CPUs. They have a lead time of somewhere between 3-5 years. And that's not including
558.
▲
by
kllrnohj
2y ago
> You need extra code on the happy path to collect context in case of an exception Again, provide an actual example please. C++ exception context handling is generated at compile time and is in a secondary, cold stack. It's unclear
559.
▲
by
kllrnohj
2y ago
> exceptions don't provide any benefit over simply returning NULL. Sure they do - they don't negatively impact the non-error case and don't pollute every function's return value.
560.
▲
by
kllrnohj
2y ago
Can you provide an example of that on godbolt or similar? In what scenarios do exceptions introduce the claimed cost? The only thing I could see is just the density of code could mean more page spills and less efficient cache line usage for
561.
▲
by
kllrnohj
2y ago
> They have a significant cost to program size and performance even if they are never used. They do have a cost to program size, yes, but they have ~zero impact on performance when never used. They are completely cold, outside of normal
562.
▲
by
kllrnohj
2y ago
> At the limit limit, there is no difference between Result<T,E> and checked exceptions How do you figure? A Result<T,E> always means a branch after function calls, while checked exceptions have no such cost. Toy example: ht
563.
▲
by
kllrnohj
2y ago
What optimizations are disabled? I don't see any reason any of them would be, nor is there any bookkeeping. The stack itself is the bookkeeping which is required regardless. The exception-specific stuff is stored elsewhere, which is wh
564.
▲
by
kllrnohj
2y ago
Look at the error rates they are testing. A 0.1% exception rate, which is certainly something that'd be "rare", starts to happen an awful lot when you have a program that's using 128 cores, and 5th generation Epyc can pu
565.
▲
by
kllrnohj
2y ago
You can't really "optimize" that every function call now has a branch after it to check for an error. That's a design choice Zig made at the cost of performance, which is not inherently bad. After all, lots of languages
566.
▲
by
kllrnohj
2y ago
Because they are just better for the actual rare issue. Consider for example out of memory. "proper" error handling via return values would mean everything that allocates memory has to have an error return path and everything th
567.
▲
by
kllrnohj
2y ago
> I'm not sure what other Android-using company would want to take that on, though. Meta uses Android for the Quest. Will Meta adopt Android XR instead of maintaining their own Android fork? Possibly, possibly not. But they are defi
568.
▲
by
kllrnohj
2y ago
> Chess is different from sports in only one way: the loss of very intelligent capable people who could be helping to create the future. Being good at chess does not mean you're "very intelligent". Most of the top players
569.
▲
by
kllrnohj
2y ago
Not necessarily. If that "only move" is obvious, then it's not really risky. Like if a queen trade is offered and the opponent accepts, then typically the "only move" that doesn't massively lose is to capture b
570.
▲
by
kllrnohj
2y ago
bool foo(some_struct* bar) { if (bar->blah()) { return true; } if (bar == nullptr) { return false; } return true; } Can the compiler eliminate that nullptr com
More ›