Live data from Hacker News

Rye Language

ryelang.org

51–60 of 61 posts

Re: Rye Language

#51

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/

I was/am a Rebol developer, and all Rebol developers know about Red as it was/is the next of Re(d|bol) languages, after we came to terms that the Rebol 3 which was about to concretely improve on Rebol 2, and be open source just won't happen.

Red also improved on Rebol 2 a lot and is a proper Rebol successor. It was started by a very productive and prominent Rebol developer, that I greatly appreciate. The only problem I see with it is that maybe they were too ambitious. They started with their own low level language (compiler) Red/system, and out of that built Red interpreter. They are really doing things as they should be done I think, but it's taking quite a lot of time.

Red, like in a way Rebol has a lot of focus on GUI and I needed a language for backend development. I was waiting for their "IO branch" for years, it was hard for me to contribute in a concrete way, since their approach was quite low level and at around 2018 started making a simple Rebol like interpreter in Go, because Go is great on the backend and I just wanted something that works, hence the higher level language than C/C++, that's now Rye.

Red is still moving forward, their community is mostly on gitter I think. It is small, but so was Rebol's and it's much bigger than Rye's, which doesn't really have a community yet :).

Re: Rye Language

#52

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.

Slavic, not a computer scientist, more of a lumberjack, otherwise very funny comment :)

Weird syntax might be just awesome syntax you don't yet know :)

Re: Rye Language

#53
post #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.

Attribute access and method access don't imply the same consequences on perfs and side effects, I like to know which is which.

Re: Rye Language

#54
post #50

Hopefully Rye will support the dataframe interchange protocol. Then it can be easily used with existing visualization frameworks.

I haven't heard about this one yet. Rye has "spreadsheet" datatype which is humanized dataframe basically. I will look into this, thanks!

Re: Rye Language

#55
post #39

Wrote my first hello world and http server to get the ticker starting on “Rye Lang X years of experience” Can’t wait for the “10 yeass of experience in Rye Lang [in 2026]” job posts from clueless recruiters

I like the optimism :)

Re: Rye Language

#56

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.

There are few conventions with Rye language. Variations of functions use \ character. Like. print , print\csv or read , read\lines ... these are separate functions, with similar goal, but most of the time different arguments.

There is a sub-convention that word\ just means like word(more), which usually means one (most obvious) additional argument. function `ls` lists current context and `ls\` accepts string, in this case "prin" and list all arguments that match it.

Rye (similar to Rebol) relies on multiple types of words to replace syntax (if that makes sense) and these types of words are denoted by specific characters at the start or the end usually.

.word is and op-word and takes first argument from the left |word is a pipe-word and is similar to op-word, but with different priority (more on that you can see on the website) 'word is lit-word (literal-word) ... quoted word in lisp terms (I suspect)

? at the end is a convention for "get" ... so noun? would mean get-noun ... so height? is convention for get-height. This is temporary "in testing" convention but so far it seems to function OK.

Thanks for your feedback.

Re: Rye Language

#57
post #51

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/

I was/am a Rebol developer, and all Rebol developers know about Red as it was/is the next of Re(d|bol) languages, after we came to terms that the Rebol 3 which was about to concretely improve on Rebol 2, and be open source just won't happen. Red also improved on Rebol 2 a lot and is a proper Rebol successor. It was started by a very productive and prominent Rebol developer, that I greatly appreciate. The only problem…

Super interesting, thanks for sharing!

Re: Rye Language

#58
post #51

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/

I was/am a Rebol developer, and all Rebol developers know about Red as it was/is the next of Re(d|bol) languages, after we came to terms that the Rebol 3 which was about to concretely improve on Rebol 2, and be open source just won't happen. Red also improved on Rebol 2 a lot and is a proper Rebol successor. It was started by a very productive and prominent Rebol developer, that I greatly appreciate. The only problem…

btw, can you talk a bit more about how you came in touch with Rebol, what do you and other people use Rebol for, and if you are already using Rye for production apps?

Re: Rye Language

#59
post #5

FYI, Rye is the name of a tool that's gaining popularity in the Python world. https://github.com/astral-sh/rye

I believe the astral devs plan to eventually merge rye into their “uv” tool, so this may end up being a self-correcting problem

Re: Rye Language

#60
post #5

FYI, Rye is the name of a tool that's gaining popularity in the Python world. https://github.com/astral-sh/rye

I believe the astral devs plan to eventually merge rye into their “uv” tool, so this may end up being a self-correcting problem

I was hoping for something like that when I saw the news about rye + uv / astral.
Post reply on HN