EliasLittle

Interesting! I can’t say I’m that familiar with Rust beyond surface level usage. What feels different is that you can declare a reference as mutable or not in Rust whereas in Valen or OxCaml it’s strictly declared in a function’s arguments.

I’m curious if this is an example of survivorship bias though. I don’t have any data, but I can easily imagine lots of projects not getting built at all due to zoning laws or the red tape cost being too high.

What’s IA stand for? This sounds like an interesting article, I wanna try to find it

I think you’re missing one of the key points of Julia, that others have also pointed out: you’re reliant on libraries other write in c/c++.

Julia’s proposition is that the entire community should be able to read and contribute to these libraries. Unlike the python community where the vast majority of users could not read the source behind those libraries let alone contribute.

While I think his terms “Soil” “surface” and “atmosphere” are kinda cute, I don’t understand the need. Each of these already has a very clear established term.

“Soil” = Implementation “Surface” = Language/Syntax “Atmosphere” = Community

Often when people talk about a programming language they mean a combination of these, but it takes very little to clarify which specific part you like or not.

Egos is really neat, and super approachable. I did some documentation work for it last fall, and despite only having a weak grasp of operating systems I could easily understand the whole thing. I only needed to figure out a few common acronyms and magic numbers that weren’t explained.

Another possible use case is for inline expect tests.

It can both help someone understand the function easier by seeing a plot in the source while also serving as a test.