pepoluan

It's basically saying, "I bear no responsibility whatsoever if this program messes up your system. It's not even version 1!"

I usually get back at them by saying something like, "When you have experience as much as I do, sometimes my subconscious mind will recognize patterns that will drive my decision. You may call it 'gut feeling', I call it autonomous decision weighting using experiential pattern matching. And there's no shortcut to that ability; you just have to have decades of experience. Which I do."

This is why I always pre-download pr0n well-ahead of jack0ff time.

Call it BBP Protocol... "Blue Ball Prevention"

This is an "old" publication. Are there newer analyses?

It's a great device.

For me _personally_ I much prefer my coffee to be "kopi tubruk", though: Pour boiling water over medium-ground coffee.

Might not be for everyone, but that's what's great: There is no one 'correct' way to do it. There are tradeoffs and you choose which tradeoff you want.

Reminds me a bit of Citroen DS, which was also revolutionary aerodynamic. Yet practical. And VERY popular.

Here's a video about the DS's aerodynamics: https://www.youtube.com/watch?v=iD1_WQQAwzw

A comment on the meta-article: The presentation is ... unique. But very easy to digest. I might be tempted to apply same "story flow" in my articles.

For spaceships, I think it's a given that launch should be automated; too many things happening rapidly to be handled by human beings. In space, though, actions are more forgiving to a certain degree, timing are usually more relaxed.

That sounds more like a failure of UX engineering/design.

That's why rapid iterations are better when developing a user-facing interface.

"You were so preoccupied with whether or not you could, you didn't stop to think if you should."

So that was an interesting experiment, but I'm not really sure if that's a good idea. Anyone wants to enlighten me on that?

To put it in a nutshell: Criticism should be put forth in a "let's get this to work, together. Failure should not be feared; it's another data point" mindset.

I don't mind criticism, as long as it's constructive and not for the sake of bringing down someone.

"I did not see you considering X factor, do you think its impact will be insignificant" is a helpful, constructive criticism.

"This will not work. You're stupid to pursue this, pursue something else likely to succeed" is not.

I disagree with Ford's principle of "not logging failures". The key is to log _in_detail_ ... the setup, the materials used, the failure, and most importantly, how and why it failed.

If someone else wants to try, they can see that if they try the _exact_ same way they will end up with failure. But they can -- and should be encouraged to -- try with changes to the variables.

Huh. TIL.

I usually just do `sudo zsh` :-)

"WooHoo" ... I thought it was about The Sims...

Sorry if this is tangential, but I just love this discussion. Rather than debating about things, this discussion thread is full of informative tidbits, and fond (or not so fond) reminiscences of image decoding programming.

Then you just calculate them all.

If Branch A is taken ... total X clock-cycles.

If Branch B is taken ... total X clock-cycles.

If Branch C is taken ... total X clock-cycles.

And so on. And then make sure that the "longest" branch fits into the clock-cycle budget.

> People who are in the top 1% of technical skill will do that. Not "the rest of us".

That means it's not 100% guaranteed one will be locked out, _provided that_ one has the tech chops. Even with such condition, is enough to totally invalidate your statement of "100% guaranteed you'll be locked out".

You probably should change your statement to say "99% of people (i.e., those withiout tech chops) will very likely -- or almost certain -- to be locked out sometime in the future". Now that new statement will be true.

This is the "killer feature" of Firefox, IMO. No other browser does what Firefox does w.r.t. containers.

> I guess tech savvy people are using android emulators on their PC to run google authenticator

I simply use Authy instead of Google Authenticator. It has a desktop app that syncs to the Authy app on my phone.

With Windows 11, you'll soon be able to run Android apps without needing to install an Android emulator, but that's not here and now, though...

> USB A is no use for a USB C MacBook for example

You can always buy a USB-A-to-USB-C adapter/converter. They are available everywhere, inexpensive, and if you're afraid it will be misplaced, there's always the option to glue the USB A key to the adapter...

> I suspect a lot of trading signals were lost this way.

If you can prove & show evidence about this, I'm sure they will (grudgingly) accept the need to improve.

Financial institutions are mostly risk-averse, "if it works, don't fucking fiddle with it!" They need something that will impact the bottom line in an (almost) direct way.

I remember working with a financial institution back in 2010. I pushed for virtualization by presenting scenarios where the main servers are impacted, we have no warm backup servers, and calculate the impact to bottom line using known MTTR (Mean Time To Recovery) values of similar scenarios (gathered from incidents all over the world).

Took several back-and-forth meetings with the BoD, but in the end they accepted the need to improve and allocated the funding + greenlight the project.

(That was also back in the day when Microsoft had just released Hyper-V, and when we asked Microsoft to join in the project, I talked to their head engineer, and they respectfully declined because "their internal testing shows that Hyper-V, at the moment, is unable to fulfill the required parameters". Ended up with XenServer.)

That reminds me of Sabaton.

In a way, Sabaton can be considered to the modern-day bard, singing in Metal.

I use "UVIMate" app to provide a general ballpark figure on how much time I should spend under the sun:

https://play.google.com/store/apps/details?id=au.com.aershov...

When the "bradykinin storm" hypothesis [1] was postulated, I already guessed that D3 would be a potent suppressor of Covid-19 mortality & likely prevention of the "Long Covid" syndrome.

Glad to see my guess is validated.

msgpack comes to mind...

Well, the page for MeowHash is written in 2018.

xxHash Performance Comparison page is last updated in 2021, and in that page XXH3 is faster than MeowHash:

https://github.com/Cyan4973/xxHash/wiki/Performance-comparis...

CRC32 is actually very slow in modern CPUs. So if you can use an algorithm that is both (1) faster and (2) better quality, why not use that algo instead?

xxHash is not really "new", it's been available since 2014. At least, that's the oldest Python bindings available on PyPI:

https://pypi.org/project/xxhash/0.0.1/

Sure, as it developed, xxHash variants appear. The latest in the family is XXH3 and it's already being used at least since 2019:

http://fastcompression.blogspot.com/2019/03/presenting-xxh3....

And what's wrong with xxHash?

According to xxHash's performance comparison page, xxHash is faster than MeowHash.