Diggsey

40 ms·

361.
by Diggsey 6y ago
It may be that viruses are simply less of a concern: perhaps at that depth viruses have difficulty surviving outside of a host and so can't spread very easily? It could even be that they lost their immune systems first due to a lack
362.
by Diggsey 6y ago
One thing omitted from this article is that it's not only the physical hardware that may (effectively) re-order operations. The compiler may also perform these re-orderings. The compiler's re-orderings will always be valid accordi
363.
by Diggsey 6y ago
> I'm going to work to listen to them and talk with them one by one until i do understand on a core level how they feel and where those feelings are derived from, Many of the people who are actually condemned for being offensive are
364.
by Diggsey 6y ago
Was the C Raft implementation in use a pre-existing library, or was it developed specifically for Redis-Raft?
365.
by Diggsey 6y ago
It would be tricky: constraint solving is a single-threaded algorithm, so the best option might be to run the broad-phase, and then break the scene down into islands of disconnected bodies for parallel constraint solving. The problems are t
366.
by Diggsey 6y ago
Not sure what you're using - rust-analyzer does support format-on-save (in fact it's actually a VS Code built-in, rust-analyzer just exposes a formatter for Rust files that then gets used by the built-in format-on-save feature) Al
367.
by Diggsey 7y ago
Instead of sending traffic anywhere, why don't they have the destination address first send a (slack-authenticated) request to the TURN server saying "I'm happy to receive traffic from [SOURCE]" and then a temporary wind
368.
by Diggsey 7y ago
Maybe part of developing a standard should be developing and maintaining test and validation suites for that standard...
369.
by Diggsey 7y ago
Yes, but it requires explicit support and is very platform-specific.
370.
by Diggsey 7y ago
Yes, as I mentioned, if you include an incrementing counter within each block then the data does not repeat. The data only needs to be non-repeating within a single stream. Different streams will use a different IV and possibly different ke
371.
by Diggsey 7y ago
Many of the alternative modes are unsuitable for this case, as it is being used to encrypt UDP packets which may be lost. There are two commonly used modes which support the random access needed here: - ECB - CTR Note that CTR is still reco
372.
by Diggsey 7y ago
Wow, it's totally dead, not even a read-only view.
373.
by Diggsey 7y ago
If one is to believe their blog post ( https://blog.zoom.us/wordpress/2020/04/01/facts-around-zoom-... ), then they do in fact use end-to-end encryption: > To be clear, in a meeting where all of the par
374.
by Diggsey 7y ago
This is rubbish. The bug exists in LLVM regardless of whether Rust has its own fork, and you don't even need to use Rust to reproduce it. Furthermore, using your system (ie. unmodified) LLVM with Rust is supported, and still exhibits t
375.
by Diggsey 7y ago
> People tend to be pretty accommodating when it comes to letting you give them money. Not really. A huge amount of charity money supposedly going to the poor in other countries is actually used to bribe officials in those countries to a
376.
by Diggsey 7y ago
Great article and I agree with all of the criticisms. There is a big problem with internet standards where the "division of thought" leaves a gap in the middle. The standard author thinks "I am just designing a template for p
377.
by Diggsey 7y ago
There's a lot of vibration, but the G forces are not that high, and they are particularly low during launch. The highest G force is right before the main engines cut off, once the rocket is already in space, at which point you presumab
378.
by Diggsey 7y ago
Maybe you just miscommunicated, but you absolutely can use generic parameters in a return type: https://doc.rust-lang.org/nightly/std/iter/trait.Iterator.ht... ... and `impl Trait` exists to be able to have
379.
by Diggsey 7y ago
This is still poor design. I never had this issue with the previous Micro-B ports, presumably because of the tiny hooks on one side. Does anyone know why those were ditched? If you want to keep it symmetrical you could put them on the insid
380.
by Diggsey 7y ago
Actually, the parking_lot mutex is fair: https://docs.rs/parking_lot/0.10.0/parking_lot/type.Mutex.ht... The high waiting variance is because the benchmark randomly decides which locks to take, meaning that t
381.
by Diggsey 7y ago
As bad as management can be, you can't entirely shift the blame from the developers. Having a good issue tracking system is addressing the symptom, not the cause. If the developers are writing software with these kinds of fundamental b
382.
by Diggsey 7y ago
The article explains that the heat transfer is too great to be explained by the black body radiation for the given temperature. It would be interesting to know how they think the heat is being transferred: are the two plates exchanging elec
383.
by Diggsey 7y ago
Given two snapshots of the schema, there are multiple paths from one to the other. This makes it impossible to generate perfect migrations from the snapshots, you always end up needing manual changes. You could make it easier to see the c
384.
by Diggsey 7y ago
You're misunderstanding the bug. In the end, the number will be displayed to one decimal place, eg. "1.1 MB" or similar due to the "%.1f" format specifier. If the input is 999999 bytes, the loop will see that it is
385.
by Diggsey 7y ago
No, it doesn't. It has the exact same rounding bug described in the article. The article even mentions: > FWIW, all 22 answers posted, including the ones using Apache Commons and Android libraries, had this bug (or a variation of it
386.
by Diggsey 7y ago
It doesn't. This is just showing the normal way that callbacks are implemented in vanilla C and how you would make that programming pattern interoperate with Rust closures. Neither one relies on the compiler trickery/runtime code
387.
by Diggsey 7y ago
That is a very neat solution. The one downside I see is that you need to be much more careful about gracefully handling errors within workers. For example: if a single worker thread crashes but the process doesn't realise it, it may be
388.
by Diggsey 7y ago
I have also found the lack of transactional guarantees in typical job queues to be very problematic. One problem with using PostgreSQL in this way (using either advisory locks or LOCK FOR UPDATE) is that it requires you to keep an open conn
389.
by Diggsey 7y ago
This is not remotely true. You can do this with pretty much any database that supports SERIALIZABLE isolation-level transactions correctly. The point is that application code has bugs, and it's a lot easier to specify your constraints
390.
by Diggsey 7y ago
The argument made in the thread is that someone could be pressured by the foreign government into leaking sensitive information. Where an employee's family lives seems like the single most important point to consider...

More ›