Lucas, yes! It make sense!
In the end, CLI and REPL will share a big part of code and they will be
just different interfaces to the same features.
+1 for this new concept!
Thanks for make it clear to me!
Atenciosamente,
Rafael J. R. Novello
Skype: rafael.novello
Blog: http://rafanovello.blogspo
That's a good point Rafael. I believe the main motivation for adding a REPL
to Marvin's toolbox is to enhance user experience.
Imo we can't just switch CLI per REPL. I don't think one excludes the
other, both have different use cases.
We may be mixing too much stuff together, but in general, I th
I do not want to be the annoying conversation but...
If we will have an unique CLI that will be able to handle any kind of
engines (in any language) by using docker, Why we need a REPL?
I think we can focus on creating this new architecture using docker and
docker SDK and use only a CLI for that.
Ok, guys
I will like to get this and work with a start on this task this week based
today in your python-engine and I'll tell you about the progress.
Thanks,
On Thu, Oct 25, 2018 at 9:24 PM Daniel Takabayashi <
daniel.takabaya...@gmail.com> wrote:
> +1
>
> Em qui, 25 de out de 2018 às 17:19, L
No, I think the idea is to do not create different versions of the CLI.
Let's use one single tech stack for the CLI, ideally, it will be shared
with the REPL. The way I see the CLI would be very similar to the REPL, but
instead of opening an interactive session the user could send
unattended comman
Hi Guys!
Let me ask about this new version that include CLI's and REPL. Will we
create different versions of CLI?
One of the reasons to create the REPL is to avoid re-implementing the same
features many times,
each time for a different language.
Regards!
Atenciosamente,
Rafael J. R. Novello
Sky
