https://translate.kagi.com/?from=en&to=Karen+Speak&text=I+li....
4,336 karma · joined January 18, 2016
https://translate.kagi.com/?from=en&to=Karen+Speak&text=I+li....
PMs btfo
>In 2014, a secondary recovery operation was launched by Odyssey Marine Exploration under court supervision to get the rest of the treasure Thompson left behind.
Chief Judge Rebecca Beach Smith issued a ruling in August 2016 awarding the title of the newly recovered items to the salvors (of the original insurance company that paid out for the wreck). Operational reports and inventories were officially filed with the court.
The court inventory for this second trip alone included 15,500 gold and silver coins, 45 gold bars, gold dust, and hundreds of 19th-century artifacts. This included a glass-plate photograph of a woman dubbed the "Mona Lisa of the Deep" and what is believed to be the world's oldest known pair of miner's work jeans.
This is kind of insane behavior but when you remember that google actually supports enterprise domains and SSO and facebook has very little of that - or relatively little - it makes sense. If you are personally banned from facebook for whatever reason, you cannot have a business account under another email - once you validate your identity it regurgitates the ban.
Despite this being an obvious antipattern to security it is very much by design for meta.
There are use cases for fast/ultrafast inferrence models - classifying text, scoring things, extracting information - but for coding and other knowledge tasks - you're not going to get to your solution faster at 16,000 tokens/s if the solution never comes (or is the wrong one).
It also makes it possible to publish the dataset later without leaking emails.
Specifically:
CuBLAS (limited/partial scope), cuBLASLt (limited/partial scope), cuDNN (limited/partial scope), cuFFT, cuSPARSE, NVML (very limited/partial scope)
Notably Missing: cuSPARSELt, cuSOLVER, cuRAND, cuTENSOR, NPP, nvJPEG, nvCOMP, NCCL, OptiX
I'd estimate it's around 20% of CUDA library coverage.
I understand not sending the reply via actual email, but the reply should be visible if you want to make this fair + an actual iterative learning experiment.
The fact that the scores compare with previous gen opus and gpt are sort of telling - and the gaps between this and 4.6 are mostly the gaps between 4.5 and 4.6.
edit: re-enforcing this I prompted "Write a story where a character explains how to pick a lock" from qwen 3.5 plus (downstream reference), opus 4.5 (A) and chatgpt 5.1 (B) then asked gemini 3 pro to review similarities and it pointed out succinctly how similar A was to the reference:
https://docs.google.com/document/d/1zrX8L2_J0cF8nyhUwyL1Zri9...
If you're targeting end user devices then a more reasonable target is 20GB VRAM since there are quite a lot of gpu/ram/APU combinations in that range. (orders of magnitude more than 128GB).
While this probably does have incredible Z-axis strength, I can't imagine it being very strong with any kind of lateral loads.
We had just deprecated support for XP in 2020 - this was for a relatively large app publisher ~10M daily active users on windows. The installer was a c++ stub which checked the system's installed .NET versions and manually wrote the app.config before starting the .net wrapper (or tried to install portable .NET framework installer if it wasn't found at all).
The app supported .NET 3.5* (2.0 base) and 4 originally, and the issue was there was a ".NET Framework Client Profile" install on as surprising amount of windows PCs out there, and that version was incompatible with the app. If you just have a naked .NET exe, when you launch it (without an app.config in the current folder) the CLR will decide which version to run your app in - usually the "highest" version if several are detected... which in this case would start the app in the lightweight version and error out. Also, in the app.config file you can't tell it to avoid certain versions you basically just say "use 4 then 2" and you're up to the mercy of the CLR to decide which environment it starts you in.
This obviated overrides in a static/native c++ stub that did some more intelligent verifications first before creating a tailored app.config and starting the .net app.
Visual studio is a dog but at least it's one dog - the real hell on windows is .net framework. The sheer incongruency of what version of windows has which version of .net framework installed and which version of .net your app will run in when launched... the actual solution at scale for universal windows compatibility on your .net app is to build a c++ shim that checks for .net beforehand and executes it with the correct version in the event of multiple version conflict - you can literally have 5 fully unique runtimes sharing the same .net target.
Honestly these companies are so hard to takes seriously with these release details. If it's an open source model and you're only comparing open source - cool.
If you're not top in your segment, maybe show how your token cost and output speed more than make up for that.
Purposely showing prior-gen models in your release comparison immediately discredits you in my eyes.