What do you think might be some better possibilities than the current mess?
855 karma · joined November 5, 2016
What do you think might be some better possibilities than the current mess?
This has evolved to the stage where it's endemic in what used to be well functioning societies, that day to day civic economic interactions are now broken, which is what the posted talked about.
The answer is regulating to avoid this race to the buttom.
I believe this is an economic race to the bottom and regulation is the answer to fixing it.
Here's the basis of an idea for how to fix the power dynamics so the market works properly
1) an ombusdman that can fine companies for user abuse of wasting user time, and redistribute the fine to the users
2) regulations of how long a company can on average keep users on hold, such as no more than 10 minutes to speak to a human, otherwise the speak to a human option is useless as the company makes it take longer than the median user can afford
3) regulations of threshold of acceptable customer complaints against a company, otherwise the company will make the service operators unable to actually fix anything as you note
4) a process with the ombusdman where when the number of complaints exceeds a threshold the company is fined and the fine distributed amongst the complaining users
5) some sanity check here to prevent user abuse, such as checking the average wait times, and confirming the customer service actually never fixes issues from a number of tests. The tests could be made in collaboration with a subset complaining customers.
Clearly companies are en masse externalizing the costs of support onto users, and plainly not supporting users in fixing real problems with systems that are now required to live in society. It's at the stage where it's breaking our well functioning civil society and turning the first world into a third world kafkaesque dystopia.
I believe this is an economic race to the bottom and regulation is the answer to fixing it.
Here's the basis of an idea for how to fix the power dynamics so the market works properly
1) an ombusdman that can fine companies for user abuse of wasting user time, and redistribute the fine to the users 2) regulations of how long a company can on average keep users on hold, such as no more than 10 minutes to speak to a human, otherwise the speak to a human option is useless as the company makes it take longer than the median user can afford 3) regulations of threshold of acceptable customer complaints against a company, otherwise the company will make the service operators unable to actually fix anything as you note 4) a process with the ombusdman where when the number of complaints exceeds a threshold the company is fined and the fine distributed amongst the complaining users 5) some sanity check here to prevent user abuse, such as checking the average wait times, and confirming the customer service actually never fixes issues from a number of tests. The tests could be made in collaboration with a subset complaining customers.
Some of the camera companies even did revenue share omg
It used to be so consistent and poweruser friendly.
Windows 11 has just broken a lot of the poweruser keyboard shortcuts for doing things, on top of all their ads, nagware, telemetry/stalking and various antifeatures, it's like they are begging power users to go to Linux.
However on desktop where power usage isn't an issue, Intel 12th gen performance has pulled ahead of AMD. Theoretically even on laptops too but I suspect they have the common problem of powerful Intel cpus in laptops where they cooling just can't hack it and they throttle to make it worthless getting top end Intel. So I believe AMD is still better on laptops presently.
Mixing state between a bunch of different backing stores, or not making in memory data structures explicit, makes data structures harder to discover, but what does that have to do with OOP?
That means that the AWS service based option costs 33 times more. Not ten time more, but thirty plus times more.
I've worked on multiple systems with around 50 developers contributing fulltime to them, very practically.
Fault tolerance again is largely orthagonal to ms. It's a matter or system architecture, see the point above. e.g. A common situation where service one depends on availability from service two, having them as seperate ms doesn't help, what helps is architectural design to keep service two useful somehow regardless, and this is orthagonal to if the services are in process or done as ms.
Scaling is a whole other discussion, and microservices can have good impact here, but so can other techniques.