twisteriffic

Well then, I suppose we should all just let her off the hook.

I mean... The problem is common enough that there are industry specific terms to describe it. Go search that database for "commercial pressure" and I'm certain you'll find what your sealioning self is demanding from everyone else.

I've found my Razer Deathadder 2013 and Logitech G5 v2 very easy to repair. I go through a set of switches every 4-5 years it seems, plus cables on the G5.

I had never heard anyone say "I'd like to double-click on that" until yesterday and now it's following me everywhere...

> Try teaching someone C# nowadays. Completely impossible.

That isn't a reasonable take. Failing to teach a language by enumerating all its features is an indictment of the instructor and not the language.

From the PoV of someone who uses C# every day those are very strange things to be upset about.

A decent portion of Azure Web Apps internals hasn't moved past .net core 2.3

Cries in dapper dapr

> C# similarly has old warts that are discouraged now. .NET Framework is a great example (completely different from modern c#, which used to be called "dotnet core"). WPF and MAUI are also examples. Or when "dynamic" was used as a type escape hatch before the type system advanced to not need it. ASP being incompatible with ASP.NET, the list goes on.

Almost all of this is incorrect or comparing apples to oranges.

.net framework and .net core are runtime and standard library impl, not languages. C# is a language that can target either runtime or both. Framework is still supported today, and you can still use most modern C# language features in a project targeting it. WPF and Maui are both still supported and widely used. ASP predates .net - c# was never a supported language in it. ASP.net core has largely replaced ASP.net, but it's again a library and framework, not a language feature.

Dynamic in c# and the dlr are definitely not widely used because it's both difficult to use safely and doesn't fit well with the dominant paradigm of the language. If you're looking for STD lib warts binaryserializer would have been an excellent example.

I don't know if you've heard, but norms don't matter anymore.

> How is it possible that other users of Aurora aren't experiencing this issue basically all the time? How could AWS not know it exists?

If it's anything like how Azure handles this kind of issue, it's likely "lots of people have experienced it, a restart fixes it so no one cares that much, few have any idea how to figure out a root cause on their own, and the process to find a root cause with the vendor is so painful that no one ever sees it through"

> The party affiliation of the owner is irrelevant to that.

Yeah that's a nice thought, but it ignores a whole lot of recent evidence to the contrary.

This exploit seems to be taking advantage of the slow token-at-a-time pattern of LLM conversations to ensure that the extracted data can be reconstructed in order? Seems as though returning the entire response as a single block could interfere with the timing enough to make reconstruction much more difficult.