Congrats, this looks awesome! Love the inline graphs and realtime updates!
Thank you! <3
Luna 1.0 Beta is out
131–140 of 171 posts
Re: Luna 1.0 Beta is out
#132This is exactly the future.
We believe it is. Such comments as this one give us always super-powers, thank you. We will do everything we can to make Luna the most powerful visual language ever created.
Re: Luna 1.0 Beta is out
#133It's cool technology, but if I take a look at an example of a simple react todo list in a similar project like flowhub: https://app.flowhub.io/#project/c111454c9fd2f74d37d1e8a4e739... This looks more complex, harder to reason about and harder to make than just writing the code. And it only gets worse as complexity increases. But of course I've got way more mileage writing code than doing this.
The link leads nowhere (seems login required, but even after login doesn't work). Link to screenshot instead?
Oops, here's a screenshot: https://screenshots.firefox.com/W3XZIh4yCnlcuMNM/app.flowhub...
Re: Luna 1.0 Beta is out
#134this is the programming language for the touchscreen generation, every language until now was born from keyboard use. brillant. I've wanted to see any language have an ast represented visually, then when you save changed to that visual representation it would save back to the original file format, this is very close to what I was thinking of.
@jlebrech thank you! :)
Regarding the AST topic: Luna does use AST for the translation - if you modify the graph, an AST-diff is created, applied to the AST and then AST-diff is created and applied to the text. If you cange text, the AST-diff is applied to the visual form. The visual graph is not direct AST visualisation because it would be completely unreadable :)
Re: Luna 1.0 Beta is out
#135Earlier quoted context omitted.
Interesting, we will investigate it ASAP. In the meantime, please try Chrome instead. We'll try to fix it soon. I'm really sorry for the incontinence!
Testing on firefox on android would be appreciated too, because right now the website is unusable :(
We'll fix that. I'm sorry you had bad experience with it.
Re: Luna 1.0 Beta is out
#136Hi, I'm one of Luna founders, I'll be happy to answer any questions! :)
Are you aware of the existence of the Lua programming language, and the word "lua" meaning "moon" in Portuguese?
Actually it is not intentional. We do not have any connection to Lua. The name "Luna" was used from the beginning of the project, people started recognizing us with it and we simply love this name so it stayed with us.
If such confusion would be often, we will change the name, however, we've got few comments that this name could be confusing but in fact nobody ever confused it.
We are still open to change it and are actively looking for any kind of replacement. If you have any idea of a name that would be suitable for such a language, I would be more than interested in hearing it.
Moreover, I just opened a thread on our forum to discuss names propositions. If you've got any ideas, please share them with us! :)
Re: Luna 1.0 Beta is out
#137Hi, I'm one of Luna founders, I'll be happy to answer any questions! :)
Hey, I'm a founder working on something that can have a pretty similar front-end! Could you comment on your business model? In particular, how's the company intend to draw in revenue?
Hi! Do not do another front-end! Use ours, here it is (with some additional code, we should move to separate repos soon):
https://github.com/luna/luna-studio
It would benefit both worlds - you start with something working and well designed and if you improve it in any way, we would be happy to have your contributions :)
Regarding business model - everything is free. We will provide some paid hosting solutions in the future / paid libraries for very specific domain use cases.
Re: Luna 1.0 Beta is out
#138Be aware, before downloading: This application will not run without providing an e-mail address. It also forces data collection. I will not use such software.
Also be aware that it's a beta. It's not necessarily an evil thing to want to get feedback on your software from those who are interested.
Then why make opting-out of telemetry consent so obtuse?
Re: Luna 1.0 Beta is out
#139Earlier quoted context omitted.
Bret Victor has written about these kinds of languages before, mainly in his "Drawing Dynamic Visualizations" notes ( http://worrydream.com/DrawingDynamicVisualizationsTalkAddend... , talking about what he just presented): > Is this "visual programming"? No. The term "visual programming" has had a well-established definition for several decades, and this tool is not that. > A "visual programming language" provides gr…
@seanmcdirmid We are not yet there, but we develop Luna to target EXACTLY these use cases - program modification AND very direct data manipulation. We see Luna as an unified platform for building rich DSL's. An example of such rich DSL is what Bret Victor demonstrated in his talk. You can read more about rich DSL's and what Luna is meant to be in our blog post here: https://medium.com/@luna_language/luna-the-visual-w…
I guess at this point, I just see a nice VPL; it seems to have the liveness properties of Quartz Composer, at least, which, as you say, displays an interactive results visualization and input data widgets (though you might have to turn the patch around or mouse over an input pin). It seems to fit into Tanimoto's liveness level 4 taxonomy.
If you have some direct manipulation and gradual abstraction going on, I haven't seen it in your examples or explained in your docs.
Re: Luna 1.0 Beta is out
#140Earlier quoted context omitted.
I love the concept of Luna and think the project itself was great, However I feel you guys have chosen a poor approach to distributing it. ① I feel it would have been far better to implement the studio as an Atom plugin rather than a fork of Atom ② I feel having the compiler only available bundled into the studio is a mistake, there should be a pure CLI interface with minimal external dependencies so that people can…
Thank you for the feedback! To answer your concerns: 1. Studio is actually a set of plugins for Atom, not a fork. It's just that we are shipping an Atom binary and make sure that it can work alongside a standard Atom installation, for a smoother experience. We understand how many people use Atom for their daily work and we'd rather not mess with that. 2. That's a perfectly valid point! We'll prepare a CLI distributio…
Regarding (1), this is a great way to distribute your language tooling. After a number of years using Atom, one thing that I've always wanted to see is a way to utilize multiple Atom instances all uniquely configured for a given use-case/language. For an editor that excels in customization, one thing Atom doesn't have is "profiles". I commend you for providing a Luna "profile" and I hope other languages/ecosystems consider using this approach.