https://htmx.org/ solves the problem of full page loads. Yes, it's a JavaScript library, but it's a tiny JS library (14k over the wire) that is easily cached. And in most cases, it's the only JavaScript you need. The vast majority of content can be rendered server side.

Graphics programming is the most obvious one and it uses it plenty, but really any application that can be modeled as a series of discrete changes will mostly likely be using calculus.

Time series data is the most common form of this, where derivatives are the rate of change from one time step to the next and integrals are summing the changes across a range of time.

But it can even be more abstract than that. For example, there's a recent-ish paper on applying signal processing techniques (which use calculus themselves, btw) to databases for the purposes of achieving efficient incremental view maintenance: https://arxiv.org/abs/2203.16684

The idea is that a database is a sequence of transactions that apply a set of changes to said database. Integrating gets you the current state of the database by applying all of the changes.

Many things that work with time series data use calculus all the time. Both derivatives and integrals are very useful in that context: derivatives being the rate of change at some particular time step, and integrals being the sum of the changes across a range of time steps.

There's a pretty wide range of applications.

Mongodb is not actually faster. Postgres still beats it in any benchmark that matters.

Nothing is ever actually schema-less. There is merely explicit and implicit schemas. If you don't want to bother encoding the schema as proper columns and instead want the schema to remain implicitly encoded in JSON, Postgres' jsonb columns do a better job of that than any NoSQL database does.

Wait, the lens flare effect is because of my astigmatism?

It could just be a joke about having younger kids that don't know any better yet. But yeah I mean it's not particularly funny regardless.

That's... a really dumb definition. And why is C# right in the middle but Java's towards obsolete and toy lang? They both compile to byte code and are overall extremely similar.

Haskell's also not there. I was ready to criticize any quadrant it was put in heh. But that's probably mostly because the axes are kinda bad.

The makeup of universities these days isn't that far off from that in general.

Sure, I just meant that I have no idea how it's at all relevant.

Any number expressible in ternary, or a base 3 number system, is expressible in binary with a very simple formula to convert between the two. Binary just requires more digits. Fundamentally, a ternary computer is the same as a binary computer in terms of the problems that are decideable.

Ternary computers have been around for a very long time. They are not new, and I fail to see how they are in any way relevant to AGI (which, to be clear, is something that exists purely in the realm of science fiction and not something we're actually going to be accomplishing any time soon). Ternary computing is certainly interesting and can offer potential performance improvements over binary computers in terms of speed/power efficiency for certain specialized applications, but it's not some magical new computing paradigm or something. Oh, and by the way, there's multiple ways of making ternary systems: -1, 0, and 1 is just one system (called balanced ternary).

Also, fuzzy logic (or logic that accounts for uncertainty) has been around for a very long time, and in fact, is exactly what neural networks are using right now. It's encoded using floating point numbers between 0 and 1, which, in binary, are encoded using 32 or 64 bits (or more rarely, 16 bits). Again, not anything new.

And I have no idea what you're talking about with analog.

It looks pretty normal to me as a professional Haskeller, though I suppose it's perhaps slightly cleaner to write it as conditionalBaptize p = fromMaybe p $ baptize p. It's largely just a matter of taste and I'd accept either version when reviewing an MR.

Edit: I just thought of another version that actually is far too clever and shouldn't be used:

conditionalBaptize = ap fromMaybe baptize, making use of the monad instance for ->. But yeah, don't do this.