cibyr

And Altavista was slow! Google was so much faster, it felt way nicer to use. But LLMs are slow; forcing my google queries through an LLM is destroying that speed.

It remains to be seen what they actually end up selling for, but it seems like Slate intend to offer a 200 hp motor, 52 kWh battery ... and the rest of a whole vehicle for $28k. That makes $27k for this "eCrate" package (which, granted, comes with 14 kWh more battery) seem like an absolutely terrible price.

Apple TV

People fight about tab sizes all the time though.

Sometimes I wonder if the throat-clearing is an indispensable part of getting to the "good bits" that follow. Like, do those extra tokens give it more "room to think" even if they're basically meaningless in themselves?

It seems to me that the distinction becomes irrelevant as soon as you connect inputs and outputs to the real world. You wouldn't say that a 737 autopilot can never, ever fly a real jet and yet it behaves exactly the same whether it's up in the sky or hooked up to recorded/simulated signals on a test bench.

I'm sure it's fine you do it properly ([1] for example). The issue here was the utter lack of engineering, not the specific manufacturing technique (although those do seem to be highly correlated, due to low-end 3D printing having become very cheap and easy).

[1] https://www.youtube.com/watch?v=rV74KhPNg1w

The extra fun thing about this is that eval has different semantics if it's assigned to a different name, in order to allow JavaScript implementations to apply extra optimizations to code that doesn't call a function literally named "eval": https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

Andy Wingo (of course!) has a good explanation of this: https://wingolog.org/archives/2012/01/12/javascript-eval-con...

My "will not bailout AI companies" t-shirt has people asking a lot of questions already answered by my shirt.

What does the word "material" in "material support" mean if advocacy counts?

The "scraping helped slow it down" theory makes no sense to me. What do you think has a higher coefficient of friction - tire rubber on asphalt, metal on asphalt, or metal on metal?

Good thing the current supreme court has such respect for precedent!

One might even say they have chutzpah.

Do any of the major airlines have a software stack that isn't a legacy nightmare?

"built to the highest Microsoft standards of security, privacy and performance" seems perhaps importantly different from "but to the highest standards".

Similar concept, though an important distinction: QFTF assumes that you have a phone you can scan QR codes with, but that isn't where you want the file to end up. Instead, it displays a QR code on both the sender and the receiver, and you scan both of the QR codes with your phone to start the transfer.

I've been working on a little utility to transfer files between two computers using QR codes: https://github.com/cibyr/qftf

It's kinda like Magic Wormhole without typing. It uses iroh for the p2p networking - on both ends, and also in the little web app that you use to scan the QR codes and start the transfer.

So many autoplaying videos on the page, and none of them are the video that the article is about.

Imgur is particularly infuriating because it was initially touted as an alternative to the shitty image-sharing sites of the day (photobucket and the like) - one that would let you just link to an image without any bullshit. Now it's completely unusable.

Zig's claims of memory safety are a bad joke. Sure, it's easier to avoid memory safety bugs in Zig than it is in C, but that's also true of C++ (which nobody claims is a memory safe language).

Can a C program be memory safe as long as it doesn't have any relevant bugs? Yes, and you can even prove this about some C programs using tools like CBMC.

What's the alternative though? If you're fine with garbage collection, just use garbage collection. If you're _not_ fine with garbage collection (because you want deterministic performance, or you have resources that aren't just memory) then Rust's borrow checker seems like the best thing going.

I think rdrd just missed that piece of the fine wordsmithing - so long as there's at least one person not included in that "some users", then "we don’t keep logs of who EVERYONE is messaging" is still true.

I really wanted a Palm Pre back in the day, but they initially didn't offer them at all outside of the US, and later only in a handful of other countries. It seemed like they weren't even trying. The tablet saw wider distribution, but it was a joke - nobody was going to pay iPad prices for a plastic piece of crap.

It's so depressing to hear that congress can't even do small things that everyone agrees upon.

ClusterFuzz: https://google.github.io/clusterfuzz/

The self-service unpause is brilliant. The worst thing about hitting these sorts of limits is that time window when you think you've fixed the problem but you can't check because you're throttled - so there's nothing you can do but wait. Giving literally any affordance so that a human can make progress with a fix removes this huge source of frustration.

Also that Python has successfully transitioned its community to Python 3, while Perl 6 flamed out, changed its name, and left the Perl community slowly atrophying.

Anyhow warrants more than an honorable mention, IMO. anyhow::Context is great, and basically always an improvement over unwrap() - whatever complaints you might have about anyhow::Error, it's infinitely easier to handle than a panic.

The threat is not exactly zero. In some cases, thieves can get physical access to the bus from outside the car, and then inject messages to unlock it, start the engine, and drive away: https://kentindell.github.io/2023/04/03/can-injection/

Sure someone in that situation could also "just cut brakes or put in a pipe bomb" but car theft is a lot more common than assassination, at least where I live.