822 karma · joined January 9, 2015
There is no comfortable position to use an iPad in. In bed you're craning your head over, or propping it on your raised thighs. The keyboard cases are flimsy or super heavy.
I love the user interface on the iPad, it looks the best of iPhone, iPad, and Mac. But a MacBook is so much more ergonomic than an iPad.. :(
I use this to block Twitter, Facebook, etc.
This could be just as disruptive.
Difficult to say that they will actually follow through, as the only mention of this date is in the random forum post I linked.
James should find a better host for his blog, the loading time is abysmal. Presumably because of the comments section. (Which is actually interesting!)
This still isn't any better than the initial example. It could still crash between sending the message and enqueueing the second job. So it may still send out the same message twice.
Heroku style still removes the burden of managing servers ("serverless"), but doesn't lock you in as much. You could easily move your own server process to a different provider.
Is it just because Amazon doesn't offer anything similar to heroku?
https://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview....
I use it with my personal email (hosted at Hover), and my work email, hosted on some IMAP server.
Works like a charm.
> CloudKit end-to-end encryption
> Apple Pay Cash, User keywords, Siri Intelligence, and Hey Siri use CloudKit end-to-end encryption with a CloudKit service key protected by iCloud Keychain syncing. For these CloudKit containers, the key hierarchy is rooted in iCloud Keychain and therefore shares the security characteristics of iCloud Keychain—the keys are available only on the user’s trusted devices, and not to Apple or any third party. If access to iCloud Keychain data is lost (see “Escrow security” section later in paper), the data in CloudKit is reset, and if data is available from the trusted local device it is re-uploaded to CloudKit.
If they were lying in their documentation, or the software itself, that would be a different story.
Only looked at the read path, which is roughly:
* filesystem receives read
* blocks on a semaphore (https://github.com/yarrick/pingfs/blob/master/chunk.c#L141)
* network thread wakes up semaphore when ICMP reply containing data is received
* filesystem thread copies data into new buffer to return from syscall
* filesystem relinquishes chunk back to network thread, which wakes up, sends it back to be echoed on the network via ICMP, and frees the in-memory buffer (https://github.com/yarrick/pingfs/blob/master/chunk.c#L107)
How silly :)
Code a lot. Understand non-blocking I/O, memory management, parallelism.
Learn everything about networking you possibly can. At every level.
Hone that skill set over a few years and you’ll be invaluable.