Live data from Hacker News

Rye Language

ryelang.org

41–50 of 61 posts

Re: Rye Language

#41
post #7

Earlier quoted context omitted.

Not having studied Rye documentation, is it true that Rye syntax is "minimal"? Compared to for instance Smalltalk?

Yes ... Rye is syntax-wise in similar camp than Lisps, only without parenthesis. Some say Lisp has no syntax (which is debatable), but has a point that there are no syntax rules. There are multiple token types and they always combine / apply in the same ways, there are no special forms like "how to define a function" or "how to write and if else". In Rye calling if or eihter (if/else) is no different than calling any…

Carl Sassenrath, the creator of the Amiga OS, created REBOL after he did Amiga Logo. Logo is what REBOL's syntax was based on. Logo is often called, 'Lisp without parentheses'.

Re: Rye Language

#42
I don't often get excited when I see a new language, but this is really neat! It's not just another lisp or forth variant, but seems to be in a class of its own (if anything it reminds me of smalltalk, but claims to not be object oriented). I'm quite interested to see where this project goes!

Re: Rye Language

#43

This sounds cool: "Every active component in Rye is a function (if, loop, for, fn, return, extends, context). No keywords, no special forms." It should make the language much simpler than other languages. The challenge of programming is dealing with copmplexity in code, and if the language takes away much of that complexity it should be a good thing.

This is a very good thing! Too many languages introduce keywords out of convenience, but in the end that makes the grammar more complex.

Re: Rye Language

#44

Interesting, but optional parenthesis is a no go for me. Every time I try to read a Ruby line with no (), I have to stop and think. Not being able to scan code is an anti feature.

Ha, I'm the opposite. Every time I'm writing python I have to stop and think "is it response.json or response.json()?" And then I think about how Ruby (I think nicely) solved the attribute/method decision problem.

Re: Rye Language

#45
The first example is not convincing:

    lsp\ "prin"
It has two problems: - it's unclear why "prin", not "print"; - the usage of backslash looks scary.

Subsequent examples are also not good:

    bears .column? 'Area |unique
- overloaded syntax of '.' and '?' characters; - unbalanced quotes; - unbalanced whitespace around the '|' characters.

Re: Rye Language

#46
post #34

Hint: the "interactive" demos are scrollable by dragging the bottom. (Sadly, you don't have any access to the terminal window's scrollbar, so you can't just scroll to the end of the "video.") I still think a non-animated transcript of a terminal session is better.

Maybe that my wording is off. This are not interactive demos, but more like demos of interactive use in console ... "animated interaction demos". These use asciinema, which is a nice tool and I think it's good to display interesting interactions compactly. But yes, for deeper look it moves too fast for one, so something what you describe could be better. I could have these animations for getting attention and then li…

I think the
 tag with a bit of styling might do it?

Re: Rye Language

#47
It's cool and weird at the same time.

Cool because I'd like to think if someone made a Netflix tech drama loosely based around Bell Labs in the early 80's, this would language would appear in that series. A language created by some Nordic computer scientist who angrily shakes his fist at the world because it doesn't get adopted due to it's weird syntax. Of course instead we get Awk.

Re: Rye Language

#48
Q for Rye's author: Since Rye is heavily inspired by Rebol, I wonder if you had a chance to take a look at Red [1] and what are your thoughts about it. Red looks really cool and capable, but it feels so niche/obscure and has such a small community that feels unpractical to use.

--

1: https://www.red-lang.org/

Re: Rye Language

#49
post #28

Earlier quoted context omitted.

Ideally this would be a view setting, and could be enabled or disabled for different users without making edits to the code.

Yes, and IDE that would know the arity of functions (which is not totally simple, because of the very dynamic nature of the language) would be able to display the "parenthesis" or the grouping of function calls. I plan to make sort of visual editor for it too as an experiment so that could be a first demo of it.

I hope we see this kind of exploration with Unison, which is stored as an AST in a database and not as text.

Of course you could just take existing text from a codebase and reformat it for viewing, but then there's this ambiguity about which version is real that you'd have to deal with.

In Unison it's understood that none of the text is real, it's only the resulting AST and its hash that matters, so if you're seeing text at all you know it's just for your benefit in that moment. It's such a cool idea.

Re: Rye Language

#50
Hopefully Rye will support the dataframe interchange protocol. Then it can be easily used with existing visualization frameworks.
Post reply on HN