It wasn't really the hardware's fault though. It was crippled by Commodore's marketing department wanting to maintain compatibility with the VIC-20's 1540 FDD, which meant that the bit banging method used to work around a bug in the VIA chip had to be used. Then to add insult to injury, because of how the VIC-II and 6510 need to share the bus, it ended up running even slower than the VIC-20.
Sound trackers actually originated on the C64! Chris Huelsbeck's Soundmonitor is generally regarded as the first tracker. There were plenty of others, such as Electrosound, Future Composer, Ubik's Music, and the Ariston Music Editor. It's not that nobody used software for this kind of thing, but it was pretty common to just use your own sound routine and toggle stuff in.
I'm not sure about Ocean, but a lot of companies used the Tatung Einstein, itself a 64KiB machine, as a development platform. I would assume that the software used for building this stuff was able to deal with source files larger than the machine can hold. They might've moved onto the likes of Atari STs, IBM-compatibles, and Amigas by the time Wizball was released though.
Plenty of music was developed in the form of source files.
Plenty, but these days mostly if you either (a) want a simple implementation or (b) don't have to worry much about cache locality. The problem is that (b) doesn't really exist outside of retrocomputing and embedded systems these days. It's still one of my favourite data structures, just because it's a clever way to get most of the benefits of more complicated datastructures on small systems with minimal code.
It's a tool with a long vintage, and it wouldn't make sense to port it to a different language just to take advantage of the likes of bubbletea or textual.
The US is not in a position to process much of the sweet crude it has. Instead, imports sour crude, which is what much of the US's refineries are actually built to handle. This is why Venezuela was such a thorn in the side of the US, as they were one of the major producers and also largely produced sour crude.
As adwn says, it's a globally priced commodity, and the US is not in a position to disentangle itself from that market because in spite of being one of the world's largest producers, US refineries are not in a position to process that product, so it needs to go abroad. The US needs to import significant amounts of sour crude to be refined for their own use.
The US is just as screwed as the rest of us.
Also, the primary worry for Europe isn't oil, it's natural gas.
The 'sell electricity to Ireland' bit here is doing an awful lot of work. It's more complicated than that.
For those who don't know, Ireland operates an all-island grid, and EirGrid (the grid operator for the Republic) owns SONI (the grid operator for Northern Ireland). That means that 'UK' and 'Ireland' in this has a large Northern Ireland shaped lump of ambiguity that statement.
And even then, I'm not sure it's apples to apples, at least if by Rego you're thinking of OPA. CEL and Rego take very different approaches, with CEL being quite procedural, while Rego is about constraint satisfaction, not unlike Prolog. At $WORK, Rego (in the form of OPA) gets used quite a bit for complicated access control logic, while CEL gets used in places where we've simpler logic that needs to be broken out and made configurable, and a more procedural focus works there.
[ my public key: https://keybase.io/talideon; my proof: https://keybase.io/talideon/sigs/xrQeNgJwDeDVr__AMXDdSK8I6jDosMvyymcRZIGGMyA ]