rothron

I see a lot of these attempts at getting a model to replicate a classic game. I'm sure this is a use case with some interest, not everyone wants to spin up an emulator, but it strikes me as odd. Rather than English being the new high level language for programming, the LLMs is handed a finished game as a specification and asked to copy it.

That gets you past the problem of the lack of specificity in English, but requires you to already have the thing you want to get made. At least tokens are cheap.

This fix means that you won't notice when you accumulate other such resource leaks. When the shit eventually hits the fan, you'll have to deal with problems you didn't even knew you had.

These are the same noises that were made on the right prior to the election. As long as people are sufficiently mad about the status quo, the other party has a chance to take over.

This topic has been written about in more depth by people who didn't try to work it out by themselves.

The classical artists color wheel is based on pigments. Printers use dyes. Screens use light. That's the whole reason why the primaries are different. The wheels are just tools.

I don't think we disagree it's just a different perspective. The forced handling or propagation is what makes them annoying, but I think they're conceptually wrong.

It would be another matter if they were designed such that you could fix an issue and continue the call on the happy branch, but I suspect the cases where something like that would be applicable are very few.

> But importance of the failure is determined completely by the program, not the library.

Exactly. I think this is the real crux about what's wrong with checked exceptions. It puts the responsibility to decide what exceptions are important on the library, where it doesn't belong. Only the user of the library knows that.

It's more of an issue the more network-y and multi-cpu your ecosystem is. I find the post rather banal and obvious. The state is literally the how and what.

I have made ice cream like this using Gellan as a stabilizer. It's just too much of a pudding to melt. It's not really what you want in an ice cream. You at least want it to melt completely in mouth temperatures.

His first mistake was to read back the verification number? Why would they legitimately asked for this theoretically?

To verify he has the phone they just called him on?

You should never have to read back a verification code.

We used to laugh at the tin-foil hat people. Maybe they were just ahead of their times.

I remember well the movement that impressed me the most. The elaborate changing of direction when running and then turning. It looked so natural, and it was the first time I'd seen that in a game.

Most platformers still violate conservation of momentum and let you change direction in mid air.

Some of them were made from 'rotoscoping' video recordings of his younger brother.

Videos exists:

https://www.youtube.com/watch?v=wKgLfqOVHco

This would've made an awesome SciFi short story.

The twist at the end is that she's lying.

You also need a CRT or at least some sort of strobing refresh display to eliminate smearing from persistence of vision.

This takes me back!

But it feels kinda wrong to have that mouse cursor and have it not move perfectly smooth.

Wouldn't an ad like that attract the biggest egos, not necessarily the best coders, nor people you would ever want to be on a team with?

The extension is somewhat of a misnomer. It's really a jif. JPEG Interchange Format. You can imagine the confusion if the jif extension caught on.

I called it that because I've seen fib be the go-to example of so many introductions to functional programming.

But I suppose it's more accurate to describe it as the poster boy example for changing an implementation to make it tail recurse.

Just to underline the futility of this, if you are clever you can let the compiler do it.

https://everything2.com/title/C%252B%252B%253A+computing+Fib...

Don't see the point really.

Languages without tail recursion will perform worse. Memoization is borderline cheating, because it's a different implementation.

Fib is the poster boy for tail recursion but the reason for that is that recursion to implement fib is simply a bad choice. It's cute but that's about it. If the point is to measure function call overhead, then measure _that_?

Yes. Especially if it has an ULMB function that can strobe the backlight.

It's sure nice to not have your corneas constantly assaulted by charged dust particles.

I've got a 10 year old who's been making a lot of stuff in Scratch since he was 6. I've been trying to think of how to phase him over to less limited languages and wasn't aware of blocklike.js, so thank you for that idea.

Having a lot of projects that you don't finish is completely normal, so don't worry about that.

The move from CRT to LCD adds a few milliseconds depending on the screen. We're so used do it by now, that typing on old hardware is almost jarring. It feels almost TOO responsive.

Theoretically, it should be possible to recompress the video back into the compressed file with no loss, provided the same codec is used, but it would be far more expensive computationally.

While interesting, it's comparing 5000+ Tensor Processing Units against 64 CPU threads. I suspect this isn't a fair comparison by watts spent.

People have done this of course, but you cannot convince a flat earther with GoPro footage because of the fisheye lens that will allow you to film the horizon curve either way, depending on the angle.

What you'd need is a wide angle rectilinear lens not normally found on light weight cameras.

He shouldn't expect much from 1800 feet tough in terms of seeing the curvature. It won't be pronounced. I think he just wants to fly.

It's square as it's 8x8 pixels, but the pixels themselves are not. There's a difference in aspect ratio between PAL and NTSC variants, and because the C64 was usually connected to a CRT, pretty much all bets are off.

Not looking forward to the video services that demand that you pay attention to ads before they let you view their content, now that they have the ability to check.

Blood banks stopped paying for blood because it attracted the wrong customers, those strapped for cash rather than the idealistic types. As a result quality suffered.

Between hospitals blood is bought and sold at the price you mention.

Radiolab had an episode about this some time ago.