kustosz

4 ms·

1.
by kustosz 9y ago
"Freemium language" is not an option. The language is, and will be free and open source. I cannot even imagine any other option, particularly after open sourcing the codebase. Premium tools and services is the way to go for us and
2.
by kustosz 9y ago
Hey, thank you! :) You can run computations on streaming data sources, and building computations on some local files and then running it as a part of a bigger, network connected pipeline is a very common workflow. As for connectors for spec
3.
by kustosz 9y ago
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
4.
by kustosz 9y ago
Hey! There isn't any out-of-the-box support for distributing Luna programs over the network or any library for that yet. We'll get there eventually, but this is too early a release. As for integrating with Hadoop and others: the n
5.
by kustosz 9y ago
We don't have a webserver library yet, but a simple one is coming soon (probably this or next week). As for package management – well, we figured it's to good have some packages to manage first and not to rush into that. It is als
6.
by kustosz 9y ago
Hey! For now the best way to interact with Postgres is, I think, using an HTTP wrapper server. A better way to do this needs to be created. Maybe as a community effort? ;)
7.
by kustosz 9y ago
Hi, I'm one of Luna founders, I'll be happy to answer any questions! :)
8.
by kustosz 9y ago
Some things look best in text and it's fine. However, "programming" is a very broad category, and definitely does not boil down only to algorithms and data structures. I'd even say that most programming tasks in the worl
9.
by kustosz 9y ago
Why don't we have both? And then some more. It is an awesome REPL with a bit of Excel feel. Runs the code whenever you change it and displays the results in real-time. It is also great for interactive data sources (like web services),
10.
by kustosz 9y ago
Interesting idea! Are you thinking about any specific applications you'd like to deploy there? I'd love to learn more
11.
by kustosz 9y ago
Other than name – none at all :)
12.
by kustosz 9y ago
For starters we've made sure to make git diffs as readable as possible. The visual data is kept at the end of text file (hidden when using our editor), usually in a single line. So if you just move nodes around, one line gets changed a
13.
by kustosz 9y ago
The standard library is 3-ish kLOCs (written entirely in Luna) and growing, the biggest use cases we've created so far were around 500 LOCs. Performance-wise, we are letting the GHC compiler infrastructure do most of the heavy lifting.
14.
by kustosz 9y ago
I wouldn’t say it’s bogus, and there definitely wasn’t any malicious intention behind it, it’s just that finding a name for such a property is super difficult. As I’ve written above, it’s about having fine-grained control over the data (obj
15.
by kustosz 9y ago
This feature is a bit of a misnomer, as it immediately brings up discussions about category theory. That being said, the idea behind it is pretty simple, yet powerful. Our typechecker will be able to track the shape of data on a deeper leve
16.
by kustosz 9y ago
We needed to design everything from scratch to make sure the two representations are truly interchangeable. Every design decision in the textual language needs to be backed by its visual counterpart, and we found this way of thinking imposs
17.
by kustosz 9y ago
It's not. That is just a name clash, but in our early days TJ was so kind as to pass the ownership of luna organization on GitHub to us :).
18.
by kustosz 9y ago
We store them in a separate section in the source file, which is hidden by default when editing. So a bare .luna file is a readable text file, containing some metadata at the bottom, which is not shown when editing with our editor. This way