ShroudedNight

Lycos

I assume the implication was an intercept facility.

Quite the opposite, people worked very, very hard to make Winamp even more non-standard via skinning.

"Is your washroom breeding Bolsheviks?"

It has been associated with 3D rendering, but given that things like the S3 86C911 are listed on the Wikipedia GPU page, saying "Accelerated GUIs don't need GPU" feels like attempting to win an argument by insisting on a term definition that is significantly divergent from standard vulgar usage [1], which doesn't provide any insight to the problem originally being discussed.

[1] Maybe I've just been blindly ignorant for 30 years, but as far as I could tell, 'GPU' seemed to emerge as a more Huffman-efficient encoding for the same thing we were calling a 'video card'

Is that what's going on? So many touch gestures seem to rely on landing in the right 2mm diameter area, but the minimum reliable resolution for touch seems to be a 4mm diameter circle. It's even worse for my father, even though cognitively, he would have no trouble understanding the hypothetical requirement. It's also noticeably worse during the depths of winter.

What does "GPU" mean here? Previous uses of the term seemed to imply "dedicated hardware for improving rendering performance" which the SVGA stuff would seem to fall squarely under.

Was it the same 1% that was using each of the long-tail features? I suspect that by refusing to invest effort in at least some amount of niche features, we essentially alienate _everybody_

"I think" is explicitly disclaiming authority. Omitting it changes the social signaling of the response significantly.

Switching "wooden" for "a bit unnatural" also does a disservice: "wooden" describes a specific quality of deviance.

Over-all, I would definitely consider the revision stiffer and more reserved than the original.

I would take things somewhat further: I'd be happy to pay the equivalent of $20 2015 dollars for this service if it were comprehensive. Unfortunately, that might allow for a consumer surplus to occur in the viewing experience and the motion picture industry ties with maybe nVidia for peak pathological hostility to retail consumer surplus.

Wouldn't browser prefetching subvert these small frictions to entry?

Are you suggesting that beggars would ride, if only wishes were horses!?

Also worth remembering that around 2010, the music and film industry associations of America were claiming entitlement to $50 billion dollars annually in piracy-related losses beyond what could be accounted for in direct lost revenue (which _might_ have been as much as 10 billion, or 1/6th of their claim):

https://youtu.be/GZadCj8O1-0

These guys pathologically have had a chip on their shoulder since Napster.

"No security features should exist for anyone" is itself fanatically hyperbolic narrative. The primary reason this event has elicited such a reaction is because OnePlus has historically been perceived as one of the brands specifically catering to people that wanted ultimate sovereignty over their devices.

As time goes on, the options available for those that require such sovereignty seem to be thinning to such an extent that [at least absent significant disposable wealth] the remaining options will appear to necessitate adopting lifestyle changes comparable to high-cost religious practices and social withdrawal, and likely without the legal protections afforded those protected classes. Given the "big tech's" general hostility to user agency and contempt for values that don't consent to being subservient to its influence peddling, intense emotional reaction to loss of already diminished traditional allies seem like something that would reasonably viewed compassionately, rather than with hostility.

At one point I could have sworn they were sticking obsoletion notices in the header, but now I can only find them in the right side-bar:

https://datatracker.ietf.org/doc/html/rfc5245

I agree, that it would be much more helpful if made obvious in the document itself.

It's not obvious that "updated by" notices are treated in any more of a helpful manner than "obsoletes"

For the audience: I had never heard of Brian Berletic previously. In an attempt to understand what this person's undisclosed conflicts of interest were, I found numerous reports of him painting the Myanmar Junta in a positive light:

https://www.reddit.com/r/InformedTankie/comments/ufq4oq/a_co...

https://forsea.co/bangkok-based-conspiracy-blogger-brian-ber...

There's a certain event-horizon where bitterness taints / skews perspective enough that even what would otherwise be helpful insights becomes so costly to disentangle from grudge-extrapolation that it's not obvious if any of it ends up being worth the cost of entry. At least to me, this person's work seems well beyond that point.

If the political environment gets bad enough, you may expect to die anyway, and the TTL difference that obfuscation provides means the difference between making a small improvement before the inevitable, or not.

I'm not an IETF process expert. Would this be worth filing errata against the original RFC in addition to their new proposed update?

Also, what's the right mental framework behind deciding when to release a patch RFC vs obsoleting the old standard for a comprehensive update?

It does look like there are legitimate issues with x87 floating-point: https://github.com/rust-lang/rust/issues/114479

Yeah, that sucks. I assume this is SSE2?

I thought the Pentium Pro _was_ a 686?

Wikipedia seems to correlate: https://en.wikipedia.org/wiki/Pentium_Pro, as do discussions on CMOV: https://stackoverflow.com/a/4429563

It's not just that, current sentiment around the CFAA is that any kind of unsanctioned third-party user agent for anything that isn't the open web is potentially prosecutable. Plus, if the big user platforms decide they don't like some aspect of what you're doing, they will shut down all of your access, and potentially access of others close to you, everywhere, and aggressively prevent you from reestablishing even a baseline of inoffensive participation, at great potential cost to your well-being.

Isn't it usually one bill, but an omnibus bill? My understanding is that the actual guard rail that the US congress has discarded is requiring that the contents of the bill be limited to the purview described by the bill's title.

I agree with the sentiment in general, but in this case it seems extremely well known:

https://www.lpm.org/news/2025-11-11/mcconnell-paul-clash-ove...

At one point laptop wifi cards seemed to mostly be m.2 cards, which, while not usually trivial, were relatively feasible to swap out. Has that changed?

I hate that curl $SOMETHING | sh has become normalized. One does not _have_ to blindly pipe something to a shell. It's quite possible to pull the script in a manner that allows examination. That Homebrew also endorses this behaviour doesn't make it any less of a risky abdication of administrative agency.

But then I'm a weirdo that takes personal offense at tools hijacking my rc / PATH, and keep things like homebrew at arm's length, explicitly calling shellenv when I need to use it.

Has something changed that allows a more relaxed refcounting / less eager "gc"? Py_DECREF was what murdered any hope of performance back when we hooked up 3.3 to OMR... Well that and the complete opacity of everything implemented in C

I did, however that call out did, admittedly, slip past me

There's also Angel Hernández retiring.

Was this compiled at O0? The generated code looks unnecessarily long-winded - at the very least I would expect the match jump table to get culled to only the Relaxed implementation.