Hacker Newsnew | past | comments | ask | show | jobs | submit | hackernudes's commentslogin

I'm guessing this is here because it was featured on an episode of Beef Season 2 from Netflix.

TMCH = Trademark Clearinghouse

Maybe we can synthesize large amounts of limited information. I thought that new training data is mostly synthetic anyway.

That is part of the plot of the TV show "Mr. Robot". Not just the loans, but balances too!

Why would you assume they physically walk around the entire space instead of teleporting/moving in VR?

> Do you partition the previews?

Also discussed here https://news.ycombinator.com/item?id=44381838 from June 2025.


Quantenna used 1.1.1.1 for RPC to their wifi chip in their SDK by default. Should not have been exposed to global routing but of course people screwed that up.

https://medium.com/@mrtcve/atts-misuse-of-cloudflare-dns-ip-...


I don't think there was ever a design to be one frame behind.

Compositing requires the GPU to do some extra work to draw the frame to be presented. This typically takes very little time (much less than a full frame period). Additionally, most wayland compositors will bypass that extra step if an application is full screen (wlroots calls it "direct scanout").

Also some wayland compositors keep track of timing and delay the final composition until right before it is time to present the frame in order to reduce latency.


And for the complete picture, X is predominantly used with a compositor, so that same extra latency exists there as well.


It's generally a single checkbox to turn off compositing in X11, for precisely this reason.


Yes, but the same is true in Wayland and it's automatic as well. Full screen applications don't require compositing so they typically don't, and this was the case in MOST X11 compositors as well.

Turning off compositing before launching a game is maybe a bit misguided, sort of like turning on the "classic theme" in Windows 7 before launching a game. It might save some memory, sure, but latency should be identical.


> latency should be identical

Should be, but very clearly isn't.


The results show it's identical. Only XWayland suffered any significant degradation, and even then we're talking <5ms which is imperceptible.


Those results depend on having a 500hz monitor. There's a world of difference between a mildly-buggy rendering loop's 1-frame delay or missing a vsync deadline causing a 2ms delay vs a 16ms delay.


You can also disable compositing conditionally in KDE, such as when a game window is opened.


Not in Wayland, the whole point of Wayland is to make stuff the X server + compositor + various other bits into the window manager.


For full-screen applications, Wayland has a protocol to let it display frames at its own pace - meant mostly for games for this very reason.


With X11, you can disable composition for windowed apps as well.


I am tickled that OOM can mean "out of memory" in another context. You clearly meant "orders of magnitude".


Heh, unintentional. Another term shorter than spelling out "orders of magnitude" is "decades", but I figure that's less familiar and even more confusing here. "Memory price started out falling two decades per decade..."


Well if you underestimate your memory requirements by orders of magnitude you'll be out of memory for sure.


Probably only used the floppy to boot into a ramdisk.


Exactly.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: