Yeah, Python requires a “runtime” program, which interprets the Python code and then translates it into native machine code to actually execute it. Because Rust is compiled directly to native machine code by the developer, you don’t need a runtime program on your PC to run Rust programs.

This is also one of the biggest reasons why Rust can be used for kernel development. You cannot rely on a runtime program for developing a kernel, since launching a program requires a kernel to already be up and running.

Well, the situation you describe, is probably best handled by CSS media queries.

In case you’re not familiar, you can write:

@media (width < 800px) {
  h1 {
    font-size: 110%;
  }
}

…to get smaller headings on mobile, for example.

But yeah, reality may be more ugly. Especially, if you’re using a bulky JS framework, it may be easier to do the JS dance.

We do. We even have an accompanying rant.

This meme was, uhm… inspired by Jamendo.
Great service. You can download Creative Commons music for the cost of creating an account there. That’s at least part of why it’s “Oh dear, oh dear. Gorgeous.”.

But well, the button for downloading whole albums is broken.
So, what I’ve been doing, is to just open each song in a new tab, and then repeatedly click download → confirm → close tab.
And then by resizing the window, it’s even possible to align the download- and confirm-buttons, so it’s just double-click → Ctrl+W.

But because of said loading screen, I have to remember to resize the window before I open all the tabs. Otherwise, I’ll get the loading screen every single time I’m put onto a new tab.

I’m guessing, it doesn’t use CSS to do the responsiveness, but rather it’s JavaScript that grabs the window dimensions and calculates how big everything has to be. But it doesn’t get told about the window having been resized until the tab is shown again, and because the JavaScript rendering is slow, you get this short loading screen every single time.