I've been considering setting up "ConfuseAIpedia" in a similar manner using sentence templates and a large set of filler words. Obviously with a warning for humans. I would set it up with an appropriate robots.txt blocking crawlers so only unethical crawlers would read it. I wouldn't try to tarpit beyond protecting my own server, as confusion rogue AI scrapers is more interesting than slowing them down a bit.

How do these much smaller cores compare in computing power to the bigger ones? They seem to implicitly claim that a core is a core is a core, but surely one gets something extra out of the much bigger one?

Cool to see the whole process behind it. Some sneaky tricks there, and much knowledge. Unfortunately, I find the picture doesn't show the tidally-lockedness very well. If it wasn't for the title, I would never have noticed. The haze on the sun side makes it look like clouds.

Thanks! You are right, the effect is weaker than I had anticipated. Maybe I picked the wrong green tones, or the perspective was too close. I'm sure I'll try again sometime!

Samuel

Oh, and there's massive use of aspect-oriented programming, the least local paradigm ever!

I have never actually seen aspect-oriented programming used in the wild. Out of curiosity, in what context are you seeing AOP used?

We use it to automatically instrument code for tracing. Stuff like this is IMO the only acceptable use to reduce boiler-plate but quickly becomes terrible if you don't pay attention.

Also good for having default activities performed on object or subsystem. For instance, by default, always having an object have security checks to make sure it has permission to perform the tasks it should be (have seen this, and sounds like a good idea at least). And also, to have some basic logging performed to show when you've entered and left function calls. It's easy to forget to add these to a function, especially with large codebase with lots of developers

> If someone feels compelled to read every function either the functions are poor abstractions or the reader has trust issues, which may be warranted.

Or it's open source and the authors were very much into Use The Source, Luke!

Some people are proud of making complex code. And too many people admire those who write complex code.

Comments should describe what the type system can't. Connect, pitfalls, workarounds for bugs in other code, etc.

But knowing what Brian was considering at the time is useful, both due avoiding redoing that and for realising that some constraints may have been lifted.

Even more infuriating is when the more expensive version is the same object but with extra unnecessary features added via software, to the detriment of usability.

That's honestly how most products are these days. The base version is lacking one feature that is present in the "premium" version and a bunch of useless add-ons are piled on to justify the expense of the "premium" version.

In a lot of cases, the base version is excluded from certain markets and only the premium is available (e.g. YouTube Premium).

And here I thought here would take about how new models come out so frequently that any information about long-term quality is long obsolete.