The comic was published on 9 February 2007 [0].
The PS3 was first released in November 2006. I haven't watched the video yet, but its description says "2010 saw the first hacks for the Playstation 3".
828 karma · joined March 14, 2017
The comic was published on 9 February 2007 [0].
The PS3 was first released in November 2006. I haven't watched the video yet, but its description says "2010 saw the first hacks for the Playstation 3".
It's annoying, but thankfully it's a single checkbox in the settings to disable it (uncheck "Suggestions from sponsors").
Plenty of websites already have comically huge pointless images (often then scaled down to tiny sizes for display). No need to make the problem worse.
That said, if I was building a small ugly toy Python implementation, I would probably also not implement long integers. Or the power operator. At least not in the first iteration.
"6 % of the annual worldwide turnover"
A) Claude really produced this counterexample
B) A mathematician working for Anthropic solved a problem mathematicians have been working on for more than a century, and then credited it to Claude for PR purposes
If you believe B is more likely, why would you then believe a proof in the form of a chat log, when said chat log could itself have been faked by Anthropic way more easily than solving the mathematical problem in the first place?
But all of this is ultimately completely unrelated to the concept of "unsafe". You can delete your home directory just fine in safe Rust/Go/Python/etc. You can write a compiler that emits broken code in the same languages; even in a 100% pure functional language with 0 side effects and a perfect bug-free implementation.
Your tests run in an entirely separate process from the compiler (and from cargo). This makes it very different from memory corruption in the compiler:
- The test process can only corrupt its own memory.
- You don't need "unsafe" to run tests. Just the ability to start another process.
- If you're cross-compiling, you wouldn't even be able to run the tests on the same machine (without emulation/compatibility layers)
Does roc run tests in the same process as the compiler?
We don't really know that.
It may have been the first person able to complain - given you couldn't even file a support ticket without getting through this prompt!
"You" here means another app that integrates their API (or you as an individual using the demo on their website). How the other app gets it is up to the other app - ideally it also just queries it directly and requires location permission.
This is matching your phone's location to the already public train data.
Or their API - it also expects device location data:
> At a minimum, requests to the detect endpoint _must_ contain a device's location measurement. Additional fields can be included where available to improve the accuracy of the returned results as outlined below.
Edit: On second thought, that's only needed if you want to run rustc itself on the old hardware, which is probably not super useful given the main reason you would need to do this is if LLVM can't target that hardware.
For building code written in Rust for such old hardware, this would be sufficient.
Do you have some examples? I have developer mode enabled and have never seen any apps complaining (and I have used a lot of different banking apps).
The actual cookie banner merely says "We use cookies to improve your user experience. Learn more" and has a close button.
You'd struggle to find a POS terminal that even has a reader for them in the UK. I've only ever had to enable them in the US or Japan.
I assume you would also have some sort of icon that indicates all of the changes you made have been synced (or the opposite, an icon for when they haven't yet).
Though of course, it doesn't help if the user outright kills the app or pulls the plug or whatever. But I think in that case they should expect to lose some data?
What's annoying is you have to do it in three steps: first transfer it to the app's internal storage, and then save it out to actual files, then delete the internal storage; and you need 2x the disk space.
(Another annoying thing is in some countries they just disable the 5 GHz WiFi, so transfers end up taking forever. Very annoying when traveling, and if I lived in one of those countries I would have definitely returned it)
Meanwhile the swifts will definitely not choose the ground.
But don't worry, Rosetta 2 is also on the chopping block:
> Rosetta was designed to make the transition to Apple silicon easier, and we plan to make it available for the next two major macOS releases – through macOS 27 – as a general-purpose tool for Intel apps to help developers complete the migration of their apps. Beyond this timeframe, we will keep a subset of Rosetta functionality aimed at supporting older unmaintained gaming titles, that rely on Intel-based frameworks.
https://developer.apple.com/documentation/apple-silicon/abou...
> Google Wallet. Create a Pass is iPhone-only. Roughly half of the wallet-using world is on Android, and our generator builds Google Wallet passes from the same form.
What does this actually mean? Google Wallet has had a button to add your own passes for many years. How is the feature described here different?
There is a dropdown at the top-right to select the platform - no need to view source.