I remember that well (because my manager at the time was asking me afterwards "why were you up at 2 in the morning restarting services?" and didn't believe my answer :( )

I must admit to being somewhat confused by the article's claim that Rust and C++ emit bytecode. To my knowledge, neither do (unless they're both targeting WASM?) - is there something I'm missing or is the author just using the wrong words?

EDIT: bramhaag pointed out the error of my ways. Thanks bramhaag!

By 'Rust compiler' and 'C++ compiler', they refer to the LibJS bytecode generator implemented in those languages. This is about the generated JS bytecode.

Yes, I re-read again, and I think you are correct. Thanks!

Thanks! I was confused about this as well.

They're referring to LibJS's bytecode (the internal instruction stream of Ladybird’s JS engine), not to Rust/CPP output formats.

We've got Check Point Firewalls at work, and during updates I see lots of .tcl in the web UI.

> Is "clown GCP Host" a technical term I am unaware of, or is the author just voicing their discontent?

The term has been in use for quite some time; It is voicing sarcastic discontent with the hyperscaler platforms _and_ their users (the idea being that the platform is "someone else's computer" or - more up to date - "a landlord for your data"). I'm not sure if she coined it, but if she did then good on her!

Not everyone believes using "the cloud" is a good idea, and for those of us who have run their own infrastructure "on-premises" or co-located, the clown is considered suitably patronising. Just saying ;)

> the idea being that the platform is "someone else's computer"

I have a vague memory of once having a userscript or browser extension that replaced every instance of the word "cloud" with "other peoples' computers". (iirc while funny, it was not practical, and I removed it).

fwiw I agree and I do not believe using "the cloud" for everything is a good idea either, I've just never heard of the word "clown" being used in this way before now.

“Cloud to butt” was popular in the early cloud days. It went around Google internally, and caused some… interesting issues.

I remember ridiculing "cloud computing" by calling it "clown computing" decades ago. It's pretty old and well established snark-jargon, like spelling Micro$oft with a dollar sign.

I recently tripped over Dogalog (live-coding with prolog-like code), which could be an addition: https://danja.github.io/dogalog/

I'm only slightly disappointed that this is not the "Someone Else's Problem" version of SEP.

crochet, sir. croquet is a game with balls and mallets ;)

He knows what he said. Now can we have an automated machine for balls and mallets please!

Are you Daniel Craig :) ?

Although Portacle isn't being maintained any more (at least as far as the main developer was concerned last time I looked a few months ago).

More information here:

https://github.com/portacle/portacle/issues/182

In 2020 they went full-time on developing the game Kandria.

They're still active:

https://shinmera.com/projects.html

https://shinmera.com/bio.html

> the agent actually used pkill to terminate itself after realizing it was stuck in an infinite loop.

Did it just solve The Halting Problem? ;)

I enjoyed having to reload everything from tape (compact cassette tape - ie the kind of thing you'd use with a home computer in the early eighties), after a crash due to my poor code. I think the term used then was "character building" ;)

One of my first C programs wrote straight into the BIOS memory (1989 iirc). The machine froze and refused to reboot. We had to remove the BIOS battery to reset the BIOS. Luckily, the battery wasn't soldered to the main board.