This runs a NodeJS server and frontend in your browser so you can see what Graphweaver can do without having to install or run anything more than a browser on your computer. The example has an SQLite database joined to a REST API. Graphweaver serves a GraphQL API with the result.
Yeah, it's all fun and games until you're at Macca's and someone says, "Oi, can you pass me a chippy?" and they get real confused when you go find a carpenter.
fast.com checks the speed to Netflix servers. So if they juice that, they also have to juice Netflix streaming speed unless they've figured out a clever way to fingerprint just fast.com traffic over HTTPS.
I can't use another company's GPS system in my car, so in the market of, "Using GPS navigation / menus / etc in my 10 year old Mini's dashboard" there's no meaningful competitor. They charge for map updates and everything.
At some point a company is just building a feature, and they're not required to make every single feature accomodate every other manufacturer's competing version of the feature. I knew I was buying the Mini system when I bought the car, and I accepted it. Same is true for iPhone users.
I'd say you lobby for preferential voting like we have here as the first step. You write numbers in boxes for your 1st choice, 2nd choice, etc until you're done.
They put all the ballots in piles by everyone's first choice. The smallest pile (e.g. least voted for candidate) then loses, and their ballots get sorted onto their second choices. Repeat until you have a candidate with a clear majority, and you have a winner.
This allows people to say, "I want Rubio, but if not, then Cruz, and if not then Jeb" etc. I suspect if this system were in play in both parties now, we'd have different nominees, and they'd be the candidates that the majority can live with instead of being the candidates that most excite the extremes. And the people on the extremes can see that their candidate lost even with people being able to vote for them without 'wasting' their vote.
Yes, in our senate this gets a bit crazy with tablecloth sized ballots (https://upload.wikimedia.org/wikipedia/commons/a/aa/Victoria...), and the first time I voted here I allocated every single preference down to about 160 something with pride. You don't have to obviously, but I chose to.
I'm from the US, moved to Australia and am now a dual citizen.
I think the reason for this here is because we have preferences in our voting, and we have compulsory voting. I can say, "First the communist, then the gun people, and if neither of those, finally go for a major party." if that suits me. That means our voices get heard, and the major parties listen.
In NSW government for example we had an unpopular law put in place that killed our nightlife, so an entire political party was created just to fight that one law. They got lots of first preference votes, and the votes for all who did that were routed back to candidates that actually won because of the preferences. Being able to allocate our votes back to major parties with our voices being heard is important. Liberal then realised this wasn't a hill they were particularly keen to die on, so they repealed the law. (https://www.timeout.com/sydney/nightlife/keep-sydney-opens-o...)
Also, compulsory voting means that everyone is going to vote. They have to by law. So there's no need to stoke the base to get turnout. Stoking the base makes you scary to everyone else and you get the smack down at the polls for it.
We currently have Greens members in our house of reps, and many many 3rd party candidates in the senate. It's nowhere near perfect, but having your voice heard clearly, having that reflected in law, and ensuring there's no apathetic middle that lets the extremes dictate policy cuts the crazy right down.
This runs a NodeJS server and frontend in your browser so you can see what Graphweaver can do without having to install or run anything more than a browser on your computer. The example has an SQLite database joined to a REST API. Graphweaver serves a GraphQL API with the result.