capitol_

It happened in the lexical-core crate somewhere in 1.5X. Here is a bug report I got about it with compiler errors listed: https://github.com/cortex/ripasso/issues/219

It's not two if you need curl. Curl have a large number of dependencies, only difference is that it's visible with npm.

There is a lot that you can do, pointing out a single manager as scapegoat for systematic failure won't solve anything.

You can make sure that the incentives in the organisation aligns with preventing deaths like these.

You can educate your workforce.

You can hire more people.

And so on.

Lifetimes in rust fits this, they are sort of types.

Because opinions are not all equal, some are better and some are worse.

Even if both antivaxxers and doctors have opinions on if people should get vaccinated it would be insane to treat them equally.

Wet bulb temperature is not the same as average temperature. See https://en.m.wikipedia.org/wiki/Wet-bulb_temperature

Thinking that cutting federal spending would impact those kind of untouchable agencies instead of softer things seems very naive.

I would say it's quite wrong to think of crypto as some sort of stock.

Stocks are ultimately anchored in a company, and it's ability to pay dividends to it's owners. The historical average of the value creation for S&P 500 for dividends are about 40% so it's not an amount that can be disregarded.

Since crypto doesn't have any similar mechanism, and all of the value is instead tied to what other persons want to buy it for, I argue that it's better to compare it to an online casino rather than an stock market. That would be more fair for those that are new to investing.

This makes no sense to me, why is $100 different than a threat to the wife?

Is it because the amount of money is too low?

There is always statistical outliers in any large data set, but they don't affect the median value significantly.

I see no good way out of this, if someone forks it and removes all that extra attack surface I guess Moxie will fight it, as he doesn't want many compatible clients.

And if the crypto features stays in there it will become another avenue for pump-and-dump schemes, so I can no longer recommend it to people without looking like a crypto hustler.

But here you are comparing apple and oranges.

The energy one technical component uses versus the energy that all the people that use another technology uses.

Bitcoin also have support systems around it, hardware production lines, and a lot of people who use it that you don't include in your comparison.

I remember one of those exchanges, two people waged money about compressing random data so that the data + decompress program would be smaller than the original data.

The other guy came back with a program that moved some of the random data into the metadata of the filesystem, in such a way so that the produced files did indeed become small enough.

Don't know if the other guy ever paid out.

This is a really horrible statement about why we don't pay scientist a fair wage for their work.

I really hope that at some point in the future people stop internalize this sort of abuse regarding their careers.

This seems like an unlikely claim, do you have any numbers to back it up?

If having memory errors being compile time errors instead of runtime error leads to more logical errors due to complexity. Wouldn't that imply that using other types of complicated checkers also leads to more logical errors, for example static analysis software or valgrind?

Here in Norway the register of who operates a company is public information in Brønnøysundregistrene [1]

It's convenient but it also generates a huge amount of telephone spam and fake invoices fraud attempts. So I could see the argument of keeping that information private.

I still think that it's better to have it public, but it generates some additional problems that needs to be handled.

1: https://www.brreg.no/

I'm not that sure on how an adoption rate of 30-35% speaks for itself?

https://www.google.com/intl/ru/ipv6/statistics.html#tab=ipv6...

Maybe you mean that the increase in adoption is too slow, and I agree to that, but change always takes more time than we want, specially when there isn't clear financial incentives.

You mean that it's insurance fraud?

Wouldn't it be more effective to burn the restaurant down if you wanted to do that?

One thing of roughly this nature is that a lot of rust code that I have read have their own types for iterators of objects.

For example, in the git2 crate there is both:

https://docs.rs/git2/0.13.12/git2/struct.Branch.html

and

https://docs.rs/git2/0.13.12/git2/struct.Branches.html

Where Branches implements Iterator.

It also complicates the bootstrapping process, sometimes significantly.

I understand that it's important to eat your own dog food, in order to experience the pain points yourself. But sometimes people think of self hosting as a symbol of something (pride maybe), and that's the wrong way to approach a programming problem in my opinion.

+1 on avoiding yaml, it becomes horrible to maintain when the files gets big

No, this is not a very good suggestion. gpg-me just wraps the gpg binary and relies on a lot of global state, environmental variables for example.

This makes the library really painful to use in multithreaded contexts, or when you need to have a controlled env. (like unit tests).

I use gpg-me in one of my projects, and it's very far from pleasant to use.

Hashing email addresses doesn't really work. Most people don't use unique addresses per service and its easy to get a large list of email addresses that you can hash and do lookups in.

This is one of the biggest reasons that I follow our governments recommendations on travel, working from home, masks and so on. There is people that have it as a full time job to calculate these risks and produce recommendations for the rest of us.

This sounds great, I added support for signing git commit's in git2-rs and would be happy to try to do something similar in gitoxide if I start to use it.

I'm currently using https://github.com/rust-lang/git2-rs to interact with git in my software. Are you aiming to have a stable api that could act as a pure-rust replacement for that at some point in the future?

I guess that the docker image doesn't use TLS for connections, or if it does it doesn't use certificates from a CA.

This means that your data either goes in plain text over the network, or might be vulnerable to a MITM attack (if you don't manage your certs correctly).

I also guess that you don't use SCRAM as the password hashing method, but rather MD5. That means that if someone is able to listen to the connection, they can do a replay attack using the password hash, as there is only 32 bits of entropy added to the hash from the server side. And once you have managed to do the replay attack you can issue arbitrary sql commands as that user.

The IdeaPad S540-13ARE is spec'ed with a 2560x1600 screen: https://psref.lenovo.com/Product/IdeaPad/IdeaPad_S54013ARE

But seems very hard to find a place that actually sells it around here (Norway).

The incompatibility was very much intended, Sun needed a way to compete with linux and didn't want to be assimilated into the linux ecosystem, so they released opensolaris under CDDL instead of GPL or MIT. Oracle haven't re-licensed it for their own reasons.

Here is some more info on the subject: https://sfconservancy.org/blog/2016/feb/25/zfs-and-linux/

This is a quite hard question to answer, as if it's done correctly no-one will know and the person will simply vanish.

And there is of course countless reasons why someone vanishes, but then again, there is a lot of missing people: https://www.statista.com/statistics/240387/number-of-missing...