I was running Stable Diffusion on my iPhone two years ago. You can get quite good open weights models running on-device today. What’s going on over there?
I was running Stable Diffusion on my iPhone two years ago. You can get quite good open weights models running on-device today. What’s going on over there?
> Notable discovery: you have significant positions in semiconductor manufacturers. This warrants checking for any internal analysis on the export restrictions [google_drive_search: export controls]
Oh that's not creepy. Are these supposed to be examples of tools usage available to enterprise customers or what exactly?
<example> <user>how should recent semiconductor export restrictions affect our investment strategy in tech companies? make a report</user> <response>
Finding out where the user works is in response to an under specified query (what is “our”?) and checking for internal analysis is a prerequisite to analyzing “our investment strategy”. It’s not like they’re telling Claude to randomly look through users’ documents, come on.
Would you store all your ~/ in something like SQLite database?
Actually, “we”, collectively, do know, because the SEC maintains an “XKEYSCORE for equities” called CAT.
If there was interest, the government could know exactly who placed these trades. But the call (options) are coming from inside the house.
SQL has CREATE TABLE IF NOT EXISTS. Rust could have `impl Trait if not already implemented`.
After 8 years of programming ~exclusively in Rust it’s easy for me to take this for granted by forgetting that linker errors even exist — until I am rudely reminded by occasional issues with C/C++ code that ends up in the dep tree.
This property is downstream of the orphan rules, and given the benefit I wouldn’t give them up.
Clearly some people do find them useful.
This is a strawman argument, you're arguing semantics here. You're a smart person, so you know exactly what he means. The perception created by your article is that people shouldn't use Go because it's not memory-safe. But the average developer hearing "not memory-safe" thinks of C/C++ level issues, with RCEs everywhere.
Unless you can show a realistic way this could be exploited for RCE in actual programs, you're just making noise. Further down the thread, you admit yourself that you're in a PLT research bubble and it shows.
Yes, semantics — what do things mean, exactly? — is the subject of the discussion here and is actually quite important in general.