whaleofatw2022

The pro did register renaming. But the way it worked, if you wrote to AX (16 bit write) and then read from EAX (32 bit read) it caused a pipeline stall from resyncing the registers.

Is it?

Never ran into that with any I owned unless the paint was questionable or the barrel was a bad fit for the paint, even when I accidentally had a very 'hot' shooting automag due to co2 and a scorcher of a big game day.

I'm not them but I will answer from my viewpoint, as someone who has learned to appreciate the efficiency of AI coding.

First, my only interaction with a waymo was while driving in a low traffic location and it started with me having to be extra evasive with it's cautious style shifting into it deciding to pass me despite my safe but assertive driving normal stance.

Second, lots of people (myself included) remember the talk 5-7 years ago around autonomous cars and how the leaders of such companies were talking of futures where nobody (but the ultra rich, of course) would actually own a car and everyone would just use these autonomous car services.

Where that breaks down is how the surveillance state makes the average person worry how every trip could be tracked and used against them somehow or outright denied...

But also everyone sees how once vendors have a captive market they get squeezed.

I think part of the comment is related to the typically much more lackluster management of video game source code, historically.

If I recall (as an example) Final Fantasy 8 had to be redone based on the PC port rather than original source code because, well, nobody cared about that back then.

The situation has almost certainly improved since then. Still, we have to remember that cases like Doom and Quake where there was cleanish source code was an exception, not the norm.

Doubly so when there are 'licensed' libraries or middleware involved, stuff coming to mind being:

- DMX sound driver (Doom) - RAD tools (e.x. Warcraft/Diablo for cutscene video) - Renderware (GTA2/3 and Vice City, among others) - Console SDKs (in the case of console games)

And, again, sure. It's possible that if the source code is clean enough, you can safely rip those things out without needing legal review. But if the source isn't clean enough (and a lot of games, its not) there is a concern.

Doubly so when it comes to console only releases and not wanting to accidentally anger a manufacturer by unintentionally exposing an undiscovered exploit.

Yep.

Some originators will hold on to servicing of your debt wherever it goes (within certain boundaries, e.x. if you go into a delinquency or reconciled delinquency state).

Those originators use it as a selling point, because many people have gotten bit by servicer flips one way or another.

There's a medium. Something ironically close to apple's 'non fully approved and supply chained repair' thing (especially when we consider the case of a screen that could be OCRing data and tossing it out later).

'You have unexpected components. You may want to have your device inspected or risking compromise of x/y/z. Should we continue or lock it down'?

Not necessarily.

In an odd sort of irony, I know that at least one WITCH in fact gives feedback to the employees about their monitoring directly, versus other 'solutions' where only the manager and/or HR gets access to the system's reporting.

So, "If only you could talk to the monsters" but at the level of this genre?

Regarding the comments about the jargon file...

Something definitely changed around the dot com crash. The channels I slummed around in of EFNet went from excited hacker archetypes to the same people doing jobs I was am in retrospect surprised about [0]

[0] - Im general, emulator devs working for bigger corporations. But most specifically one that wound up doing stuff around customs intrediction tech, major shift from their pre emulation work.

IIRC, they specifically started with freewheels because they arent that different from a reel in how they work.

One exception that does come to mind, is .Net Framework on x86. AFAIR that didn't use SSE or SSE2. (In x64 mode it did however, since those were part of the baseline for x64)

Bold assumption until there is legal precedent set.

... was in jail.

He died in 2021.

Curiously enough, unless something changed and nobody updated his Wikipedia page, his family didnt even collect his ashes.

5% is a pretty high rate IMO. When I worked at retail 20 years ago we got around 2 or 3%, and that was a mom and pop shop, not big retail...

Dumb question, wouldn't node size impact the logic latency itself on some level?

I do believe that yes, if it was wiped before entering, there would be no charges (unless there was a shadow docket open... that gets murky)

Not just the RAMBUS debacle, that 20 stage pipeline and IIRC the barrel shifter wasnt as good as on P3 or AMDs CPUs...

Used to flip both ways...

I.e. for a time, it became easier for talented people to find a better role.

In the last 5-10 years though, between the race to the bottom and AI/Bot spam (even ignoring the overall decrease in job availability) things frankly suck.

Not sure about that bit...

What is well known however, is that a bunch of Alpha engineers wound up at AMD, and a lot of that DNA went into the OG Athlon

Its funny because I have been asked by some folks at work as to why I dont just 'allow all commands' and instead review each one, and then I let my colleague in infosec know who asks that so they are aware of dangerous users.

Where it gets tricky is that, at least in past US case law, 'maps are facts' and thus cannot be copyrighted as easily (this is part of why published maps often have intentional, hopefully subtle errors in them) [0]

[0] - I believe a specific case was Nintendo vs Prima publishing, which was even involving a map of a fictitious construct.

The RE thing may have been a false narrative, but tax abatements were a factor in at least one local company doing RTO; their business tax breaks were partially based on employees working in the city and then paying city payroll tax.

One of the things I ironically loved about my windows phone was that it was a PERFECT Phone [0], Sms [1], and Navigation device [2], good enough for music, but SUCKED the further you went from that.

[0] - Call audio was pristine

[1] - large live tile for SMS was great

[2] - Bundled HERE Drive let you pre download map data long before competitors had the option.

Part of me wonders, would 3d xpoint (if still around) be a viable option?

Yeah it is slower than real RAM by a good amount for latency, but you can get similar bandwidth and the cost was history about half of the same size DDR.

There are some minor exceptions but agreed otherwise. Manufacturers have been excessively using VRAM limitations as a price point distinguisher.

Aka 'follow JSF guidelines that still apply to C and not just C++'.

I.e. all alloc should happen up front, functions should have predictable execution time, etc etc

But can it do a better bad apple?

Lest we forget how they snubbed Bungie...

Depends a LOT on the res.

E.x. notebookcheck indicates that FEAR (released a yearish later) could get 20-30ish FPS at 640x480 but chokes at 1024x768 (at numbers matching the HL2 lost coast demo slideshow at 1024x768).

Gotta remember a lot of mac people were just happy to play something more modern than Marathon or Giants CK

Something to be said for branding.

There's a pizza place by me called "slice of the 80's" that has tacky vaguely 80-s feeling styling.

Surprisingly its been around for over 15 years and not the flash in a pan pizza shop that tends to come and go. Heck, I dont even think its very good, yet it has survived.