Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
arghwhat
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
36 ms
·
631.
▲
by
arghwhat
2y ago
If only the headline came with a blog post that provided details… For the lazy, it’s a few conditional jumps changed to unconditional jumps.
632.
▲
by
arghwhat
2y ago
> https://www.trevormarshall.com/ should be a good _starting_ point. That's not a starting point, that's just his web page. Works that were relevant would be e.g. specific papers on the topic that gained tracti
633.
▲
by
arghwhat
2y ago
Note that RF does not make everything oscillate violently - the energy is dissipated by inducing spin in water molecules, leaving little energy to budge huge macro structures like enzymes. Enzymatic oscillations are also to my knowledge on
634.
▲
by
arghwhat
2y ago
I mean, the only caveats of multithreading (apart from bugs) is whether you can obtain full linear scaling or if your data structures require synchronization to the point of becoming bottle-necks. In case of a database, the majority of the
635.
▲
by
arghwhat
2y ago
It's not really reliance on wheels, but reduction of all mechanical work as one then goes to sit at a desk. Walking a 60km commute every day wouldn't be good for your knees either though. > will lead to bone density loss and
636.
▲
by
arghwhat
2y ago
Unless the topic is how TikTok can cause hemorrhoids from sitting too long on the can, I imagine the topic is specifically the effect of radio waves in the cellular bands on nervous tissue, not the general concept of mobile phones on gene
637.
▲
by
arghwhat
2y ago
This triggers connected screens to wake up despite no signal every time it does it. Unfortunately you cannot disable it on Apple silicon Mac’s…
638.
▲
by
arghwhat
2y ago
Apologies, I have to nitpick: Of course they can't both believe one thing and the opposite at the same time. Now, believing something with zero supporting evidence or arguments, and plenty against it, is of course silly - but you still
639.
▲
by
arghwhat
2y ago
On the side of sensible caution when presented with unknown factors, yes. That does not apply when there is neither practical evidence nor any room for justified suspicion. At that point it might at best be silly, even if not harmful. Depen
640.
▲
by
arghwhat
2y ago
What’s wrong with the gdb and lldb integration in all the various IDE’s? The various screenshots of RemedyBG doesn’t seem to suggest anything special.
641.
▲
by
arghwhat
2y ago
Empty barrels make the most noise. It’s cheap to be vocal about a topic, whereas donating time or money to the cause is not.
642.
▲
by
arghwhat
2y ago
I was just pointing out specifically that there is no such thing as PCIe-based video - nor is there any need for that. Support for USB4/Thunderbolt DP will proliferate, but there is still benefit to a DP altmode as it's free to im
643.
▲
by
arghwhat
2y ago
> and lastly there is some trend to PCIe everything in both consumer and server hardware. In the consumer segment it had been somewhat limited to the "luxury" segment, i.e. Thunderbolt. But with USB4 it slowly ends up in more a
644.
▲
by
arghwhat
2y ago
Heh, good point, USB 2.0 would absolutely suffice. You'd hardly need more than a standard audio profile either. Some TVs even support this already - recent Samsung models at least. A specialized port could theoretically have a lower
645.
▲
by
arghwhat
2y ago
You’d be surprised by the number of users who are satisfied with the built-in media experience. I’d say it’s most likely a large majority. Google TV is common, but people with an Android-powered TV are not the main target for those until th
646.
▲
by
arghwhat
2y ago
> At any rate, for some reason DisplayPort has just not caught on all that much. DisplayPort won everything, except not becoming the physical connector for home cinema. Heck, even within those HDMI-exposing devices, DP won. The vast ma
647.
▲
by
arghwhat
2y ago
In that case you’re at risk no matter what you do.
648.
▲
by
arghwhat
2y ago
JPEG at 100% quality makes very little sense - the goal is to dial it down to the lowest value where artifacts are still low enough to not notice. AVIF also has much better behavior in the artifact department, letting you go much lower with
649.
▲
by
arghwhat
2y ago
Luckily we do not have to rely on opinion. Take this 1204x800 real-world photo which is less than 80KB: https://raw.githubusercontent.com/link-u/avif-sample-images/... That's slightly less than half the heigh
650.
▲
by
arghwhat
2y ago
They should just be made properly - a properly made PDF is less than a megabyte, and model pictures should be just hundreds of KB. Takes a lot of models and instructions to burn hundreds of megs that way.
651.
▲
by
arghwhat
2y ago
To use the cache you shouldn’t need to do any of this - just have appropriate cache headers.
652.
▲
by
arghwhat
2y ago
Caching is free up until a service ceiling - certain file types and sizes are excluded in the free tier for example.
653.
▲
by
arghwhat
2y ago
Hmm? Pretending the page size is larger than it is would not yield the primary performance benefits of reduced TLB misses. Unless I am missing something, that seems more like a hack to save a tiny bit of kernel memory on a constrained syste
654.
▲
by
arghwhat
2y ago
Quite a bit, but 2M is an annoying size and the transparent handling is suboptimal. Without userspace cooperating, the kernel might end up having to split the pages at random due to an unfortunate unaligned munmap/madvise from an appli
655.
▲
by
arghwhat
2y ago
A more relevant bit of background is that 4KB pages lead to quite a lot of overhead due to the sheer number of mappings needing to be configured and cached. Using larger pages reduce overhead, in particular TLB misses as fewer entries are n
656.
▲
by
arghwhat
2y ago
> Also, large corps get SOC2, yet they are still not secure. SOC2/ISO27001 audits are just "are you living up to the processes you defined yourself for SOC2 compliance", not "are you secure". It is dealt with by
657.
▲
by
arghwhat
2y ago
Average Joe and businesses alike will assume that a tool telling them their site is secure means that they don't have to worry much about it. A tool that can easily be made to report "100% secure" is then quite harmful. Even
658.
▲
by
arghwhat
2y ago
> I don't agree with OP about I/O-bound ops, I think if you're looking to green threading, you've taken a wrong It depends in the implementation. In Go for example, all I/O is async and suspend your green thread,
659.
▲
by
arghwhat
2y ago
For web, my favorite is JIT miscompilations. A tie between a mobile Safari bug that caused basic math operations to return 0 regardless of input values (basic, positive Numbers, no shenanigans), or a mobile Samsung browser bug where concate
660.
▲
by
arghwhat
2y ago
I don't mind them having AI features, but I wish they'd fix some of the most basic performance issues considering that their entire reason to exist was "performance". You know, things like not rerendering the entire UI o
More ›