mat_epice

Porkbun has been good to me.

I've used porkbun.com for a bit. I've had no complaints, and at least when I looked initially their prices were pretty good.

I agree that a battery would have been nice. My first thought was that I would like to move this around in my kitchen while I'm doing this and that.

That said, since it's USB-C, it's possible to put a battery pack on it. Cue the third-party ecosystem making a specially shaped battery that can attach to the base (or compatible stand mount with battery for the wall-mounted version).

There are many ways to answer this question. My top answer is that this is an advancement that does not need to be immediately applicable to anything to be valuable. Add this to your list of things that you didn't think could be done and draw inspiration from it.

My second answer: It's portable in the sense that I can fit it in my bag. Do I also want to put a Linux mini-pc in there when I'm already carrying my iPad?

My third answer: This is also a nice demonstration of the ridiculous user space things you can do with driverkit. This can motivate people to do other nice things with other hardware that is more portable, or use Linux drivers with driverkit on their mac mini (say).

I was excited that I may have been able to help, but I just have issues from volumes 36 and 37... Perhaps this is for the best, as it would have deeply fed my pack rat tendencies.

The Cray-1 was measured on 64-bit FLOPS, so you would have to do apples-to-apples (heh). A modern iPhone can do 300 GF of 64-bit, so only 2000x.

The iPhone 4 was probably the first that could beat a Cray-1, and it was by a narrow margin. However, that was only a 32-bit chip. The next year iPhones went 64-bit, and it was all over.

Pretty sure not, especially since it requires 64-bit floating-point, so the GPU cores don't help. #500 right now is 2PF. One Mac won't do anywhere near 20 TF. Google tells me you can get 350GF of DP from one 10-core M4, so you might need 10,000 to get there. Then there's the network...

I read it as a little joke, since both Danish and Americano are named after different countries.

I don't think that adding the feature is the issue here, but instead Google deciding it needs to push an order of magnitude more data and store it on your device. I can understand wanting to at least re-evaluate your use of a tool when that happens.

If you were to install Chrome fresh, what if it was a 4GB+ download from their website? I would at least pause. For reference, a regular offline installer is 140MB.

Sounds like you've jumped to conclusions without reading the whole thing, or are making a disingenuous connection between two very different concepts. Climate impacts (really just energy waste) and "legal" arguments are different parts of this article. The legal part centers around whether they have permission to install this model along with Chrome, and whether they are using deceptive practices related to the model.

"Article 5(3) of Directive 2002/58/EC (the ePrivacy Directive) prohibits the storing of information, or the gaining of access to information already stored, in the terminal equipment of a subscriber or user, without the user's prior, freely-given, specific, informed, and unambiguous consent, except where strictly necessary for the provision of an information-society service explicitly requested by the user..."

That is not about climate.

The article goes on to say that there would not be a legal issue if Google simply asked, documented, not taken initial action without user approval, allow deletion, etc. Also not about climate.

What they do imply is that Google's being dishonest if they say that they are carbon neutral (as is often said in their Environmental, Social, and Governance reports) while imposing up to 250 GWh of power use on network providers and end users. I can see the concern.

Sure, AI tools can do this. However, VS Code is the platform. Why aren't more people worried about running arbitrary VS Code extension that can do the same thing, AI or not?