Love the image of mathematicians laboring over flasks and test tubes, mixing things and extracting numbers... would have far more explosions than day-to-day mathematics usually does...
That aspect makes it kind of a massively parallel "startup name or fantasy sword" challenge, once you get past the obvious ones (whether that helps or hinders I wouldn't claim either way, but it rhymes?)
Nice afternoon of puzzling, thanks for sharing it. (The one feature I could have used was either dragging items around - maybe only already-grouped ones - or the ability to pop back to the one that got merged, since I'd noticed something in the neighbors but had to pick only one of them :-)
(minor spoiler) Fess up, how many of you tried to figure out if "Google Lips" was ever a thing? :-)
This sounds a lot like the classic "the way to get a good answer on the internet is to post a wrong answer first", but in reverse - the AI gives you a bad version which trolls you into digging in and giving the right answer :-)
When I went from a 2006 mini to a 2021 polestar 2, there were a bunch of things that were either "up in class" or "15 years makes things better" - traction control, non-invasive lane-assist (with invasive options), per-driver (per-keyfob really) seat adjustment memory, charge-aware navigation, radar cruise-control, 360° camera fusion, headlight washers, kick-to-open trunk, interior pre-warm (including seats, as a software upgrade), smart (camera-based) auto-dim of high beams, mirror-retract when parked, mirror tilt when backing up, retractable trailer hitch... little of this is structural, it's just an accumulation of details and attention paid to them.
And a few downgrades (if my 2023 Polestar 2 is an indication)
* Wait 60 seconds to start using the GPS / nav to become responsive
* Unreliable backup camera (even after several software "fixes")
* No buttons or knobs for climate control
* No way to disable intrusive line detection that makes car vibrate when you get close to yellow and white lines
* Overzealous auto-dim of high beams (our 2023 Mazda CX-5 is significantly better with almost no false positives)
It's not all bad, and once the infotainment warms up, it's plenty responsive. It's certainly a luxury car though (as an admitted Mazda fan) you can get a lot of nice from a $30k Mazda.
Yup. It's certainly an art project or something. It's like setting a bunch of Markov Chaneys loose on each other to see how insane they go.
…kind of IS setting a bunch of Markov Chaneys loose on each other, and that's pretty much it. We've just never had Chaneys this complicated before. People are watching the sparks, eating popcorn, rooting for MechaHitler.
Yeah, staff engineer is a pinnacle "still doing engineering and maybe leadership but not management" position in engineering firms. The academic "staff" is just a "not really one of us" gatekeeping-the-servants title.
Probably either (1) they don't request another jpeg until they have the previous one on-screen (so everything is completely serialized and there are no frames "in-flight" ever) (2) they're doing a fresh GET for each and getting a new connection anyway (unless that kind of thing is pipelined these days? in which case it still falls back to (1) above.)
You can still get this backpressure properly even if you're doing it push-style. The TCP socket will eventually fill up its buffer and start blocking your writes. When that happens, you stop encoding new frames until the socket is able to send again.
You probably won't get acceptable latency this way since you have no control over buffer sizes on all the boxes between you and the receiver. Buffer bloat is a real problem. That said, yeah if you're getting 30-45 seconds behind at 40 Mbps you've probably got a fair bit of sender-side buffering happening.
> you have no control over buffer sizes on all the boxes between you and the receiver
You certainly do; the amount of data buffered can never be larger than the actual number of bytes you've sent out. Bufferbloat happens when you send too much stuff at once and nothing (typically the candidate to do so would be either the congestion window or some intermediate buffer) stops it from piling up in an intermediate buffer. If you just send less from userspace in the first place (which isn't a good thing to do for e.g. a typical web server, but _can_ be for this kind of video conference-like application), it can't pile up anywhere.
(You could argue that strictly speaking, you have no control over the _buffer_ sizes, but that doesn't matter in practice if you're bounding the _buffered data_ sizes.)
Love the image of mathematicians laboring over flasks and test tubes, mixing things and extracting numbers... would have far more explosions than day-to-day mathematics usually does...
reply