That's strange, the form factor is the worst part for me.
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.. :(
Apple Support cannot do anything if you forget the device passcode, there is no back door. Best advice I can think of is, is ask her to restore an iCloud backup, after erasing the phone.
> The Brydge Pro+ has been designed to bring a better experience to the iPad Pro. We've created hardware that maximizes the current functionality within iPadOS, and as accessibility features evolve and improve, the user experience will become more intuitive.
James should find a better host for his blog, the loading time is abysmal. Presumably because of the comments section. (Which is actually interesting!)
> Going back to our message-sending example, how might we use these concepts to ensure consistency? In this case, we might break the job into two pieces, with the first one sending the message and enqueuing the second one, and the second one writing to the database. In that scenario, we can retry either job as many times as we want—if the message-sending provider is down, or the internal accounting database is down, we’ll appropriately retry until we succeed!
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.
Does anyone know why lambda is taking off, compared to heroku style PaaS?
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?