How does one handle an upgrade to mutators? If a client is running old code then the operation will differ to the server. Obvious answer would be to version them independently: `increment_v1`, `increment_v2`, but wondering if there is a better answer?
Has anyone built a mobile app on top of SQLite that can work offline, but then sync to a server when it gets connectivity? It feels like this could be built with a similar approach to this distributed SQLite, you'd "just" need more robust conflict handling.
This also addresses an issue when you transition from black to transparent to emulate a shadow, and end up with a "cliff" where the gradient abruptly changes. You can see this in the tool when you transition from black to white with LRGB. Any of the other color spaces avoid it. Very cool!
Although it technically has cross platform GUI, Flutter has actually reimplemented all the native OS widgets. As soon as the OS changes some look and feel your app will look out of date.
We currently use wasm on the Adobe XD team for rendering shared prototypes in the browser. It allows us to share C++ rendering code across desktop and web and has been a massive success for us.
The browser support is good enough for our customer base, as it works across all operating systems and mobile devices, and we can fall back for asm.js for IE11.
"These switches to generic medical and psychotropic medications have from time to time caused an increase in reported adverse events, and this is likely to be due to negative attitudes towards generic medicines rather than pharmacological differences between the branded and generic versions of the medication.
This is the kind of thing that leads to an "uncanny valley" app, where things feel slightly off, or they look good until the OS changes something and Flutter doesn't keep up.
Citymapper[1] will do that to a certain extent and it’s pretty good, especially with docked bikes.
I wish I could tell it I like walking more than catching a connecting bus, so I’m occasionally working on a side project to allow custom routes for common commutes.
Is there a writeup on how you architected the project to share 99% of code? I'd be really interested in reading that! From a skim it looks like React + React Native.
Some developers might see this as a good move for them. I don't think it is.
It might be a good move for developers in the short term but it’s a bad move for developers and the web in the long term. We need to keep the web APIs vendor neutral so that one company cannot take control of the future of the web, and move it to benefit only themselves.
The number of barely-standardised APIs they’re adding to Chrome is astounding. It's great to push the web forward, but the fact that product teams at Google have a direct connection to the Chrome team allows them to prioritise the features that benefit their web apps the most.
If the web is going to become Chrome (and sadly it looks like it might), then Chrome needs be moved to a foundation that's outside the control of one company.
Lots of interesting bits in here, and some parts very prescient. The more interesting thoughts to me were near the end: “throw-away workers”, and the last quote on “truth”.