This was not easy month, so I apologized for not responding for so long. Now I write some remarks about seminar and respond in few days to posts here.
Talk was in form of combination of slides and programming using Jupyter Notebook, mostly in the form of running written before code, with some short, true live coding. Given time constrains, 50 or so minutes, I think that was good choice, showing in what way Julia is dynamic language and how compilation of code and reusing it really looks like. Even if compiling take some time I think that is the best way to show nature of working in Julia (at least how experinced working with it). I only reloaded some packages like
Plots to not used to much time for that.
I get one major criticism: that I started from reason to not learn Julia. Maybe I also listed to much such reasons, since I really don’t want oversell anything and I generally not very optimistic person, so naturally talk about problems. I don’t know how much this critic is valid, since colleagues of mine who makes this comment is quite odd fellow, hard to say if others have similar feelings.
For I think was big mistake, I don’t make one slide for methods of optimizing Julia. I was thinking that things like type stability was to specific topic for such talk, but in retrospect even this is in someway esoteric topic, make information how optimization looks like was big mistake. Even if type stability may sound scarier that it is, it better make a point, that you must learn something new to make your code fast.
There were also two comments from younger part of audience, that I don’t consider as strict criticism. One that Julia optimization is very odd, while C is very natural. Personally, I don’t see anything natural in C optimization, we just learn it from the cradle, so it looks like natural thing. Also Julia optimization don’t look odd to me, just different than in languages like C.
Second was, that C can be hard to learn, but after learning it we can do anything since, we know what compiler is doing with our code and this is reason why we should prefer C. Recently I lost my personal faith in that I understand what compiler is doing and I start thinking since every language separate (assembler and things like that excluded) me from hardware, it should separate me as much as it can reasonably do it. I didn’t have any other answer to this person.
Response. From older people one was interesting in Julia, one decided that is better to learn again Maple (he was never computer stuff guy, so this was predictable), about younger part I write above.
I want to thanks everyone from Discourse, that help to make this presentation or say how can be improved.
Seminar with used Jupyters Notebooks is here. But this is note version that I presented, since this is too much for 50 minutes and many parts need more work, so I removed them from presentation. Also references are really long, because they sometimes as for sending presentation to study it, so I want them to be in some way guide to people. Also nootebooks are too long for 50 minutes, but I make them hopping that I will reused them in the future.