SQLite works great as the database engine for most low to medium traffic websites (which is to say, most websites). The amount of web traffic that SQLite can handle depends on how heavily the website uses its database. Generally speaking, any site that gets fewer than 100K hits/day should work fine with SQLite. The 100K hits/day figure is a conservative estimate, not a hard upper bound. SQLite has been demonstrated to work with 10 times that amount of traffic.
A toy that can serve the vast majority of DB use cases. I get it, you can't build a massive-scale project with SQLite, but that doesn't exactly make it a toy DB...
Does your "Careers No Reply" email send auto-rejection messages?
I applied for the Senior Android dev role around 5 weeks ago and got a rejection message 11 days later, so I'd like to know whether there's any point in re-applying now.
In most modern economies fiat is backed by the 'full faith and credit' of the issuing government, which requires more young people paying into the pension system than retirees drawing from it. That's as clear an example of a Ponzi scheme as can be imagined, albeit moving on a slower timeframe than we usually think of such things working.
Fiat is backed by the insistence of the issuing government that you pay your taxes in that denomination. It has very little to do with pension systems, except to the extent that the government runs those also denominated in dollars.
But the US could end social security tomorrow and as long as it still required taxes and tariffs in the form of dollars, the dollar would still have value.
Zimbabwe required taxes and tariffs in the form of Zimbabwean dollars... You need a little more than just taxes and tariffs for a fiat currency to have value... You need a hard money that is not going to be devalued also. This is where all fiat falls short and has done since the demise of the gold standard.
Raw fiat is NOT a new experiment, the Yuan dynasty in China printed paper money in the 13th century, not backed by any precious metal or commodity. They printed too much and had inflation problems, so that's not a new problem either.
You could say Ukraine has Russian roots in that it split off of the Russian Empire and then the USSR. You could also say Russia has Ukrainian roots because that was the historic domain of the Kievan Rus.
Similarly, you could say Bulgaria has Russian roots because it gained its independence from the Ottoman Empire in the 19th century in the wake of the Russo-Turkish war. Alternatively, you can say Russia has Bulgarian roots in that Cyrillic was invented in Bulgaria in the 9th century and spread to other Slavic cultures.
The bottom line is that Eastern Europe and Russia have, for better or for worse, strong historic and cultural ties.
My point was more that if Google can do it, other manufacturers can do it.
The issue with other manufacturers is that they concentrate a lot more on features that are visible to users whereas features like these aren't necessarily visible directly to the user and aren't given attention even though they're possible to implement.
(Taken from https://www.sqlite.org/whentouse.html)
A toy that can serve the vast majority of DB use cases. I get it, you can't build a massive-scale project with SQLite, but that doesn't exactly make it a toy DB...