onre

The site has a headline about halfway down the page, which apparently gets machine-translated to the reader's assumed language, probably based on GeoIP as my browser is set to request pages in English. This doesn't work very well... the Finnish-language version of the headline makes very little sense, the second word reads as either a weird homophobic slur with a typo or just plain nonsense.

This is equal parts brilliant and demented. Thank you.

  syöte olkoon vakiosyöte

  yritä
    tee syötteen kullekin alkiolle:
      käsittele(alkio)
  paitsi poikkeustilanteessa liukulukuylivuoto:
    kirjoita(virhetulosteeseen, "liukulukuylivuoto")
  muutoin:
    kirjoita(virhetulosteeseen, "odottamaton poikkeus")

I'm typing this on a 6S Plus, and so far it seems like this'll do until iOS 15 patching stops.

Instead of ignoring everything, I've found it better to apply this setting instead:

  git config status.showuntrackedfiles no

Intake and exhaust manifold shapes affect the power and torque characteristics of the engine. Also, these are not cheap parts. Also a quick glance at the parts catalogue suggests that the example engine, BMW B48, has different pistons and connecting rods for different tune levels, suggesting that the cast engine block is one of the few components which are actually interchangeable between the versions. Didn't check, but I'd guess the turbocharger compressor and turbine wheels might be different, too.

For a moment I was really confused about this purported achievement of late Mary Stuart before my brain made the right connection.

As a Northern European (Finland) I can tell you that the electricity cost here for last year was closer to 0,1 € per kWh including the transfer fee and taxes. Additionally, more than 40 % of houses here have electric heating. The heating season starts in early autumn and ends in late spring, lasting 8 to 9 months depending on the year. As the electricity used by the device is turned into heat, during the heating season running it costs nothing.

I would most likely end up with something like this:

  CAT          CATalogue - output the contents of current directory
  RM           to Raster Memory - load contents of named file in framebuffer
  MV           Make Virtual - map the file into memory and output the address
  LS           Load System - attempt to reboot using the named file as the kernel
  CD           Create Directory - self-explanatory
  SH           System Halt - immediately stop all processing

...and so on.

Yes. The current state of things makes much more sense when one is aware of the background.

Thanks, I always mix up mold and mildew. However, "arpa" is specifically a lottery ticket, whereas there are tickets for concerts, tickets to ride, tickets in Jira etc...

> I have to say, .home.arpa doesn't exactly roll of the tongue like .internal.

In my native language (Finnish) it's even worse, or better, depending on personal preference - it translates directly to .mildew.lottery-ticket.

I remember borrowing a book from the library, which had a type-in checksum program of this sort. It was done like was common for C=64 things of this kind - there's a BASIC FOR-loop iterating through a memory area, reading in bytes from DATA statements you've typed in and POKEing those bytes into memory, not completely unlike entering a program manually from the front-panel switches of an older computer.

So, after typing that in and probably SYSing (C=64 BASIC command for executing machine code from arbitrary memory location) to some address, it did print out a two-digit (eight-bit) hex checksum after every BASIC line I entered on the C=64 and the program listing in the book had the correct checksums for every line, so spotting errors was more or less instantaneous.

This stuff brings memories.

  FOR I=40960 TO 49152:POKE I,PEEK(I):NEXT I
  POKE 1,54

From top of my head; loop through the BASIC interpreter area, reading byte by byte with PEEK and POKEing those bytes back to the same addresses. Sounds nonsensical? Not so, because the C=64 does have full 64 kB of RAM, but some of it is overlapped by ROMs. What happens here is that you're reading from ROM but writes always go to RAM, so you're copying the BASIC interpreter from ROM to RAM. After that, the POKE statement turns off the ROM overlap and the interpreter is now run from RAM, so you can edit it live - and obviously cause all sorts of interesting crash situations.

It sure did help later with career in IT to have understood this kind of stuff at age of around ten.

I feel this is a side-effect of so many people getting "simple" wrong, as in, calling things simple because they superficially seem so, even while being aware of but ignoring the underlying complexities.