> The issue isn’t what can be done in PHP, it's what PHP encourages by default:
Lets break this done.
> global state,
PHP is stateless.
> poor encapsulation,
Encapsulation in PHP is mostly consistent with Java.
> inconsistent APIs,
PHP is written in C and an original design decision by those C programmers was to make the APIs consistent with libc.
> and difficult-to-enforce discipline.
Its very easy to enforce. All modern projects would run tools like Pint, Phpcs & Phpcbf to enforce their code standards and preferred style in their CI Pipeline.
1. When you say 'Our Partners' invest the money - who are they? Are they US entities and/or how often are you and your partners audited? Will you and your partners make those audits public? I think that would be a selling point over the other stable coins.
2. You say that I can _always_ redeem my $1 Glo Dollar for $1 USD again. But if you're buying US Treasuries - only a few can redeem it when they want no? Others will have to wait for the bond to mature to get their money out. What percentage of reserves are kept in cash vs assets?
3. You don't mention how much basic income my $1 USD in your example above will generate. How much _good_ can I expect to generate with my $1?
4. Swapping $1 USD for a unit share of some US Treasuries seems like a simple transaction that would get played out millions of times everyday. Where does the crypto play fit into this?
> Brale initially retains 100% of the earnings on the first $2M of assets backing the Glo Dollar.
While trying to find these answers I noticed this statement at the bottom of your website. That's quite murky and I think you should mention that up front.
It means Binance is running low on USD reserves and is buying more by preventing large USD outflows while continuing to allow USD inflows.
It's worth noting that Binance operates BUSD, a stable coin pegged to USD which according to their website saw a 25% reduction in net asset reserves between Nov 2022 to Dec 2022 (https://www.binance.com/en/busd) - if that trend has continued that may be why they need a short-term supply of USD.
It sounds like you might benefit from AWS Beanstalk which feels like a configuration widget built on top of CloudFormation - https://aws.amazon.com/elasticbeanstalk/
Choose your stack and beanstalk deploys to a load balanced, autoscaling group in your VPC. You can attach a RDS when you choose your stack. And all resources can be managed separately or through CloudFormation. Beanstalk also supports container deployments.
From the website > "You can simply upload your code and Elastic Beanstalk automatically handles the deployment, from capacity provisioning, load balancing, auto-scaling to application health monitoring. At the same time, you retain full control over the AWS resources powering your application and can access the underlying resources at any time. There is no additional charge for Elastic Beanstalk - you pay only for the AWS resources needed to store and run your applications."
There are currently 900 blogs in the index. Every blog is manually reviewed, so this number will grow slowly and steadily over time, until I maybe automate things.
Lets break this done.
> global state,
PHP is stateless.
> poor encapsulation,
Encapsulation in PHP is mostly consistent with Java.
> inconsistent APIs,
PHP is written in C and an original design decision by those C programmers was to make the APIs consistent with libc.
> and difficult-to-enforce discipline.
Its very easy to enforce. All modern projects would run tools like Pint, Phpcs & Phpcbf to enforce their code standards and preferred style in their CI Pipeline.