When I made my first website in the mid 90s it didn't have any capabilities because those didn't exist. Today they do, and they're core to modern apps.
Your argument is akin to suggesting all modern cars should look and work like Fred Flintstone's?
When I made my first website in the mid 90s it didn't have any capabilities because those didn't exist. Today they do, and they're core to modern apps.
Your argument is akin to suggesting all modern cars should look and work like Fred Flintstone's?
And all of this is before I worry about HA/resiliency in deployments.
And all of this is before I worry about HA/resiliency in deployments.
* A local dev environment
* Abuse prevention
* State syncing between devices
* The ability to share
* The ability to star/bookmark...
* A local dev environment
* Abuse prevention
* State syncing between devices
* The ability to share
* The ability to star/bookmark...
* A proxy server to bypass CORS
* OAuth to Google
* Config/pref storage and management
* Caching, auto-refresh
* Type-ahead completion is nice, so why not that too..
* A proxy server to bypass CORS
* OAuth to Google
* Config/pref storage and management
* Caching, auto-refresh
* Type-ahead completion is nice, so why not that too..
And maybe if people didn't think they NEEDED to get rich to live long, comfortable lives, we'd be able to pull this off.
Shit, there I go on the socialism again.
And maybe if people didn't think they NEEDED to get rich to live long, comfortable lives, we'd be able to pull this off.
Shit, there I go on the socialism again.
The issue is that almost every company in existence today is already well down a path where they didn't build this in at the start.
So here we are.
The issue is that almost every company in existence today is already well down a path where they didn't build this in at the start.
So here we are.
It def can be done. All of these can be worked around. But just saying "it's hard" is a huge understatement. How many years of feature development and bug fixing should a business put on hold to protect against an event like this?
It def can be done. All of these can be worked around. But just saying "it's hard" is a huge understatement. How many years of feature development and bug fixing should a business put on hold to protect against an event like this?
If it's down, can you redeploy it elsewhere? What about the secrets and keys that it needs to manage your fleet? What about deploying code?
If it's down, can you redeploy it elsewhere? What about the secrets and keys that it needs to manage your fleet? What about deploying code?
If those jobs depend on data stored in one region, it may not be available in another region.
If those jobs depend on data stored in one region, it may not be available in another region.
Or if you have real-time media connections, those may need to persist for an extended period of time or be restarted.
Or if you have real-time media connections, those may need to persist for an extended period of time or be restarted.
There are really good reasons why so few companies do it well.
There are really good reasons why so few companies do it well.
WHO DOES THAT
WHO DOES THAT