Rarebox

If one lidar hits another, it will result in at most one bad reading (perhaps a bad column?). This can likely be filtered, or a bad scan (360deg) can be altogether rejected and the data predicted using models based on past sensor readings.

That's a pretty good example. The summary is actually useful, yet it still annoys me.

But I'm not usually reading the comments to learn, it's just entertainment (=distraction). And similar to images or videos, I find human-created content more entertaining.

One thing to make such posts more palatable could be if the poster added some contribution of their own. In particular, they could state whether the AI summary is accurate according to their understanding.

Interesting example! I've been learning AVX512 by using it to optimize Huffman coding. I found _mm512_permutexvar_epi8 and used it to do byte-indexed lookups, but _mm512_permutex2var_epi8 means I can get by with 2 shuffles and 1 comparison instead of 4 shuffles and 3 comparisons. In the end, on my CPU (AMD 9950x), changing to _mm512_permutex2var_epi8 only sped up compression by ~2%.

Compared to Huff0[1] (used by Zstd), my AVX512 code is currently ~40% faster at both compression and decompression. This requires using 32 datastreams instead of 4 used by Huff0.

[1] https://github.com/Cyan4973/FiniteStateEntropy

Also just stopped reading at that point. The idea seemed quite clever.

The peak of human civilization, before robots took over.

I could be wrong but I think many times the researchers don't care about the exact function. It could be something like 1/log(log(n)) .

https://yuri.is/not-julia/ is a good write-up of one person's opinion on the problems of Julia. I'm much less experienced with Julia but I somewhat agree. There's too much focus on "magic" instead of correctness for me to try building serious software using Julia. An amazing language in many aspects though.

He says he'll port his performance optimizations to the original game once he's done with his game / romhack. Otherwise he'd have to always update two codebases when he finds a new optimization.

Back then I remember switching to Chrome for these reasons:

1. Feeling faster than firefox (still does)

2. Process separation for tabs. Firefox used to crash the whole browser, whereas chrome would crash just a single tab.

3. Shipped with support for Flash and PDFs

Exactly. It could even be turtles all the way down, with new building blocks of physics becoming relevant as we go smaller and smaller (and back in time).

Would that be morally close to torturing an equally intelligent real worm?

It's jarring initially, but becomes natural very quickly. Writing loops like "for i in 1:length(arr) ... end" is pretty neat compared to C++ or even python. Plus in math sequences typically start at index 1.

It is nitpicky, but the fact that these classes deal with decision problems and not general problems is something which feels like should be mentioned more often.

Of course this ends up not mattering in practice since we can convert a problem with arbitrary (bitstring) output into a decision problem. To do this we just include a index n in the input and make the decision problem about whether the bit at given index n is 1.

This would make sense right? You probably can't run all cores at max turbo frequency before hitting power and thermal limits. So dividing chiplets based on binning would result in good performance for 1-8 -threaded tasks while reducing chip lottery.

(But it's possible there are other reasons for the discrepancy)

I thought google did this versioning thing for libraries before, but it was stopped for reasonable reasons (g3 components).

Basically if you could pin lib versions everyone would be stuck on old versions for a long time, causing difficult debugging work for each user of the library. You'd then also have all sorts of diamond problems: what if you want newest absl but older bigtable client?

It's a difficult problem no matter which way you go.

I can believe this. Around the time I left people were patting backs for fighting racism by getting rid of terms blacklist/whitelist.

Not something I feel super strongly about, but the fact that it's so scary to go against these stupid ideas is annoying. It's pure politics, there's nobody benefiting from this except the people claiming impact for antiracist work in their perf.

There's very little you need exceptions for with STL. Data structures, algorithms, etc. all work just fine without exceptions.

C++ without exceptions is great. Google doesn't use exceptions and they still use STL. Gamedevs usually don't use exceptions and they're fine. Just use some other mechanism for errors, like error codes, absl::Status, std::expected, etc.

You can buy drugs and other illegal things off the internet (tor), that's very useful for some people. Basically crypto allows for transactions that could otherwise be blocked or easily tracked by central parties (1). It can also be used to bypass gambling laws.

For legal purchases and activities crypto is useless, regular money is much more practical.

[1] depending on which crypto and how it's used tracking is possible, so care is required (especially) when converting dollars to crypto.

There doesn't even have to be a conspiracy for this to occur.

Companies always want to seem like the good guys, so they'll jump on any trend that doesn't hurt them. BLM, LGBTQ+ (), etc. are issues that companies don't have to lose anything to take part in. Advocating for (e.g.) unions is something the Amazons of the world don't want to promote. This creates bias on every level which suppresses topics that are inconvenient for the powers-at-be.

People fighting over race is very convenient for the 0.01%, so no effort will be made to end that fight.

( Not that these aren't important, just that there are important issues that are not discussed on the same level.)

Who are they asking for the data? ISPs, USA today, NSA?

To verify a single transaction, the network uses 1150kWh of energy which produces 550kg of CO2 [1].

[1] https://digiconomist.net/bitcoin-energy-consumption/

To discourage people from finding the box inside, we could insert traps to hinder explorers.

Youtube channel link: https://www.youtube.com/channel/UCPiQ_mEXdEbB-3Yhiq7gq5w

There's a lot of convenient new instructions in avx512 that can work on 128/256-bit vectors. I'm guessing that those wouldn't throttle more than regular avx.

WhatsApp would still be plenty incentivized to make their software secure. They understand that this wouldn't get rid of the exploit market, or state actors. I'm sure WhatsApp has been focusing a lot on security lately because of the brand damage.

Even if it wasn't effective in practice, entering this lawsuit can be seen as a message to users that WhatsApp is serious about protecting people's privacy.

Setting a precedent here might force remaining actors to stay shady instead of acting in the open, which would make it harder for them to operate (so they'd be less effective).

However, I have no idea what other consequences a precedent here might have. Definitely interesting.

Exactly. Having the experience of solving difficult algorithmic puzzles under time pressure makes parts of software engineering (writing working code, debugging) easier, so you can focus on the hard parts. Algorithmically, almost anything written in the real world is trivial in comparison.

Also note: The number of miles per intervention isn't a metric of AI driving skill, but of how safe the company is being to other road users.

I've experienced the same, although I don't think I stress out about flights anymore.

My theory is that it's caused by air being dryer in the plane, as my lips are usually chapped on/after flight.

The system is clearly not decentralized, if one organization can hold your funds for "misbehavior".

* science-based

* fetus

* transgender

* vulnerable

* entitlement

* diversity

* evidence-based