Experience with Elixir in comparision to R - how to develop without something like RStudio?

Have you happened to use the pry feature in elixir ? and also try to use observer which provides certain monitoring facilities…

This thread here is very much related to this:

Also, this uses Visual Studio Code, that provides some GUI comfortability:

https://forum.elixirforum.com/search?q=visual%20studio

There are various plugins for Vim, Atom, etc., please do check the elixir-lang official site for supported editors.

Thanks.

Welcome to the community

We have a few options - tho many are not a full blown IDE they come pretty close

First, you may find this poll interesting:

And here are some other threads of interest:

And a few more at the code-editors tag.

On the Elixir website there is also a list of code editor support with install instructions

CODE EDITOR SUPPORT

• Emacs Mode
• Alchemist (Emacs Elixir Tooling)
• TextMate / Sublime Text Bundle
• Sublime Plugin
• Vim Elixir
• Alchemist.vim (Vim Elixir Tooling)
• GtkSourceView (gedit)
• Atom Package
• IntelliJ Elixir
• Visual Studio Code Elixir

I’d recommend trying a few and seeing which one you prefer, and if you run into any issues or have any other questions just let us know

I was afraid of being misunderstood by not being able to explaining my situation properly…

I am not so much looking for an IDE. I know that there is not some thing as RStudio.

I wanted to know how people program in Elixir. Do they know exactly that every code line is correct so that they do not need to see the variables’ values at any time? No need to debug?

I will have a look at ‘pry’, thanks.

It is not usual to follow variables changes because variables are immutable.

You might get used to sequential coding, but it’s more

input -> function -> output

or more like a pipeline of transformation… like

output = input
|> apply_change1()
|> apply_change2()
|> apply_change3()

In that case, You can insert some inspect/1 in the pipeline to see how data changes.

@Rolling Welcome to the forum!

When I start writing a function and I want to experiment I usually do the following :

start an iex session: iex -S mix, alias Project.Module the modules I’m using so that I don’t have to write the long names every time I’m just use Module to refer to them

Whatever operations I wanted to do inside the function I try them in the console one by one, check that they work as expected or fix them

To get the values from a specific expression I usually do:

iex (5)> 2+2
4
iex (6)> var = v 5
4

and if I change a module I need to load it again: r Module in order to be able to call the updated functions

I always write the tests and use IO.inspect/2 either in the code or the test to see the value passed in. This is my own variant of TDD. Instead of red-green-refactor, I write enough in my test code (sometimes without assertion) to execute the code I am writing, and use mix test.watch to run the test so that I can see the value.

Personally, I enjoy this way of writing code compared to using iex -S mix. When I am done with the code, I will end off my test with the assertions to check everything is working correctly.

TDD is definitely how I approach it. If you’ve not used it before this mini series from Kent Beck is a great introduction (not elixir but easy to follow) TDD Intro, Episode 1, first 10 minutes, unedited