The biggest advantage of json is its ease-of-use. It is super easy to get started, and once you are start using it to build a quick prototype, you are stuck with it.
And the customers of your api understand it as well, so you likely need to support json even if you may use something else internally.
Created an account to play with it. Great work! Some suggestions:
1. Accuracy needs to be worked upon. I asked "How many total movies are there" in the demo project, it gave me "You are trying to run an unsafe operation" (!!).
2. It asks for database access if you want to run on your database. Until the trust in the tool is developed and value proposition is clear, will be hard to give any database access.
Biggest takeaway for me from this article:
(a) Huge cost savings ($38K/week) by moving away from cloud,
(b) Using MRSK for web app deployment (instead of Kubernetes).
Question - for folks looking to host a rack in a third-party data center, what are the current top choices?
It is in the best interest of the passengers (at least the international ones) to go back to the airport and get the immigration done. It will only cause trouble at the time of future departures/arrivals, and cause issue in visa extensions, etc.
I would also add that the databases in 2020s will be written in Rust, rather than C/C++. The safety guarantees Rust provides makes the development process faster, as well as results is clean code that is easier to understand and extend.
The examples presented are not significant issues (in my opinion).
If someone from the Rust language development community is reading this, what I would really like to see is Rust supporting default arguments to functions. Coming from C++/Java/Python world, that is one language feature I sorely miss.
And the customers of your api understand it as well, so you likely need to support json even if you may use something else internally.