Readit News logoReadit News
paholg commented on Sick of smart TVs? Here are your best options   arstechnica.com/gadgets/2... · Posted by u/fleahunter
MegaDeKay · 2 months ago
Not really. That same link talks about how Intel and nvidia drivers can provide HDMI 2.1 on Linux but it is via their non-free firmware blob.

AMD doesn't (can't? won't?) do the same but there is a workaround: a DisplayPort to HDMI adapter using a particular chip running hacked firmware. That'll get you 4K 120 Hz with working FreeSync VRR.

https://forum.level1techs.com/t/it-is-possible-to-4k-120-hdr...

paholg · 2 months ago
Some of us would like our expensive hardware to work without hacked third party dongles.
paholg commented on Bird flu viruses are resistant to fever, making them a major threat to humans   medicalxpress.com/news/20... · Posted by u/bikenaga
pengaru · 3 months ago
> Can we simply remove fever and coughing somehow… super annoying and more dangerous than the virus themselves sometimes.

You're basically asking to become a bat

paholg · 3 months ago
So we can also fly? Sign me up!
paholg commented on We reduced a container image from 800GB to 2GB   sealos.io/blog/reduce-con... · Posted by u/untrimmed
zatkin · 3 months ago
272 layers in a single image seems really unusual, is that just due to my lack of experience with containers? I've never seen an image with more than maybe a few dozen in my career...
paholg · 3 months ago
You can build docker images with nix, in which case you can have every dependency be its own layer.

That is clearly not what these people are doing, though.

paholg commented on Crossfire: High-performance lockless spsc/mpsc/mpmc channels for Rust   github.com/frostyplanet/c... · Posted by u/0x1997
enricozb · 3 months ago
When reading this project's wiki [0], it mentions that Kanal (another channel implementation) uses an optimization that "makes [the] async API not cancellation-safe". I wonder if this is the same / related issue to the recent HN thread on "future lock" [1]. I hadn't heard of this cancellation safety issue prior to that other HN thread.

[0]: https://github.com/frostyplanet/crossfire-rs/wiki#kanal [1]: https://news.ycombinator.com/item?id=45774086

paholg · 3 months ago
Futurelock is not about cancellation safety (cancellation is actually one solution to futurelock), though the related issues that are linked in that post are.
paholg commented on Why I code as a CTO   assembled.com/blog/why-i-... · Posted by u/johnjwang
dangoodmanUT · 4 months ago
It seems like you're confusing technical founder CTO at a startup with professional CTO at a large org.

For the later, what you said makes some sense, and it definitely seems like you're more familiar with this archetype.

For the former, the article appears correct. If you've not worked at an early stage startup before, the culture is _very_ different.

As a side note: This article is doing it's job. People that are a good fit for the company will agree, and want to work with them. People that are not a good fit for the company will not agree, and naturally run the other way. Makes filtering out candidates easier.

paholg · 4 months ago
At an early stage startup, shipping a feature should not require "many meetings across product, legal, and engineering". Especially not one that can be mostly built in a day.
paholg commented on J-Link Compact USB-C Issues   alvarop.com/2025/09/j-lin... · Posted by u/worik
userbinator · 5 months ago
This means there’s a small microcontroller inside the cable with information on the cable’s capabilities.

More evidence that USB-C is an insanely overengineered spec. Cables should be dumb pipes, not devices with their own active circuitry. IMHO Ethernet, while not perfect, got this part right.

The only reason the signals don’t exactly match the one above is just the orientation of the cable.

This is one of the more perplexing design decisions. Was simply mirroring the contacts too simple for them? Did someone imagine a use-case where they wanted to detect the orientation of the cable? WTF.

paholg · 5 months ago
Ethernet doesn't support 240 W.

I am very happy that I can charge my phone and laptop from the same charger, and don't ever have to worry about whether the cable I'm using will be a fire hazard.

paholg commented on When I say “alphabetical order”, I mean “alphabetical order”   sebastiano.tronto.net/blo... · Posted by u/sebtron
paholg · 5 months ago
I think the real issue here is that two Android phones take photos with incompatible naming schemes.

I am sure that at some point someone thought the milliseconds should or should not be separated from the seconds and made that change without thinking through the consequences.

paholg commented on Zoxide: A Better CD Command   github.com/ajeetdsouza/zo... · Posted by u/gasull
mrcarrot · 5 months ago
Yeah, I've been trying it recently and I'm not entirely convinced I want to keep using it.

My biggest annoyance at the moment (and this may be me missing something), is that I have two directories: "thing" and "thing-api". I'm doing work in "thing" much more often than in the "thing-api", but whenever I run "z thing", it takes me to "thing-api" first, and I have to "z thing" again to get to where I wanted to go. It ends up being more effort than if I'd just tab-completed or history searched a plain cd command.

paholg · 5 months ago
zoxide stores a rank for each directory based on how often you visit it, but you can manually adjust the scores.

Run `zoxide query -ls thing` to see the scores, and `zoxide add thing -s AMOUNT` to increase the score.

paholg commented on Asahi Linux lead developer Hector Martin resigns from Linux kernel   lkml.org/lkml/2025/2/7/9... · Posted by u/Mond_
CopperWing · a year ago
The DMA subsystem maintainer has some reasons: at this time you can disable all rust drivers when building the Linux kernel but you cannot disable rust wrappers to C language APIs. So if you need to change for example the DMA APIs, you also need to fix the rust wrapper before submitting the C patches otherwise you cannot even build a C only kernel.
paholg · a year ago
I don't think that's true. I have seen R4L folks reiterate time and again that C changes are allowed to break Rust code, and they will be the ones to fix it.

u/paholg

KarmaCake day392July 3, 2017
About
[ my public key: https://keybase.io/paho; my proof: https://keybase.io/paho/sigs/o9yHMvmMOPfwkKqOGiymsDtB9qOquhKlK4uD82lb_PA ]
View Original