[10x28] How to install and use Pluto.jl (reactive notebook programming environment for Julia)

แชร์
ฝัง
  • เผยแพร่เมื่อ 29 ธ.ค. 2024

ความคิดเห็น •

  • @berntlie6799
    @berntlie6799 ปีที่แล้ว +1

    Great with a simple intro to how to start with Pluto. I haven't tested it yet, but probably should... A few questions:
    * When you save a Pluto notebook, is there a "file browser" for where to save the document, or do you need to type in the entire directory tree?
    * Seems like *print* statements show evaluation *below* the command cell, while markdown and ordinary statements are shown *above* the command cell??
    * I use Jupyter notebooks quite a bit. These tend to become slow when I have equivalent to some 30 pages of html file (if I save the notebook as html...). What size of Pluto notebooks is reasonable?

    • @tubesteaknyouri
      @tubesteaknyouri ปีที่แล้ว

      Yes your first two questions. I'm not sure about the third question, but my guess is that the speed is similar.

  • @lordxaradar8324
    @lordxaradar8324 9 หลายเดือนก่อน

    how can i delete manualy a file in Pluto? i don't see any button

  • @sankarmaradana2195
    @sankarmaradana2195 ปีที่แล้ว +1

    My pluto notebook is stuck on loading forever. Any way i can reinstall pluto ?
    Edit: Removing Pluto and adding it back fixed it. yay.

    • @doggodotjl
      @doggodotjl  ปีที่แล้ว +1

      Glad you were able to get Pluto to work!

  • @cemtutum273
    @cemtutum273 ปีที่แล้ว

    What is the difference between "import" and "using" keywords?

    • @doggodotjl
      @doggodotjl  ปีที่แล้ว +2

      This is one of the confusing things about Julia. "using" will load a package AND make the exported function names available for direct use. "import" will also load a package BUT it will NOT make the function names available for direct use. If you use "import" the only way to access the functions is to use the dot-notation (e.g., Pluto.run()).

    • @cemtutum273
      @cemtutum273 ปีที่แล้ว

      @@doggodotjl Thanks for clarification! Is there any preference for convenience or speed/memory usage? It sounds similar to the case in Python:
      from copy import deepcopy
      versus
      import copy; copy.deepcopy()

    • @doggodotjl
      @doggodotjl  ปีที่แล้ว +1

      @@cemtutum273 I can't speak to the memory usage, but a practical reason to use "import" instead of "using" is if you need to use multiple packages that use the same function names that are used for very different purposes. "import" will allow you to avoid any potential name space conflicts.