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.

This is super exciting!

Having mutability not be a property of the data, but of the function arguments reminds me a lot of modes from Jane Street’s OxCaml ^1 which is really interesting to me, as OxCaml’s focus is not really about memory management (they still use garbage collection for everything not on the stack). Feels like we might be converging towards a new standard! I can see the morning sun on the horizon :)

[1]: https://oxcaml.org/documentation/modes/intro/

Just my personal blog that I’ve been trying to add more to recently: https://aelias.dev

I’m no expert, but looks like you can represent chebyshev polynomials as the determinant of a square matrix, and if they’re all the same size then multiplying the polynomials should be equivalent to multiplying the matrices and taking the determinant afterwards. Given that the matrices follow a very predictable form, this should also be pretty hardware performant I think.

Just some quick thoughts though :)

https://en.wikipedia.org/wiki/Chebyshev_polynomials?wprov=sf...

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.

8 way trees are used for 3D, they’re called Octrees.

https://en.wikipedia.org/wiki/Octree?wprov=sfti1

yep! https://www.moderntreasury.com/journal/rss.xml

You can also get automatic emails