That is definitely not right. That sounds like you don’t have a shebang or it isn’t defined correctly. The shebang has to be the very first thing in the script, with no whitespace before it. It gets read out by the kernel, which very dumbly checks the first few bytes.

And well, such a shebang should also work for Python or the like. If you copy the first script in this link into a file script.py, then run chmod +x script.py and finally run ./script.py, does that print Hello, World! ?

I have fish set as the default command to run when my terminal emulator starts, but my system-wide default shell is bash and I always throw a #!/bin/sh or #!/bin/bash shebang at the top of my scripts either way.

With that setup, I hardly notice fish’s syntax differences. Are you using it like that, too?

Yeah, modern computers often feel like a scam. Obviously, some things are faster and obviously, we can calculate more complex problems.
But so often, programs are only optimized until they reach a level of “acceptable” pain. And especially with monopolistic, commercial software that level is close to infinity, because well, it’s acceptable so long as customers don’t switch to competitors.

Either way, the slowness that was acceptable twenty years ago is generally still acceptable today, so you get much of the same slowness despite being on a beefier PC.

I guess, those don’t work for hidden/minimized windows.

Perhaps worth considering a bspwm-like workflow. Rather than minimizing windows, you put them onto another workspace. Just absolves you from dealing with the whole concept of minimized windows…

It’s still effectively Chrome under the hood…

Yeah, I tried it in my other comment, and at first it started with “I think, folks…” which was already a dead end, because any continuation I tried would eventually need a “they”. Kind of wild that something as basic as plural can fuck you up. 😅

I think, you usually post, if you got a thing to say. And thus you want to say that thing, not look for formulations all day long…

Mastodon instance where you can’t post the letter “e”: https://oulipo.social/public/local 🙃

Yeah, had to think of this right away:

But what if your kink is personal attention?

Lots of “modern” languages don’t interop terribly well with other languages, because they need a runtime environment to be executed.
So, if you want to call a Python function from Java, you need to start a Python runtime and somehow pass the arguments and the result back and forth (e.g. via CLI or network communication).

C, C++, Rust and a few other languages don’t need a runtime environment, because they get compiled down to machine code directly.
As such, you can call functions written in them directly, from virtually any programming language. You just need to agree how the data is laid out in memory. Well, and the general agreement for that memory layout is the C ABI. Basically, C has stayed the same for long enough that everyone just uses its native memory layout for interoperability.

And yeah, the Rust designers weren’t dumb, so they made sure that Rust can also use this C ABI pretty seamlessly. As such, you can call Rust-functions from C and C-functions from Rust, with just a bit of boilerplate in between.
This has also been battle-tested quite well already, as Mozilla used this to rewrite larger chunks of Firefox, where you have C++ using its C capabilities to talk to Rust and vice versa.

I also enjoy that it’s on a laptop, which they could’ve carried to M’am’s office.

Perhaps, yes. 😅

It was a diplomatic way of saying that I doubt the author’s assessment that Ruby’s tooling is worse than Python’s. Partially, because Python’s tooling has traditionally been terrible (even if it’s been improving in the past two years, from what I hear). But yeah, partially because I do not see Ruby programs being as buggy as they insinuate here…

I think it was that back when it was relevant (but replace data scientists with web devs)

Sure, but if programs from that era are still around, chances are the maintainer is quite experienced by now and has fixed all the funky behaviour. 🙃

I never got interested in the ecosystem myself, but I’ve run into it every now and then. I feel like it’s in the same place as PHP today: still used a lot for legacy reasons, but you’ll get weird looks if you start a new project with it and you’re under the age of 40

Ten years ago, a university buddy of mine discovered Ruby and you might’ve thought a miracle happened from how excited he was for it. But yeah, that was also the last time I met someone in real life who was excited about Ruby. 😅

Apparently, it was in a forest in Guyana. And well, perhaps you’re imagining a filled-out spiral, but in this case, it looked like a normal ant migration at the first. They were going in 6 lanes at most and at 370 meters circumference, that just looks like a line until you follow it around.

That’s according to this source, which seems to have excerpts from his book: https://themountainsarecalling.earth/the-army-ant-death-spiral/

https://en.wikipedia.org/wiki/Ant_mill

Man, I haven’t done structural inheritance in years and by now, this reads like the ramblings of a mad person.

Like, I recently had a use-case, where I actually wanted to define multiple types with the same fields and for various reasons ended up using a macro for that.
And that still felt simpler than whatever is going on in this article, because there were no cross-relationships between the types at runtime. The macro templated the type definitions as if I had copy-pasted them, except there’s no actual code duplication, which is ultimately all I wanted.

Hmm, I don’t have too large of a sample size, but I don’t feel like Ruby programs are buggier than Python programs, on average. Not being the language for programming beginners and data scientists, probably aides that impression, though…

Since no one mentioned it yet, this is the classic card game “Klondike”.

KPatience is a program that implements multiple such card games…

A few years ago, I learned that the stomach rumble when you’re hungry, is part of a process that’s actually kind of important health-wise: https://en.wikipedia.org/wiki/Migrating_motor_complex

So, it’s good when your stomach and small intestine empty out on a regular basis. It’s good when you’re hungry on a regular basis.
Just yet another luxury problem of modern times, that we have food available at all times and need to stop ourselves from snacking.

Side-note: It’s also good to go hungry, because then when you do eat, the food tastes so much better. This also means you can go for healthier food and still have it hit the spot.