A lot of the reasons listed in this article actually made me shift from sophisticated ORMs like Hibernate back to a query based approach. A really nice framework for this (in Java) is jOOQ which gives you the possibility to write typesafe SQL via code generation.
https://www.jooq.org/
(I'm not at all affiliated with jOOQ - just a happy user)
Cool idea. I hope you somehow confirm the listing on the dashboard, otherwise someone can just list some domains under your username to cost you money ;)
There are a few consulting companies doing project work that hire a good amount of people. (However none are even close to you >100 / year number)
And also, it will be pretty hard to get near the 200k mark in Zurich if you're not at either a bank with a very specific expertise or at Google.
this is on a similar level of trust as the question about whether your paper vote is actually counted by some volunteer or just scraped.
But I agree, that e-voting systems require a high level of trust by the users but I would argue that it is comparable to the trust you need in letter voting. The main difference in my view is the authority is typically split between fewer people with an e-voting system giving a single person more potential influence when they abuse their power. (e.g. a single server admin can deploy a malicious version of the system rather than a person only having access to maybe a few thousand ballots)
I've been using Recharts [1] lately. It offers many different chart types and has a high level interface that makes it easy and quick to use for basic charts. If you want to customize you can still do so because almost every part of a graph is composable. (I have no affiliation)
(I'm not at all affiliated with jOOQ - just a happy user)