aaaronic

Jerk, Snap, Crackle, and Pop are the only ones I thought had agreed upon names. But my understanding is probably 20 years out of date at this point.

However, the paper says they’re not commonly taught, but jerk is taught in many high school (AP) Physics classes — we have to keep our balance by noticing the change in acceleration.

The GBA has native support for integer division, but it does not have any hardware support for floating point arithmetic at all — compilers will insert a virtual floating point unit that does IEEE 754 in software, which takes hundreds of CPU cycles for most operations. I believe the LUT you refer to is for floats.

I think the edge cases were entirely unclear in day 1, part 2. I had to redo it in a "dumb"/brute-force way to avoid using fancy regex tricks I don't know.

It's quite clear the small sample data was chosen intentionally to not cover them.

With the bug I saw years ago, just having certain accessibility features of the browser enabled _at all_ caused the bug (we were able to temporarily mitigate by disabling some obscure Edge accessibility feature via a launch parameter). So, my theory here is Grammarly is just enabling an optional accessibility feature in Chrome that has this bug when trying to "read" the gif.

This is _so_ familiar!

I have seen accessibility tools in Chrome lead to this kind of issue in the past with a dropdown menu -- to the point where it could be replicated with a miniscule amount of HTML. The particular bug I hit 2 years ago was in Chromium-Edge, but the symptoms and cause were very similar.

Grammarly almost certainly leans on some of the accessibility tools in Chrome. These tools are somewhat different in the various Chromium flavors (Edge, Brave, Chrome, etc.).

Probably the least crazy of his ideas.

With the runaway inflation there, I get why the idea seems like a good one, especially at first glance. I know the realities of such a change are pretty complex and nuanced and that doesn't seem like this new president's strong-suit.

The recent John Oliver coverage of Milei has me far more concerned about the social and environmental destruction and instability his leadership is likely to cause.

I sincerely hope he governs far better than I think anyone has a right to expect, given how he campaigned.

3+ body orbits can be wild!

It doesn't make any sense in a 2-body orbit (those are all conic sections).

I feel like I used to use a tool called Beyond Compare that presented _many_ different views of a diff (and even supported N-way diffs) back around 2012.

The "everything must be a SPA" mentality these days just saddens me. I get that GMail and similarly complicated apps get benefits from being SPA, but I've worked at too many places that just insist on a mess of complexity on the frontend when basic CSS / HTML (and maybe a sprinkling of JQuery) would give them all the same features in _WAY_ less time (and with significantly fewer bugs).

Web browsers in particular have become operating systems unto themselves. The "modern web" has so many features, often implemented in half a dozen competing ways... Just text rendering on modern hardware can be a HUGE lift.

Modern toolchains are all about "not reinventing the wheel" -- but when each dependency has picked a different version of said wheel, just pulling in a few dependencies leads to 6 different implementations of the same low-level features.

Why won't they see another generation of star formation when supernovae push gases into dense regions again? It seems like the stage you're talking about is more than a few billion years away (more like 10s of billions).

"As a concrete example:..." I ended up completely misreading that line at first because my brain was desperately looking for a pun.

I just read this as an argument for tiny incremental changes and very short-lived branches. This can work well for a team that is very highly engaged and where Code Reviews get immediate attention. When I've worked for startups, I've seen this kind of usage out of git and it can be quite effective (no branches alive for more than a couple days + frequent rebasing in of upstream changes from main/master).

Long-lived, all-encompassing feature branches are definitely an anti-pattern and they bit-rot unbelievably quickly, especially as team size grows. Some shops I've worked in still prefer them, though, because they demand zero dead code paths or half-baked features making it into the mainline (which are definitely their own risk of technical debt).

Or more, indeed!

Finally! It was only hidable via a registry hack when it first came out.

Won't the new Bing be used by DDG? I thought DDG was on top of Bing already.

Sure, but .1 is definitely representable, so they can be excused for finding it a little unreasonable that .1+.1+.1+.1+.1+.1+.1+.1+.1+.1 doesn't equal 1 in many languages.

Explaining _why_ .1 isn't representable requires explaining IEEE-754 and explaining _that_ requires an understanding of binary numeric representation.

I teach college students who find this confusing, so I think it's fair that the average person finds floating point behavior confusing (in fact, I've had to explain to Physics Professors doing computation simulation work why their 1-<tiny number> isn't working out the way they expect -- though they initially tried using double doubles to get around the problem).

Asbestos is, sadly, completely natural and mined directly from the ground. The other things in your list are obviously not.

GMOs are a very complicated topic, and I can see both sides of the argument having some merit. Proving that new things don't actively do harm (both short- _and_ long-term) should be required before they go to market (or they should have to have very strong warning labels about being untested).

Yeah, I was really going for something like "the more things change, the more they stay the same."

Good to hear you're doing relatively well, and I agree that injecting positivity where you can is probably one of the sanest ways to live.

I think you hit the nail on the head there with the survivorship bias and the raised in a bubble comments. Most people are raised in a bubble because children generally can't cope with how messy and complicated the world is. And systems and companies that last a long time can point to how successful they were because of their good decisions while ignoring their equally bad decisions that really should have undone them had they not been lucky.

The older I get, the more I realize how fragile a lot of human systems really are, but I suspect it has always been this way and it won't change significantly any time in my lifetime.

Your comment itself sound somewhat nihilistic, so I hope you're doing well mentally!

Geodes?

Isn't this just a bunch of static object pools? That's extremely common in embedded programming. I'm glad to see someone recognized it could apply to a database.

My students do this on the GameBoy Advance specifically so they don't need to learn about dynamic memory allocation to get useful things done early in my course. In fact, they only learn about dynamic memory allocation for academic reasons later on and never _need_ to use it in their games.

I believe in Star Trek cannon, Romulans use artificial black holes as the power source in their ships.

Office Space has relevant scenes: https://www.youtube.com/watch?v=N9wsjroVlu8

This 100% aligns with my own experience and reasons for switching teams in the past.

poorly monitored -- the vote up/down is typically used in internal performance metrics and when it dips too low, then someone analyses the feedback to see where they can improve the scores.

Some teams stay way more on top of the metric than others.

But the sock puppet sings exactly the quoted line...

Too true in the case of the multi-sig wallet I lost one of the keys to :'( (thankfully only a fraction of a single BTC).

I worked at a place that was trying to do this for thousands of restaurants, only they wanted to configure the POS system (all the items, variations, modifications, combos, etc.) using just the PDF menu. We never got very far with automating it, but part-time high school employees were usually pretty decent at it.

Menu layouts are all over the place, so using OCR was trivial, but trying to figure out what went together and what modifications were valid on which items was a complete mess. Shrimp cocktail w/ cheese, anyone?