HNHacker News
TopNewBestAskShowJobs

tuetuopay

1,764 karma · joined December 23, 2021

submissionscomments
tuetuopay··on Ubiquiti SFP Wizard
Yup, that's pretty nice. I sold a couple of XXV710s to a friend that moved over there.
tuetuopay··on Our LLM-controlled office robot can't pass butter
their paper explicitly mentions the rick and morty robot as the inspiration for the benchmark
tuetuopay··on Ubiquiti SFP Wizard
> 2.5gbit, 5gbit and 10gbit RJ45 is getting more affordable and more common

Still, compared to the SFP+ gear it's ridiculously overpriced. NICs are <$20 on ebay and an 8x10G port managed switch is $120 on aliexpress.

> Over here in NL we now get more and more access to >1gbps speeds

Same in France, yet the main "geek" ISP (free) has an 8Gbps symmetric ISP router with a 10G SFP+ cage for full bandwidth to the LAN. RJ45 ports are 2.5G.

And it's hard to fault them, as customers that are likely to even hardwire stuff to the router and moreso at 10Gbps are usually enthusiasts that do prefer SFP+ due to the abundance of hardware on the used market. Oh, and their team designing the router are a bunch of nerds that most likely all have a 10Gbps network.

tuetuopay··on Ubiquiti SFP Wizard
Small Form-factor Pluggable, a common optics format for 1 to 25Gbps networks. See the wikipedia page: https://en.wikipedia.org/wiki/Small_Form-factor_Pluggable
tuetuopay··on Ubiquiti SFP Wizard
I've recently had a laugh on a UDM trying to setup IPv6 routing. Somehow, it did not install the default route in the FIB, but the OS was aware of it, so the router was reachable from the outside but did not route packets. I tried adding a route to `::0/0` and it spat at me that a multicast destination was not valid as a route destination. I gave it a route to `::0/1` and it's happily chugging along now. /shrug
tuetuopay··on Ubiquiti SFP Wizard
It's more for enterprise gear than anything. For example, enterprise Cisco gear will absolutely reject non-cisco optics, but datacenter gear won't. As an example, the Nexus 9000 line accepts non-cisco optics by default. Granted, those are 10k+ boxes so somewhat high-end but nowhere near the ASR line.

The nexus line being more modern in spirit also helps. Catalysts still reject non-cisco optics without a configuration line afaik.

A good rule of thumb is whether the equipment tries to vendor-lock you in.

Another example that comes to mind is at least one generation of Intel NICs (don't remember if it's the 5xx or the 7xx), where even the open-source mainline (!) driver will reject the optic without a driver argument passed to it when modprobe'ing it.

tuetuopay··on Go beyond Goroutines: introducing the Reactive paradigm
Sometimes it feels like that Go mistakes readability for comprehendability. Sure, I can read every single line of Go I've ever read. But can I comprehend the bigger picture? Can I understand why? Isn't the actual meat buried under piles of non-abstraction?

This is precisely the premise for their library: I don't have the mental context to fit all the boilerplate in, nor do I have the brainpower to sift through it.

Sure, assembly is readable: every line is one machine instruction. But that's way too many details. On the other hand, C++ templates are not enough details.

tuetuopay··on Life next to 199 data centres
Scaleway DC5 is large by French standards, rather small by US hyperscaler standards. But the main reason is DC5 does not use classic cooling, thus does not have huge dry coolers outside, which definitely helps for noise (it's adiabatic cooling).

Another fact is just the sheer power density of those problematic north virginia datacenters. I'd bet us-east-1 is not an issue (old building and lower power density), but the newer AI ones are. Just take a look at how much AI clusters eat: a single DGX H200 box with 8 GPUs is 10kW. Most facilities provide 10kW for a whole rack, not 8Us. You're looking at 60kW racks, which is a mental power density: a single aisle trivially gets over the MW threshold. You used to feed rooms with megawatts. Heck, DC5 has 24MW of power, that's only 20000 H200 (again, think hyperscaler scale).

Still about cooling, the load profile is even different. DC5 is a general purpose datacenter, where the load is not full blast. Your AI datacenter has the GPU clusters full blast all the time. That's a LOT of power.

I happen to know pretty well the Scaleway infra and visited others of their datacenters. You can stand centimeters from the noise-dampening wall surrounding the dry coolers and not hear a thing; while almost needing noise protection within the wall.

tuetuopay··on 10M people watched a YouTuber shim a lock; the lock company sued him – bad idea
The most absurd thing is the original video response from the company was good, and with a very compelling argument: their customers never saw shimming in the field. Their user base don't need shimming resistance: security needs to be adequate, not perfect. And they follow-up by presenting options about people requiring the lock to be shim-proof.

Granted, in this day and age, it's a disgrace to still make locks that can be shimmed. Especially when the shim-proof alternatives they show just have an additional notch to catch the shim.

tuetuopay··on PCB Edge USB C Connector Library
I've done HDMI edge connectors like this using plain HASL without too much trouble. Just don't forget to remove all soldermask on the connector path, they'll dirty out quickly otherwise.

But, now I do ENIG everywhere because it's often the same price as lead-free HASL (or so close it does not matter), while looking way cooler. I've started to take quite seriously leaded stuff now, especially since low temperature lead-free solder exists (SAC305).

tuetuopay··on /dev/null is an ACID compliant database
> a command outputting an incomplete line without a line terminator is producing garbled non-textual output

I would argue that no, there are many valid cases for commands to not produce a final \n in their output. The first example that come to mind is curl'ing a REST API whose body is a single line of JSON. Many of those will not bother with a final \n, and this does not qualify as "garbled output" in my book. I would even go as far as saying that a shell just printing the prompt at whatever place the cursor happens to be is a side-effect of how terminal emulation works and the fact it's just a character based terminal.

This is actually something that Warp does pretty well, with a strong integration with the shell where your command is in a dedicated text box, by the virtue of it being GUI and leveraging GUIs. (I don't use it however, I'm too much of a sucker for dense UIs).

However I do agree with your argument that it's not the role of the shell to protect you against `cat /dev/urandom` or `cat picture.png`. And fish indeed does not try.

IMHO a shell is built for humans when in interactive mode (one of the raison d'être of fish), and the lack of final \n is such an annoyance that handling this specific edge case is worth it.

tuetuopay··on /dev/null is an ACID compliant database
I don't get why this is still the case on classic shells. fish properly puts the prompt on column zero, while outputting a small "line return arrow" at the end of the command to indicate it lacked one.
tuetuopay··on /dev/null is an ACID compliant database
The only bug with it was due to my own stupidity. I wanted a quick way to see how fast a drive was, thus sending one of its large files to /dev/null was fine. Except I went too fast and cp'd the file to /dev/null.

It took a while before noticing I had no more /dev/null on the machine (read: the time needed to fill the rootfs). In a panic, I removed the file.

Seeing the machine collapse due to /dev/null missing was fun.

tuetuopay··on CPU cache-friendly data structures in Go
Oooh, that's what is happening. I assumed it locked some structure about the thread while touching it, to prevent races with the runtime. That's what I get for not RTFM'ing (in fairness, why Lock and not Pin, when both of these words have pretty well defined meanings in programming?)

Thank you

tuetuopay··on QUIC and the end of TCP sockets
Even on perfect networks HoL blocking is an issue. If the receiving end of a set of stream blocks on one stream, it ends up blocking the whole connection. One stream stops due to backpressure, all streams stop.
tuetuopay··on QUIC and the end of TCP sockets
Even the TCP graph is dubious. Cubic being systematically above the link capacity makes me chuckle. Yes bufferbloat can have cubic "hug" a somewhat higher limit, but it still needs to start under the link capacity.
tuetuopay··on CPU cache-friendly data structures in Go
Overall great article, applicable to other languages too.

I'm curious about the Goroutine pinning though:

    // Pin goroutine to specific CPU
    func PinToCPU(cpuID int) {
        runtime.LockOSThread()
        // ...
        tid := unix.Gettid()
        unix.SchedSetaffinity(tid, &cpuSet)
    }
The way I read this snippet is it pins the go runtime thread that happens to run this goroutine to a cpu, not the goroutine itself. Afaik a goroutine can move from one thread to another, decided by the go scheduler. This obviously has some merits, however without pinning the actual goroutine...
tuetuopay··on The least amount of CSS for a decent looking site (2023)
I don't mind limiting content-width. I do mind the trinity of plz-scroll-to-read-two-words: content-width limiting, bigger fonts, bigger line height.

Most websites abuse the latter two, and makes my mouse wheel spin like a meth addict without a dose.

Please keep the default font size. It's aligned with the system's size, and is precisely what a browser's zoom function will scale.

tuetuopay··on The least amount of CSS for a decent looking site (2023)
Serif is meant to be printed, on paper, with the ridiculous DPI of printers.

These fonts have not been designed for pixelated displays. Yes, it's better on Retina / HiDPI displays (I even enjoy some serif fonts on those), but those have to be designed with pixels in mind. But they usually are atrocious on "classic" pixel densities.

And tangent: the print industry has a much wider typeface selection than "just" Times New Roman, which is rather rare in my personal experience (sample size of one, though).

tuetuopay··on DXGI debugging: Microsoft put me on a list
Until microsoft ships the .arm.exe name in the list. pretty much a ticking time bomb.
tuetuopay··on Apple Photos app corrupts images
Since it looks like a concurrency issue, most likely the new laptop made the issue less frequent through the simple virtue of being faster.
tuetuopay··on EU court rules nuclear energy is clean energy
We’ve had our share of anti-nuclear activists in France. The project got endlessly stalled, with shifting legislative grounds, and general opposition. Also, the general inefficiency and incompetence from Areva meant this was a match made in heaven (or hell, depends) to get nearly infinite delay.
tuetuopay··on Behind the scenes of Bun Install
CICD is a major usage. But dependencies version bumps are also a big part of it. In the python ecosystem I’ve had poetry take minutes to resolve the ansible dependencies after bumping the version. And then you see uv take milliseconds to do a full install from scratch.
tuetuopay··on We should have the ability to run any code we want on hardware we own
Sadly yes. The average joe is not a target for technical exploits that use CVEs. They are, however, targets for meatsack exploits tricking them in installing crap like remote control software.
tuetuopay··on Go is still not good
Thanks, I was not sure, hence the "may". Comment edited :)
tuetuopay··on Go is still not good
Rust has `.inspect()` for iterators, which achieves your printf debugging needs. Granted, it's a bit harder for an actual debugger, but support's quite good for now.
tuetuopay··on Go is still not good
Depending on your iterator implementation (or, lackthere of), the functional boils down to your first example.

For example, Rust iterators are lazily evaluated with early-exits (when filtering data), thus it's your first form but as optimized as possible. OTOH python's map/filter/etc may very well return a full list each time, like with your intermediate. [EDIT] python returns generators, so it's sane.

I would say that any sane language allowing functional-style data manipulation will have them as fast as manual for-loops. (that's why Rust bugs you with .iter()/.collect())

tuetuopay··on Go is still not good
Sorry but for most programming tasks I prefer having actual data containers with features than an HTTP library: Set, Tree, etc types. Those are fundamental CS building blocks yet are absent from the Go standard library. (well, they were added pretty recently, still nowhere near as featureful than std::collection in Rust).

Also, as mentioned by another comment, an HTTP or crypto library can become obsolete _fast_. What about HTTP3? What about post-quantum crypto? What about security fixes? The stdlib is tied to the language version, thus to a language release. Having such code independant allows is to evolve much faster, be leaner, and be more composable. So yes, the library is well maintained, but it's tied to the Go version.

Also, it enables breaking API changes if absolutely needed. I can name two precendents:

- in rust, time APIs in chrono had to be changed a few times, and the Rust maintainers were thankful it was not part of the stdlib, as it allowed massive changes

- otoh, in Go, it was found out that net.Ip has an absolutely atrocious design (it's just an alias for []byte). Tailscale wrote a replacement that's now in a subpackage in net, but the old net.Ip is set in stone. (https://tailscale.com/blog/netaddr-new-ip-type-for-go)

tuetuopay··on Code formatting comes to uv experimentally
Doing a lot of Rust, there is one huge benefit of having cargo handle rustfmt: it knows the fileset you're talking about. It will not blindly format all rust files in the cwd, rather the "current" crate (current having the same definition as cargo!).

Translating this to uv, this will streamline having multiple python packages in the same directory/git repo, and leave e.g. vendored dependencies alone.

Also, since their goal really is "making cargo for python", it will likely support package-scoped ruff config files, instead of begin file- or directory-based.

tuetuopay··on Breaking Git with a carriage return and cloning RCE
Using other languages would likely fix the issue but as a side-effect. Most people would expect a C-vs-Rust comparison so I’ll take Go as an example.

Nobody would write the configuration parsing code by hand, and just use whatever TOML library available at hand for Go. No INI shenanigans, and people would just use any available stricter format (strings must be quoted in TOML).

So yeah, Rust and Go and Python and Java and Node and Ruby and whatnot would not have the bug just by virtue of having a package manager. The actual language is irrelevant.

However, whatever the language, the same hand implementation would have had the exact same bug.

← PreviousPage 8 of 20Next →