Which animations are you referring to? I don't think I can find any components with animations in the GOV.UK Design System <https://design-system.service.gov.uk/>.
Likewise for underlines on headings – I can't see that in the style guide.
Switch the `<link href="">` value to point to a high contrast stylesheet.
Or alternatively, apply a class to the body tag – e.g. `<body class="high-contrast">` – and declare CSS rules accordingly. Specificity should take care of overriding the 'normal' style rules where needed.
It comes with an adapter for Google Photos, so you can use it to download / backup photos and videos in your library.
Note: there are some limitations to this approach – namely that rclone won't be able to download your original image files, even if you uploaded with 'original' quality. These limitations are documented on the rclone website: https://rclone.org/googlephotos/
I'd recommend that your customer checks out [Chrome Remote Desktop](https://remotedesktop.google.com/). It's completely free, simple to set up, and seems to perform way better than VNC. Plus no need to open firewall ports or worry about encryption and security – that's all handled for you.
Just for the record, you don't need to worry about any of that with RealVNC either, and the protocol seems way more efficient than any other VNC I've used. Frankly, I think the product should be renamed to get rid of this bad association. It's way more similar to LogMeIn Pro than TightVNC, for example.
It’s a terrible user experience for anything other than clicking on things. Can’t use a lot of keyboard shortcuts because they trigger browser behaviours. An issue that didn’t exist when they had a chrome app. The website always breaks in some form. Is laggy. If you’re using windows and the lock screen happens and you come back. Copy/paste stops working.
This. If the link preview fails to load on the sender's device, it'll never appear for either party. The preview is sent along with the message – the receiving device never generates the preview.
If you're quick enough, you can see it in action:
Paste a link in a WhatsApp message. The preview might take about half a second to load. Hit 'send' before the preview has loaded, and it'll never show for that message.
Paste the same link again, but wait for the preview before hitting send. It'll stay attached to that message.
Serverless backends tend to work quite well when paired with a Single Page Application on the frontend – e.g. Vue.js or React. That way your frontend can be served from a static host – e.g. S3 or GitHub Pages – almost instantly. And so the perceived performance of your application isn't harmed (as much as you'd think) by the latency of your backend, since other aspects of the application's interface can load and continue to be responsive.
To me, that does not seem to describe anything specific to "serverless"?
You've always been free to serve your static assets in any way you like, so I'm unclear as to how the way the backend is architected comes into play here.
I think they're suggesting that bad latency from a serverless architecture is mitigated by a SPA, since the application can render and appear functional while it's fetching data.
Still, not sure how damage control for poor performance is a "pro" of serverless design.
Well, there's very little (if anything) that "serverless" can do that other techniques can't accomplish. It's about costs & benefits, not whether or not you can do something.
Though I tend to agree I'm yet to hear a really compelling description of why I should move very much into it. Some of this may be because I tend to write in a style that makes it fairly easy to mix & match bundles of application functionality anyhow, so to me adding some tiny function to a running app isn't that big a deal. (I don't use Erlang directly, but Erlang is where I learned this from.) If you're in an environment where deploying a single new REST handler or some recurring service is much harder, though, I could see where it comes in handy for certain things.
I guess. I fail to see how this is better than sticking an API server onto Heroku or similar, especially given the engineering hours spent will easily dwarf any potential hosting cost differences.
Not sure if any of the serverless offerings are 100% there yet, but I have a hard time not seeing this as the future for most things.
I just want to quickly deploy code in a friction and maintenance free manner with zero compromises on scalability, latency, flexibility or reliability, what the problem is?
It's really silly – but Apple keep the NFC functionality exclusively for use by Apple Pay. Whilst it is NFC, Apple have never marketed it as such. Presumably they want people to think that it's just Apple Pay 'magic'.
Not just Apple Pay anymore, they also use it for certain transit cards and student ID cards. New phones can read tags and launch the appropriate app (via notification like Camera gives you for QR code reading): https://www.macrumors.com/2018/09/12/2018-iphones-background...
Is the UK most advanced? In Australia they can pay for anything up to $100 with tap. Over $100, they can still tap, but then need to enter their PIN into the terminal (i.e. no need to insert the card for PIN entry – a tap is sufficient). We don't have that in the UK.
Similar in Poland. You can always tap and then it asks for PIN or it doesn't. I expect this decision is based on the amount of the purchase and maybe some other factors.
I don't think having a higher limit makes anything more advanced. I'm fine with having a lower limit for cards, and then switching to Apple/Samsung/Google Pay for higher priced transactions.
Most advanced in Europe maybe. I rarely use anything but contactless in the UK (where I live), but often find no option for contactless elsewhere in Europe. I've never had to swipe and sign anywhere in my whole life, though.
Likewise for underlines on headings – I can't see that in the style guide.