p_l

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.

Only on specific devices, but generally every GPU released in last few generations, and every dedicated GPU from intel[1], supports "large BAR" this way to map entire GPU memory into MMIO space. This has to be supported on both target device and AFAIK the PCI Root Port[2], and of course needs to be properly handled in firmware - which this tool fixes.

[1] Intel GPUs actually can't work without it, because they do not have legacy "windowing" mode where portions of 256MB BAR window are mapped to different areas in GPU memory

[2] This tool implies that it's possible to handle root port side entirely in firmware, but it's new to me at least, so I can't vouch for that :)

The issue was not reverse engineering Active Directory to make a compatible system, it was that they didn't really capitalize in that direction. Sun has all the necessary pieces to make a compelling option at the time.

Microsoft really only wiped competition in the area when 2000 landed with Active Directory instead of the clunky previous NT Domain system.

Because pretty much every BMC out there in last decade is shipping AST2400/2500/2600 which include VGA and you want to deal with cases where people do not know how to navigate serial console, especially in case of windows servers

If I wanted 16 hours for just SSH, I would have went with X-series thinkpad already back in 2015 or so when it easily reached 26 hours without suspend in my friend's testing. As a thin client it also sucks, because keyboard, never figured if they fixed grounding of the chassis, the "let's make your doctor ask if you're suicidal" hard edges near wrists, and so on.

The nice thing with kerberos is that it v5 has extensibility effectively built in :)

I'd say the switch to DAP/LDAP was obvious better choice than Hesiod, and GPO essentially standardizes a lot of tooling that SIPB et al built for Athena as well

I am enough of a nerd to know that people will come with assumptions about libc based on Free/Net/OpenBSD and get burned because no, you can't fix the system libc with brew oneliner

No, people don't.

It's just that mishmash of OSFMK (with BSD APIs of 1991 or so) with random additions of newer APIs does not necessarily make it a great Unix to work with in 2026

You can ignore KVM license if you have good netboot infrastructure and only install OS in UEFI mode - SOL works fine.

The big issue is usually "remote media" support, thus my recommendation for setting up netbooting infrastructure

Oxide happened long after (U)EFI brought proper serial support to boot process