DiffProg

From the devs themselves: https://blog.jupyter.org/i-python-you-r-we-julia-baf064ca1fb...

> When we decided to rename part of the IPython project to Jupyter in 2014, we had many good reasons. Our goal was to make (Data)Science and Education better, by providing Free and Open-Source tools that can be used by everyone. The name “Jupyter” is a strong reference to Galileo, who detailed his discovery of the Moons of Jupiter in his astronomical notebooks. The name is also a play on the languages Julia, Python, and R, which are pillars of the modern scientific world. While we (Love Python), and use it for much of the architecture in Jupyter, we believe that all open-source languages have an important role in scientific and data analysis workflows. We have strived to make Jupyter a platform that treats all open-source languages as first-class citizens.

Keyword is imagine, because with Mojo you do have to write your code in a new language. You cannot use the Python parts if you want speed. That's writing code in a new language.

Well assuming that a usable thing exists seems to be where you went wrong according to the reports on Twitter and such haha.

0:16 from https://www.youtube.com/watch?v=mQh9es5gfpo, says "we'll be open sourcing documentation"... by the end of the year. Documentation? It will have taken a full year to open source documentation. Congrats.

I wonder when Jax joins this list. 2023?

Agreed. Fish sticks must be a regional thing, maybe East Coast where more fried fish is common. The only cheap fish of this sort that I see around the Portland area isn't fried, it's tilapia.

This still doesn't fix the fact that PyTorch libraries like torchdiffeq tend to benchmark orders of magnitude faster than other libraries (1) and then devs just write off the performance issues (2)

(1): https://gist.github.com/ChrisRackauckas/cc6ac746e2dfd285c28e... (2): https://discuss.pytorch.org/t/why-torch-jit-is-so-slow/36616...

Agreed. Every good serious story will have comedic elements to it.

Indeed, this is the same terrible idea I see whenever my next job wants me to switch to the new latest and greatest javascript framework, or the new latest and greatest ML framework. If you never have time to build up the simple knowledge you keep wasting time.

The breaking changes don't seem to effect all that much. I for one don't see it being that breaking.

Interesting! From reading the book I started to think that was the case!

Indeed currying shows up most in functional programming world

Definitely above my expectations. What a great man.

By far the #1 committer and founding engineer of Swift for Tensorflow also recently left the project: http://rxwei.me/about/ . From the committer list, it looks like Dan Zheng is the only individual who is actively working on it, and he's was an intern until he formally started January 2019. I don't know the ins and outs of Google culture, but it looks at least like every senior engineer has moved onto something else.