p_l

Unless you have good ANC headphones, or find something like pink noise that fits you, you're still dealing with all the talking to microphone of your colleagues.

I wish they supported older gen XDNA though :(

Washing by hand, both dishes and clothes, as well as drying them "old school" are all skills I found very practical to keep even if rarely used (hand washing dishes is pretty common when for me though if I only have one or two items...)

DEC BASIC on VMS even had somewhat common-lisp comparable condition facility thanks to OS support, for those who don't know that means non-unwinding exceptions that allow continuing from where the condition was signaled

The only case that would match for 90dB anywhere outside a datacenter are abominations like the xAI one with ton of barely-legal to straight out illegal (before recent rule change) gas turbines providing power, which is an issue downstream from US grid being utter shit

A lot of estimates used online for datacenter usage at large scale actually calculate water dependency including power generation - to the point that they might include water used by hydropower plants. It does not mean the reports are wrong, the data is simply for specific use that is then misrepresented by people who didn't read deep enough (or who have an agenda)

Agent-shell uses ACP server published through ACP registry here [1] - those are AFAIK used by editor extensions as backend since VScode can't exactly run Go-based extensions - Zed instructions explicitly talk about using ACP Registry too [2]

[1] https://github.com/agentclientprotocol/registry/blob/main/an...

[2] https://antigravity.google/docs/ide/extensions/zed

I am not talking about ACP command flag - there is a separate binary that exists for integration into editors, and it's how VScode extension works. So it's the same usage pattern underneath

It's not - it uses the same interface as editor extensions like the one for VScode.

It does mean however that it cannot operate as flexibly as it it could with raw API, IMO, but agent-shell is essentially designed towards wrapping the official clients

3.5 Pro has been pretty much canceled for few months now, 4.0 was in the works instead

and has explicit "/copy btw" if you want to save it

Arguably gemini-cli was done in similar style, but claims on reasons for switching were about speed and efficiency of the internal jetski tool in comparison (antigravity toolkit wraps jetski code)

agent-shell works with antigravity but I haven't tested it much yet

Not sure what's the problem with phone app rollout, mine has 3.1 Pro, 3.5 Flash-Lite, and 3.8 Flash (with optional extra effort), and pretty much it switched to latest Flash series as main option since 3.5 just after release

3.8 Flash (but also last two ones) have really strong preference for dissecting binaries with quick thrown-together bits of python in my experience.

Including going first for decompiling AGY binary instead of searching the web for documentation...

It's the same issue that cognitive science had for animal intelligence, honestly...

Might be related to NixOS being strongly related to Netherlands and them picking local

SV in 1990s was effect of 60-70 years of hardcore government funding that was not only not stopped, but amplified by WW2 whereas Europe was heavily wrecked by it (UK finally stopped wartime rationing of food in 1954!). In comparison, in 1945 USA was trying to redirect wartime production surplus into other sinks to give "soft landing" to industry and invented new approaches to discriminate women from workforce to create openings for returning soldiers.

Could something be done starting with 1990? Probably, though the much fragmented by natural borders (if not regulatory) markets with resulting less cash-flush companies had issues fighting against US competition being able to underprice them with politicians ensuring there were no barriers for american companies "or else".

Some of it was at worst mostly local (if with American "advisors"), like in Poland - we started technically from same position as Taiwan when it came to semiconductor manufacturing, but instead of investing "shock therapy" destroyed it. At the same time... can you mention a taiwan major business that is not TSMC, or part of semiconductor manufacturing chain? Without thinking too long or googling?

I was thinking essentially about Linux equivalent of PEP.

Of course my preferred setup would be for systems to actually ship compliant UEFI instead of Qualcomm shitshow

Color depths, not modes per se, and it's more that XFree86/X.Org by virtue of being lowest common denominator didn't have optimizations based on it, and over time GTK and others forgot they exist.

Some systems like Xsgi went further with having several visuals used for predefined purposes in their modified Motif versions

The math is more that benefits aren't that great and the dangers are pretty big, especially if someone fails to properly secure the carrier and you get a rejected takeoff

The enormous water usage values are generally about powerplants providing the power, and even the better reports on that include water use by hydroelectric plants - which makes sense in context of the report, but that context nor sense isn't understood by journalists and hype-men quoting just "trillions of gallons a year, more than X cities"

It's really about bandwidth and availability - US satcom systems were really struggling, and the only truly global (Iridium) was quite low bandwidth. Starlink is essentially "Iridium with newer tech and mass production" and IIRC DoD through various fronts put quite a lot of early financing to make it a thing, even if later the networks were supposedly disaggregated (would make sense to start building separate one once PoC was proven)

I think those do it by running official tsilscale client.

To get other tsnet clients to connect to non-tsnet client you need to provide the connection configuration through netmap from coordinator server

The most insane flexible screen proposal from Nokia was the "nanotech" one - Nokia Morph [1], where the phone "normal" candybar shape was formed out of folding it twice with a clip for speakers - you would pull the clip and unfold it into something akin to A5 or A4 paper. Future sounded bright with software defined tactile buttons and the like.

[1] https://www.youtube.com/watch?v=IX-gTobCJHs

Unfortunately I can't edit my earlier post, because I can't find it - might have been distorted rumour that reached me, then :/

Wasn't helped by my experience reacting very strongly to story of early Arc drivers being problematic because the devs were too used to GPU being just a ring-bus away ;-)

(someone who went on rabbit hole trip through tsnet) It's not very visible (and not really user-accessible) but Tailscale supports connecting arbitrary wireguard peers into the network, and it's how mullvad integration works IIRC - got confirmation on twitter I think from apenwarr.

So yes, tailscale is compatible with wireguard, it's just not exposed by any of the major coordination servers other than mullvad integration in tailscale.com, but the clients will happily consume information about wireguard peers that do not run tailscale at all.

One option would be to implement the custom non-standard Qualcomm drivers that technically it needs to implement anyway, but with support for the UEFI/ACPI interface.

On Windows, Qualcomm ships custom drivers that override normal ACPI platform logic in various places, IIRC

Then it changed, because early on I recall people reporting the drivers wouldn't work at all

Yes, intel lacks a remapping mechanism to support BAR smaller than the total VRAM size.