hckrnws

You do a good job on explaining the what of the language, but I cannot quickly find the why of the language. What is the language's purpose? Why should or could I use it?

Agreed. Feels like "a scripting language for C developers who hate JavaScript"

That can be a decent "why" though...

I feel like I keep harping on about Nushell but as scripting languages go it's right up there for me. Built with rust too and comes with a ton of stuff built in.

What's the niche this fills? I came across roc-lang recently which seemed interesting too, again built with rust, and opinionated on certain things common in older languages.

It doesn't have to, and obviously it's your project, but what is this offering over other languages. Why would I reach for it?

I hadn't really looked at Nushell, but it (process control) is definitely something I plan to improve in Aria (https://github.com/egranata/aria/issues/21). Right now I have a simple system() wrapper, but not much in terms of advanced subprocess control. Maybe worth investing some time in cleaning up?

I have tried to fill the niche of "scratch my itches, please", which means Aria is intended to feel smooth, pleasant and simple to write in. There are still things I want to improve before calling it a 1.0, but the general theme is, a general purpose scripting language with just enough structure and as little ceremony as possible.

It may be that I struck the wrong balance somewhere (and I know of a few places, e.g. operator overloading - I plan to rewire the syntax), and that would be great to get eyes on and get feedback!

Just a side note, roc-lang is being rewritten in Zig[0]

[0] https://gist.github.com/rtfeldman/77fb430ee57b42f5f2ca973a39...

What would this offer me over more established scripting languages? Main thing I want to know when I see a new offering. On a quick look I find the almost but not quite C syntax more difficult to read, like the lack of parenthesis on the if statement's test and this is my biggest issue with C like languages, they change things just enough that I have to think about it and I don't see what the change offers beyond those used to C syntax having to stop and think.

Good news is I can offer you parentheses, but they are indeed optional on conditionals/loops. I am fairly sure there are other C-style syntaxes that leave those out. See https://stackoverflow.com/questions/2061593/why-do-c-languag... - you can't have the same ambiguity if you have mandatory braces around the body. Would there be a reason to require them?

With that said, this will work just fine and you wouldn't have to think about it too hard, if at all:

  func main() {
    if (1 == 2) {
      println("oh no!");
    } else {       
      println("phew!");
    }
  }

Mileage may of course vary and you may think that balance is actually nowhere to be seen. That's great, hit me with it.

Judging from the small example in the readme, the language looks pleasing to the eye.

What’s under the hood though? What are some of the technical choices, performance characteristics and longer term goals?

The current implementation looks like a compiler to a stack-based bytecode with a straightforward textbook interpreter. For example, here is the interpretation of the Add bytecode: https://github.com/egranata/aria/blob/master/vm-lib/src/vm.r...

So to a very rough first approximation, performance characteristics should be in CPython's ballpark.

Does it support higher-kinded types and typeclasses? Does it support call-site expansion?

Why the name conflict with aria the technology?

[dead]

[flagged]

I think it's cool that someone is creating a language specifically for creating a piece of music for just one voice!

What do you mean, not that aria[1]?

[1]https://en.wikipedia.org/wiki/Aria

I think it’s cool that someone is writing a language to find information about the Russian heavy metal band.

https://en.wikipedia.org/wiki/Aria_(band)