I have had nothing but issues with HDMI. Doing development and trying to integrate HDMI into a hardware design. Everything should just be Display Port. No question. It is a racket.
Readit Newstkuraku commented on Valve: HDMI Forum Continues to Block HDMI 2.1 for Linux heise.de/en/news/Valve-HD... · Posted by u/OsrsNeedsf2P
tkuraku commented on Peanut allergies have plummeted in children nytimes.com/2025/10/20/we... · Posted by u/JumpCrisscross
My son has a peanut allergy. He was deemed very severe. He started treatment daily peanut doses. Starting at 5 mg. He is now eating 4 peanuts a day and counting. Zero issues with exposure now. If you have a kid with a peanut allergy find an allergist who will desensitize them.see https://www.palforzia.com/
tkuraku commented on Fast Fourier Transforms Part 1: Cooley-Tukey connorboyle.io/2025/09/11... · Posted by u/signa11
For FFTW the showstopper was GPL license. For IPP, 200 MB of binary dependencies, also I remember when Intel was caught testing for Intel CPUs specifically in their runtime libraries instead or CPUID feature bits, deliberately crippling performance on AMD CPUs. I literally don’t have any Intel CPUs left in this house. For cuFFT, the issue is vendor lock-in to nVidia.
And the problem is IMO too small to justify large dependencies. I only needed like 200×400 FFT as a minor component of a larger software.
It would be interesting to see how it compares to https://gitlab.mpcdf.mpg.de/mtr/pocketfft. The c++ branch is header only. I believe this is what scipy uses by default
I think you just pick a problem you want to solve with gpu programming and go for it. Learning what you need along the way. Nvidia blog posts are great for learning things along the way such as https://devblogs.nvidia.com/cuda-pro-tip-write-flexible-kern...
> Going from MATLAB to NumPy I felt like I suddenly became a mediocre programmer, spending less time on math and more time on "performance engineering" of just trying to figure out how to use NumPy right.
Matlab is about as slow without readily vectorized operations as Python.
Slowness of Python is a huge pain point, and Julia has a clear advantage here. Sadly Julia is practically just unusable beyond quite niche purposes.
Python does now have quite serviceable jit hacks that let one escape vectorization tricks, but they are still hacks and performant Python alternative would be very welcome. Sadly there aren't any.
I've found matlabs's JIT to be about on par with numba for loops.
Lots of US houses have coax to all the main rooms (family, bedrooms) because that was how you got cable TV.
(I still see it in new construction, though if I was having a build done I'd say run multiple Ethernet instead of any coax)
I'm just building a new house this year and Ethernet to every room is standard in this area. In a different state in the US coax is standard in new construction. (We just moved) It varies by location.
tkuraku commented on TeX and Typst: Layout Models (2024) laurmaedje.github.io/post... · Posted by u/fngjdflmdflg
> I think one of the best ways to overcome the enormous momentum of TeX is to point out its limitations (while still keeping an eye on Typst's limitations), and explain how Typst overcomes them.
One of the other easy ways to overcome it is to provide as many templates as possible for journals. I’ve used LaTeX for years, but would by no means consider myself an expert in LaTeX, as I’ve almost exclusively been able to grab a template from a journal or from my university, and then just draft in the relevant blocks, write equations, add figures, and, rarely, add a package. I would guess that there are a huge amount of LaTeX users like me out there. I do all my drafting on Overleaf. I love TeX (and curse my PI whenever he requires that we use Word/365 instead of LaTeX/Overleaf)… but so much of the benefit, for me at least, comes from the fact that templates are readily available for any journal I would want to submit to; my masters thesis was built in a template provided by my university; etc. I don’t have to deal with any of the cognitive overhead of styling and formatting (except for flowing the occasional figure) and can just focus on drafting.
For me to even consider typst, it’s pretty much a requirement that there is some degree of template parity actively being worked on. The most natural way to approach that would be to just sort every journal by impact factor and start working top to bottom; given that so many journals share templates due to being within elsevier, springer etc, it should be straightforward to reach a reasonable degree of parity relatively quickly.
Getting the major publishers to support and offer their Typst templates would make me try it out immediately for what it’s worth.
This is exactly right. I like latex not because it's super ergonomic, but if I use a template I don't have to think about any formatting.
tkuraku commented on Residential Networking over Telephone computer.rip/2025-02-02-r... · Posted by u/zdw
It's tangential to the topic (though mentioned in the article towards the end) so I'll be lazy and ask the crowd here: What's the current state of the art in powerline networking?
I have an application to network a couple of outbuildings. I don't have tremendous bandwidth needs (1Gbps would be glorious, 100Mbps would be fine). I would prefer wired connections for reliability and privacy. I would prefer not to trench and run fiber. The outbuildings already have electrical service from a central panel. Powerline networking might be a good fit.
There's a lot of consumer stuff out there. I'd like something a little more geared toward an industrial, commercial, or service provider use. (Analogously, think of the difference between using a dumb Netgear switch versus a managed name-brand managed switch.)
Edit: I appreciate the feedback I'm hearing here. This is exactly the kind of stuff I wanted to hear. Sorry to hijack HN for my personal needs like this!
I know you wanted wired, but a point to point wireless link might be a good fit. https://store.ui.com/us/en/products/ubb