OCaml

A lot of the languages that do auto-currying, they do a lot of work at compile time in order to avoid those problems.

Although very clever, like OCaml is about when... how exactly they insert the auto-currying during code generation.

It doesn't really fit

with

Roq? Is it Roq? I think.

But basically the stuff based on OCaml and the calculus of inductive constructions.

And then I also did some model checking back in the days.

So I also like this kind of formal methods.

And what he's saying here is there was an emergency outfix for Rails 8, and the same day they patched it, so the outfix came out same day, they patched it same day, and they found people trying to exploit it literally when they came the next day.

Second, if you look at the article just below it, Rumor of a Bug, what Anil, who is a maintainer for OCaml, for an OCaml library, OCaml is a programming language.

If you look at what he's saying there, what he's saying here is the Rumor of a Bug is good enough for Emu.to go and exploit.

Let me state this slightly differently.

The conversation overall was largely cautious and skeptical about the long-term effects of AI dependence, with warnings about societal lock-in and loss of skills.

Learn programming with OCaml.

Hacker News.

The post shared information about a new English translation of a French book on OCaml, funded by the OCaml Software Foundation.

It highlighted the availability of the book in PDF and EPUB formats and provided links for the code and feedback on typos.

The discussion in the comments mostly focused on the value of learning OCaml, the benefits of functional programming, and the role of languages like OCaml in understanding systems and AI, with most community members emphasizing the importance of deeper understanding and the practical advantages of OCaml for working with large language models or formal verification.

In the comments, the dominant sentiment was largely supportive, with users discussing how learning OCaml can... significantly influenced programming thinking and system design.

Some debated whether it's practical to learn languages like OCaml today, given the dominance of Python and Java, while others considered the long-term benefits of understanding fundamental language paradigms.

I realize given the name of this podcast, I have to be careful what I say.

But setting aside the types part of it, right, like programming in languages like OCaml or, you know, C Sharp or, you know, JavaScript or something like it without all the weird and wild parts, it's actually a fairly comfortable experience, right? Like, here's the thing.

Here's the thing.

One of the things that I point out is like, you small is deeply embedded in our algorithms because if you think about the cost model behind big O, it is assuming small.

Okay, let's slow down here a second.

Now, did I just hear you say that OCaml has a problem? Yes.

I know you didn't say that because I'm pretty sure that OCaml is a perfect language that doesn't have any problems, Teej.

Maybe you can rephrase that.

No, I think I can say that now because I started making my own language.

that.

So that's what, like, University of Maryland's comp sci program does.

They do Java as, like, the 100 courses, and they go to, like, OCaml, Rust, or C after the fact.

And I was relatively technical, having done my tech internship for one of my three summers.

And having learned OCaml and OCaml Bootcamp, I got involved with that.

And that involved things like thinking about how we keep track of our risk or exposure to different commodities.

If you're looking at your positions in energy products, you could look at it at a very high level, or you could look at just oil and related products.

So just a rumor of a bug existing in one of these platforms is enough to send those agentic systems at those platforms and identify those bugs.

And he talks through what it is that he actually identified and saying, OK, he doesn't have access to Glasswing, but DeepSeq vPro or v4 Pro was enough to actually turn up and find this flaw in co-HTTP, part of OCaml.

And that's.

Yeah, but it's not American.

Object-oriented programming comes in when you talk about components and modules and essentially encapsulation, these sort of things, where functional programming typically doesn't really have a very strong story.

I mean, there are languages like Standard ML or OCaml that do have very capable module systems, But other functional languages don't.

And people, when they think of functional programming, they don't really think much about components and interfaces and these sort of things, which are things that I believe also matter very much.

Could you give an example, maybe like an object-oriented thing that you could do in Scala, but you couldn't do in Haskell, which is pure functional?

You mentioned that a lot of the programming languages, they're kind of drifting or kind of being inspired by the other ones and adopting new features.

In the design of Scala, is there a programming language that you admire most and influences Scala the most?

Historically, Scala was Essentially, you could say it was a blend of Java, OCaml and standard ML, which is close to an ML-like language, and Haskell.

So I'm by trade, well, I'm by trade an imperative programmer.

So I was digging through some job postings at a couple of the big quantitative trading firms the other day, and one language kept showing up that I don't think we've ever given a proper spotlight on this show.

It's OCaml.

OCaml, really? That's the one that's been around since the mid-90s, right? I always thought of it as a bit of an academic niche.

Exactly.

It's got that reputation.

Okay, that's a bold move.

Why would a firm that's all about speed and reliability pick something that's not exactly the mainstream choice?

Well, the short version is that OCaml gives them a level of safety that's hard to get in C++ or Java, but without the runtime overhead you'd associate with something like Python.