vytautask

Congrats! However, it does not look ready to be used. For one, I am missing docker-compose which would spin both frontend and backend with all dependencies. Documentation does not state that but in backend docker-compose file I see a dependency on Redis. Things like that makes it hard for me to try this out (also, not supporting local models - but this might be coming in the future, as you've stated)...

USA army could be one of the best ways to avoid that ;)

>It doesn't cost anything or hurt to keep older versions

First, it affects my app ratings in the application store/shop. Some user with 15-year-old device gives me 1-star rating because of some annoying bug that was already fixed 10 years ago but he can not upgrade because that newer version is using a newer API.

Also, what about bugfixes and support? I do not want to have to support (answer emails/calls and deal with bad reviews on all platforms) my ancient version of an app. This would make my app unaffordable for 99% of my users.

IMHO, would be easier to get a new restaurant mobile number and update that on the restaurant/google website than to contact Google support. However, this article in the Guardian will likely attract some attention from Google employees.

That's not true. E.g. Lithuania has laws restricting it (can not even have opened alcohol bottles inside of a car).

I was genuinely expecting another article about ChatGPT and some ingenious way to use it for generating test-cases. Turns out, this is just marketing post after all with no relation to the former... Disappointing...

Also, the orchestration becomes easier - you can run the same docker container on multitude of different OSes and configurations. In addition to that, you get great isolation.