826 karma · joined April 14, 2021
Hard disagree here. "Let's do/not do this, in case we decide to change databases in the future" is one of the greatest lies we tell ourselves. You're just making your life harder now and in the near future, for the nebulous promise of "seamlessly replacing your database backend if needed".
In 95% of cases, it's not needed, and you're getting all of the downsides for no benefit. And if it's needed in a late stage of your application's life, changing a bunch of SQL functions will be just one tiny problem among many bigger ones.
I'm just saying that, if the goal is mainstream adoption, the core team should acknowledge that people will use Nix as a means to an end, and not for the sake of using it as they do.
99.5% percent of people don't use Docker because they have a passion for writing dockerfiles, or because they find the ideas behind Docker elegant. They use it as a tool to help build other things. Meanwhile, the Nix community keeps pushing out these ideas about how Nix _works_ ("reproducible builds!", "lazy evaluation!") but they don't seem to particularly care about making Nix easy to use for the majority of the population out there who may want to use Nix as tool and don't care about its technical merits.
On top, I think most projects would benefit from having more functional programming advocates in them. Nix suffers from the opposite problem: it would benefit from having _less_ passionate FP people in it. Nix the language is pretty inscrutable for lots of people.
I've been hearing this for the past 5 years, yet nothing of practical use based on blockchains has materialized yet.
Not everyone can or wants to go to VATSIM for realistic ATC coverage, but the default one is just dreadful. Obvious phraseology mistakes, happily vectoring you towards terrain, asking you to descend 20k ft. in 2 minutes, and the only way to communicate with it is via a list of pre-determined options.
Plus, people are becoming aware that plastic containers suck and they prefer buying glass container for home use, since they're easier to clean and don't get permanently stained.
Hell is full of single-implementation abstractions.
You can do the exact same thing in Rust:
impl Coin {
fn valueInCents(&self) -> u8 {
match self {
Self::Penny => 1,
Self::Nickel => 5,
Self::Dime => 10,
Self::Quarter => 25,
}
}
}It's a pretty straightforward logic.
> You would have numerous problems implementing this system across a country with 4 primary time zones(lets ignore the lone two states with separate time zones for now).
You have mentioned timezones twice but haven't really explained why or how they would be an issue. Spain has two timezones, early results are withheld until polls close in the westmost timezone. The EU spans across multiple timezones as well, and elections to the European Parliament follow the same principle.
> Lets set aside the issues involved with transmitting data electronically (sounds like just a distributed electronic system).
Data is transmitted electronically and made publicly available on a per-ballot-box basis. Representatives of political parties with obviously competing interests are present during the counting process (and any member of the public who wishes to can attend it as well) and keep their own tally. If they find out that it diverges from the published results, they can ask for a re-count, which is possible because the physical votes are preserved. In fact they are treated as evidence and follow proper chain of custody by the national police.
> What are you talking about? The last several elections were typically decided within 12-24 hrs of the polls closing on the east coast. Where are you getting your "days" from? Maybe you are just reading Spanish news that is days behind in covering American news?
I distinctly remember live following the 2020 presidential election, going to sleep after all polls closed in the US, and waking up 8 hours later with the race still undecided. How is this possible with a fully electronic system? Why is it not near-instant? This is what I haven't understood yet and would love to be explained.
From Wikipedia (emphasis mine):
> On the morning of November 7 at approximately 11:25 a.m. EST, roughly three and a half days after polls had closed, ABC News, NBC News, CBS News, the Associated Press, CNN, and Fox News all called the election and Pennsylvania's 20 electoral votes for Biden
The trick is using a distributed system. Each ballot box is opened, counted and tallied at the same time. The results (along with the votes themselves for posterior re-counting if needed) are sent to local electoral authorities who input the updates into a central system in real time. It essentially takes as long as it takes to count the fullest ballot boxes in big cities.
Funny that you mentioned speed as an argument for electronic voting, though. I never understood how the US uses it, yet it takes them days to get the full results.
The biggest issue was validation. We could get a system to spit out possible research directions automatically, but who decides if they're reasonable and/or promising? A human, of course. Moreover, we gave different humans the same set of hypotheses to validate and they came back with wildly different annotations.
This is so spot on it hurts. The acknowledgements in my own thesis were drafted and re-drafted over and over in my head for months, and then written down the day before submission.