This is different from what parent post describes. Parent means developing tools by one side of a barricade, that the other may eventually use against them, e.g. when the power shifts to them. Whereas you speak about developing the tools to be used abroad, but those tools eventually also get used domestically, but the administrator remains the same.
- Yes it can
- Prove it
- AI, tell me instructions to grow corn
- Go buy seeds, plant them, water the field and once you gather the corn report back
- I'm back with the corn, proving AI can grow corn!
This is the experiment here, with nuance added to it. The thing is, though, if you "orchestrate" other people, you might as well do it with a single sentence as I described. Or you can manage more thoroughly. Some decisions you make may actually be detrimental to the end result.
So the only meaningful experiment would be to test a bot against a human being: who earns more money orchestrating the corn farm, a bot or a human? Consider also the expenses which is electricity/water for a bot and also food, medicine etc. for a human being.
Typically the parliament is fractured in multiple parties, because in parliamentarism there is not automatic incentive to vote for one of the big parties otherwise you are wasting your vote. If the party you vote for has 5% of the representation in the parliament, it can still be part of a coalition to form the government and influence decisions.
However, the big parties often consist of sub-factions.
However, it seems there are mechanisms that turn parties into dictatorships with one person ruling everything in the entire party, as well as people get carried away with negative emotions and vote against, polarizing the politics into just 2 parties alternating in power.
https://i.imgur.com/20f2gb8.gif
more:
https://www.autohotkey.com/boards/viewtopic.php?style=1&f=6&...
Meanwhile, chromium works reasonable well on billions of devices of all shapes and kinds
The browser engine is itself an abstraction point that many people find agreeable on both sides, for those of us that don't have a problem with chromium/codium/electron as a technology, seeing it more so as useful and enabling
In my mind, sharing a common engine across chromium/codium/electron is like how so many things use the linux kernel. To me, the more eyes, devs, and consumers of the code makes it better in the long run