I can't tell if he's being sarcastic, or not, or if he knows whether he's being sarcastic or not.

The red band is where the real geniuses are. Apparently.

Allow me to clarify.

C has for, while, and do-while. That's it.

Ruby has for, while, do-while, until, rescue, inlined conditionals, optionals, and iterators, for what amounts to the same task; not to mention exceptions (something the C standard has repeated swerved away from, wisely) and lambdas.

I'm not saying that there isn't a time for Ruby, but if you think C falls into the same category then we're very much in disagreement.

When you're first writing a line of code, you should already be thinking about how you might refactor it in the future, and preparing for that.

For me the big issue with Ruby—which admittedly has many fine features I would like to see in other languages—is the lack of a general standard for its operations. There are so many ways to get the same basic logic loop done, it feels like a recipe for either unfollowable code or chaos in programming teams.

Props and big up for the G'MIC shoutout. That thing is a BEAST.

Absolutely. I don't know if it's the absolute best, but I very much agree for using a high-level language for high-level tasks. There's a reason they're designed that way—you're not burning Hertz, dang it; you're burning seconds, and you're burning them either way!

That said, please, please don't use it for performance critical code.

Not necessarily. They could easily be talking about the monstrosity that is Eclipse.

I'm hacking together a demo game, and I can save enormous amounts of animation time if I can simply use an armature in the middle of my otherwise JRPG-like game. That way i don't have to worry about individual frames, and can almost go directly from Krita/Blender to Godot.

Scene tiles allow me to do that.

Later on, I can try replacing these with animated tiles selectively, if overhead becomes an issue.

I'll post a link when things start coming together!

God, it works great. Read through the tutorial and it will give you an idea of just how powerful the tile editor is.

The only downside to scene types is that they are effectively instanced at every placement in the scene, so they're more demanding; but most of the time that's not that big a deal.

OK, I seem to have figured it out. It was me.

I created a second scene, which had a Node2D root. Its children were, in order, a TextureRect2D set to a noise texture (just to test this as I work), a SubViewport with with a MeshInstance3D torus and a Camera3D as children, and then finally a TextureRect2D with a ViewportTexture, set to that SubViewport. The camera was of course aligned to look straight down at the MeshInstance3D.

The viewport's transparent_bg was toggled to on, and I can see the TextureRect2D right beneath it. Importing it as a scene tile worked fine, I can see the grassy green underneath the tile now.

It seems likely that I may have messed up my blending mode somewhere in the old one, which is fine; apparently I don't really need to worry much about that.

I need this on a poster on my wall.

I don't even want to know what that is. We've been speaking downhill since Javascript...

I'm going to be the snarky SOB that says it's the same reason they're still using NTFS when dozens of open and objectively better file systems have been created in the thirty years since--no one seems to hold them to any practical standards.

Rcedit can do the job, but it isn't an open license and you would need to run it through Wine on Linux or *BSD.

Does anyone know if it is at all possible to specify an SVG icon like a sane person yet? At least on 11?

Sorry for your loss. 📉

I miss the days when Python had comprehendable version systems...

I think IBM is going to immediately regret this immediate decision.

You could kind of feel it when their budget went down the tube and they started phoning in the script.

On the bright side, India just did this, so we've got data coming from the poles after all!

You know what this reminds me of? The processing failure that killed Phobos 2 right before it reached Mars.

As I recall, the craft lost attitude control and didn't have a safe mood to orient it toward the sun; so it burned through its batteries making adjustments in a few hours. It had two landing probes on board that never got to be used. So, no emergency backup systems. Never heard from it again.

Of course this was 1989, and most people only had a vague idea what programmers did; but it still feels like a serious and kind of nebulous oversight.