Unless you're hoarding data or want to avoid Microsoft, the choice is simple. And I'm sure you have even cheaper services.
The thing is, I just can’t find an argument why I should be able to get very rich doing my job. It’s a comfortable job. It pays a good salary. I got here by taking no risk at all. I wouldn’t want to switch jobs just to drive up my pay even if I could. I have other things to think about. I have worked 20 years in the same job and so have my colleagues. This is a cultural difference I feel.
I've seen people (including myself) trying to change the lifestyle, thus money is a vehicle to do so and to build something with. Not everybody has got rich parents or sugar daddies, some people start from nearly zero and try to climb the social ladder.
A higher salary can unlock multiple benefits, in terms of long-term economical security (e. g. in case of market crash and companies go bankrupt / berserk mode, laying people off) and maybe buy yourself a house/apartment.
Plus, saving for children's future is one of the best gift a parent can do.
Coming to an end: having a salary which is similar to what in SF are offered would be really good
* communicate with clients * does the architecture design * does the API stub implementation * does code reviews * provides technical leadership / last word on a choice
A pure "throw away" would be much cheaper
Java Preferences API are a classic example of this false myth, since e.g. on MacOS it behaves differently than in Windows/Linux.
And ever heard of Native Runtime? If you want to create a native runtime, you just need to do this on the target platform.
So this is very odd to me. GoLang went much further, doing true cross compilation
Another good measure is the number of dependencies used: if too much, the quality might be poor (= poor maintainability).
Is the application vulnerable? Check OWASP for this.