Really enjoyed this lecture! One request though... Could you please move your microphone for your next recording? It's picking up a lot of noise from keystrokes and mouse movements as low thumping noises throughout, making it quite uncomfortable listening on headphones!
To be fair .. it doesnt exactly create a copy of the data , go try this out in your REPL ... julia> A = [ [1,2] , [2,3] , [3,4] , [4,5] , [5,6] ] julia> B = A[1:3] # select over elements 1-3 to B julia> B[1][1] = 100000 # modify the first element of the first element in B julia> println(A) i dont mean to pedantic but when you are a beginner i think this is an important difference to know or might eventually bite you someday , look up on immutable and mutable data types .
Its a different notebook focusing on reactivity (based on observablehq: observablehq.com/@observablehq/observable-for-jupyter-users). A great trade-off for teaching imho, no student should care about rerunning a notebook in the "right" order.
wow - Julia makes these 2 types of slices very explicit - very user-friendly for new programmers.
Really enjoyed this lecture! One request though... Could you please move your microphone for your next recording? It's picking up a lot of noise from keystrokes and mouse movements as low thumping noises throughout, making it quite uncomfortable listening on headphones!
Nice tutorial, thanks for your help.
Your voice is so good.
To be fair .. it doesnt exactly create a copy of the data ,
go try this out in your REPL ...
julia> A = [ [1,2] , [2,3] , [3,4] , [4,5] , [5,6] ]
julia> B = A[1:3] # select over elements 1-3 to B
julia> B[1][1] = 100000 # modify the first element of the first element in B
julia> println(A)
i dont mean to pedantic but when you are a beginner i think this is an important difference to know or might eventually bite you someday , look up on immutable and mutable data types .
A is changed as expected. What's your message?
If you type v[3:5] .= 9, the 3rd to 5th elements of v will change to 9 too. Is the 'view' function necessary?
It's all natural now but sometimes people get an impression @view -> view(only) -> no allocation but also cannot change
This notebook would make more sense as a jupyter notebook than a pluto notebook
Its a different notebook focusing on reactivity (based on observablehq: observablehq.com/@observablehq/observable-for-jupyter-users). A great trade-off for teaching imho, no student should care about rerunning a notebook in the "right" order.