Calculating Burn Rates in J

In J every symbol is precious and extremely well thought out. The ancestor language "APL" uses its own custom symbols where there the traditional Unicode looking division symbol is used. I really like the APL symbols (there's a video of a guy using the special APL typewriter from the 60s on YouTube), but with J you don't have to worry about installing a special font and buying a keyboard with the symbols written on the right keys. J doesn't precede C in age, but the author/architect (Turing award winner Ken Iverson) had been making large contributions to computing well before C, so he would've had no reason to think "let's make sure as many of my symbols follow C as possible". APL and its descendents are used in industry and have been for decades. Primarily in finance (see KxSystem's awesome KDB+ used by many such as Morgan Stanley), but also in places like Volvo...etc.

Edit: I just re-read my comment and I hope it didn't sound too condescending (not my intent). I'm fairly new to J, but it's pretty cool and I hope you give it a shot if you ever need to do any data oriented tasks.

Yes, `%` is division. It's not that odd, if you look at the symbol - it looks quite similar to the division symbol `÷`.

It's almost better asking where C got the idea that it should be mod from!

In APL based languages (like J), the symbol / has a strongly established history of meaning "fold", or, if you prefer, "reduce".

But it is not a "C-based" language. It is APL-based. APL preceded C by at least eight years.

I've used Pandas a bit and it certainly works well, but there are a lot of library functions to learn while J seems to basically be learn the two uses for every symbol and know how to do all math stuff ;).

I'm always impressed to see derivative and both matrix inversion & transpose as elementary operations instead of googling for a library that is most likely poorly documented. Furthermore, since the vector is the basic data type, things like matrices crop up a lot more in J & APL. In Python they are for scientific pursuits. In J they will often crop up even if you're writing a blackjack game. I think this is why it doesn't appeal to many programmers without a strong mathematics background, but it's very appealing to those who have that kind of background and grow tired of writing incessant loops.

In all honesty it's more a comfort thing: I'm so used to vanilla Python that the extra stuff in Pandas messes with my head. It's just easier for me to work in a completely different language.

Also J is more fun as a puzzle language, so I use it for personal projects. If I was writing stuff for production I'd probably (if begrudgingly) use Pandas instead.