4,052 karma · joined September 25, 2014
They could’ve done the Either type which would’ve been more correct or maybe EitherT (if the latter is even possible)
https://hackage.haskell.org/package/oneormore or scala: https://typelevel.org/cats/datatypes/nel.html
it's for type purists, because sometimes you want the first element of the list but if you do that you will get T? which is stupid if you know that the list always holds an element, because now you need to have an unnecessary assertion to "fix" the type.
See here for the details: https://openprinting.github.io/achievements/#cups-upstream-h...
Also as long as you don’t use it to curl random things the security impact is not that high and I doubt that there a tons of uses for that.. you probably won’t attack yourself?
People are angry about minio , but that’s because of their rugpull.
I mean yes you can build it with native interop and aot. But then you would loose the .net benefits as well.
Why? Why do some databases do that? To have better performance in benchmarks? It’s not like that it’s ok to do that if you have a better default or at least write a lot about it. But especially when you run stuff in a small cluster you get bitten by stuff like that.
> Off-site replication of guests for manual recovery in case of datacenter failure.
which would've been an actual killer feature
The one demanding it is the maintainer of keepassxc it would’ve been better to just close the issue that this is a Debian only problem and he should install it like that and just close it.