I can see how it might be useful if the AI is only used for research and pointing out existing case law etc.

Otherwise it just sounds like another pointless and BS use-case from another rando AI company to keep the money taps flowing.

Y'all is a feature of general Southern vernacular and has nothing to do with Texas other than most of the settlers of Tejas were from the South.

Also saying things are a feature of Texas is a feature of Texas.

IIRC it was initially employed for their payroll system to help print checks.

First commercial use in Bell Labs is usually credited as the secretarial pool for writing patent applications.

I always give an ironic chuckle when fighting the print system on a unix machine(lpd, lp, cups...) the internal rant that goes with it is something like.

"Printing was THE original purpose, the reason for existence, of unix, you would think it would be a solved problem instead of the terrible mismatch of sins that it is."

printing on unix in my experience is quite painless compared to windows for example, in my experience

it just works :p

I'm going from 30+ year old memories as an intern, but from what I remember:

Usually the RS232 was just on the terminal side. Somewhere along the path it got converted to twisted pair.

All the twisted pair serial lines congregated in the server room at a punch-down box. Eighteen year old me wasn't allowed to mess with anything past that point, but from what I can remember those lines were concentrated by a multiplexer (mux) and sent on to the minicomputer.

I think you're right. I remember seeing a lot of ads for muxes in the Datamation magazines I read as a kid.

I can't give any details about them, because well, I was a kid, and the details of what they were talking about were beyond me...

NASA's IT used to be split into the field centers and a central core IT organization. The field centers managed their own stuff, but anything agency-wide was handled by the core IT organization. Central IT also usually won out when there was a conflict.

When NASA combined their disparate field center mail systems into one (OneNASA and later NOMAD) massive mail system in 2006-2008 they deployed everything that wasn't the squishy Exchange underbelly on SuSE Enterprise 10.

The field centers were very invested in RHEL. Mostly for scientific software and Oracle.

JPL has traditionally been separate from the rest of NASA and works with CalTech for their infrastructure.

RedHat also backports fixes, security patches, and (occasionally) features to existing RPMs without incrementing the minor version.

For example fuzzywhatsit-3.0 in RHEL could be functionally equivalent to 3.5 in another distro.

They even rebase packages to new upstream versions in point releases (where doing so maintains backwards compatibility, of course).

There's a much larger than zero possibility something (network gear) North of this thing is black-holing ICMP echo and/or your ISP is dropping the responses.

Yeah I'm going to call this a hard pass until I see third-party benchmarks, power draw numbers, and what AMD has with RDNA3.

This is starting to look like a repeat of Geforce FX vs Radeon 9700 Pro all over again.

It has been multi-threaded since at least the early 2000s and most of the work for handling scaling beyond 32 cores was completed in 2012.

https://www.cl.cam.ac.uk/teaching/1516/ConcDisSys/2015-Concu...

Well, to be honest a whole lot has been done to FreeBSD network stack scalability quite recently (14-CURRENT), eg introduction of epoch(9) and the routing nexthop patches.

If I recall correctly 3D Pipes shipped with NT 3.51 as IIRC 3.5 only shipped with software OpenGL with no support for hardware acceleration.

I remember running it on a DEC Alpha box with an AccelGraphics AG500 and being awed by it.

I think that's correct: Windows NT first. It ran just fine on my 486DX2.