summaryrefslogtreecommitdiffstats
path: root/2024/talks/julia.md
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--2024/talks/julia.md81
1 files changed, 47 insertions, 34 deletions
diff --git a/2024/talks/julia.md b/2024/talks/julia.md
index 4b16f531..ba610a75 100644
--- a/2024/talks/julia.md
+++ b/2024/talks/julia.md
@@ -74,40 +74,53 @@ communities drive innovation.
## Notes
-- \<martinl\> Great, now I wanna learn Julia\... :-)
- - \<vidianos\> Highly recommend it. Especially if you do any sort
- of scientific computing. It's an amazing language
-- \<sctb\> Lots of things to like. Perhaps the most Dylan-like modern
- language? 
-- \<gs-101\> Got me interested in Julia, great talk
-- \<akirakyle\> Sooooo emacs written in julia?
-- \<xlarsx\`\> Amazing, thank you
-- \<mretka\> M-x clap
-- \<vidianos\> Great talk \[13:10\]
-- \<mretka\> Thank you for the talk! \\o/
-- \<martinl\> Thank you!
-- \<akirakyle\> I've been so happy ditching python for julia for all
- my scientific research needs :)
-- Some of these features, like the interactivity and the decompiler
- reminds of Common Lisp
-- One of Julia's best features (multiple dispatch) was inspired by
- Common Lisp's defgeneric/defmethod.
- - I would also add that Julia takes the idea further than Common
- Lisp ever did, because you can't opt-out of being generic in
- Julia, so it's everywhere and used pervasively.
- - In Common Lisp, you had to opt-in, so it wasn't as apparent how
- powerful this way of organizing code could be.
-- \<gs-101\> Got me interested in Julia, great talk
-- \<akirakyle\> Sooooo emacs written in julia?
-- \<martinl\> akirakyle: First Guile Scheme (re: Robin's talk, next),
- then Julia! ;-)
-- \<akirakyle\> Yes ;)
-- \<jkm\> So julia is like using CLOS everywhere?
-- \<akirakyle\> Sort of, but with the llvm runnig full optimized
- native code generation for every argument type a function is called
- with
-- \<akirakyle\> also julia \--lisp is bulit in!
-- \<akirakyle\> emacs-jupyter works with julia quite well btw
+- Great, now I wanna learn Julia\... :-)
+ - Highly recommend it. Especially if you do any sort
+ of scientific computing. It's an amazing language
+- Lots of things to like. Perhaps the most Dylan-like modern
+ language? 
+- Got me interested in Julia, great talk
+- Sooooo emacs written in julia?
+- Amazing, thank you
+- M-x clap
+- Great talk \[13:10\]
+- Thank you for the talk! \\o/
+- Thank you!
+- I've been so happy ditching python for julia for all
+ my scientific research needs :)
+- Some of these features, like the interactivity and the decompiler
+ reminds of Common Lisp
+- One of Julia's best features (multiple dispatch) was inspired by
+ Common Lisp's defgeneric/defmethod.
+ - I would also add that Julia takes the idea further than Common
+ Lisp ever did, because you can't opt-out of being generic in
+ Julia, so it's everywhere and used pervasively.
+ - In Common Lisp, you had to opt-in, so it wasn't as apparent how
+ powerful this way of organizing code could be.
+- Got me interested in Julia, great talk
+- Sooooo emacs written in julia?
+- akirakyle: First Guile Scheme (re: Robin's talk, next),
+ then Julia! ;-)
+- Yes ;)
+- So julia is like using CLOS everywhere?
+- Sort of, but with the llvm runnig full optimized
+ native code generation for every argument type a function is called
+ with
+- also julia \--lisp is built in!
+- emacs-jupyter works with julia quite well btw
+- org-babel also works well
+- def looking forward to the julia talk
+- It would be great to integrate pluto with emacs, but currently very hard to figure out best way to do so
+- That would be interesting for sure
+- Pluto.run(auto_reload_from_file=true) is the best right now
+ - Problem is pluto is very tied to browser
+ - I dislike leaving emacs for things
+ - But Pluto is a great tool
+ - Same, I suppose one could alternatively say the problem is emacs can't be very easily tied to the browser
+ - As opposed to vscode where such integrations are easier
+ - Although, on the other hand, I am happy emacs isn't tied to a browser
+ - It's better in general
+ - Yes it shouldn't be tied to a browser, but it also would be very helpful for emacs to have better access to rendering content that requires a dom/js environment in an emacs window
[[!inline pages="internal(2024/info/julia-after)" raw="yes"]]