top | item 46894532

(no title)

oneseven | 26 days ago

What I really want to see from a "*-programming-language" post on HN is _why_. Why Lily?

discuss

order

keychera|26 days ago

I am curious as well. some past readme has Why sections and I am not sure why they are removed/changed

this have "Why" section https://gitlab.com/FascinatedBox/lily/-/blob/d3ace2907747106...

this have "How Lily stands out from other languages:" section https://gitlab.com/FascinatedBox/lily/-/blob/785a88534cced53...

Nevermark|23 days ago

> More importantly, this design makes it easy to compose whole programs that will never be paused by a garbage collection by avoiding cyclical structures.

Or by "breaking" cycles, which will trigger the reference count deallocation.

andyferris|26 days ago

The README on gitlab at least has a sentence or two on that: https://gitlab.com/FascinatedBox/lily

> An interpreted language with a focus on expressiveness and type safety

Personally I think typed scripting languages could be the future. They should support AOT compilation where necessary.

bonesss|26 days ago

F# and C# are typed scripting languages. F# is quite similar to python in script form (.fsx), and has OCamls expressiveness, exhaustive pattern matching, and type inference. That results in highly expressive, terse, and ergonomic domain code.

The .Net VM now supports AOT compilation.

The future is now-ish :)

keyle|26 days ago

Why do you think that's the future?

Isn't a waste to essentially reinterpret an entire program that may be run 5000 times a day?

AOT compilation, how is that different than make && run?

At some point, you have a compiled language, if it's quick to compile, you're doing the AOT yourself, the scripting is an illusion. Pun intended.

nofriend|26 days ago

a statically typed aot compiled scripting language is... not

EagnaIonat|26 days ago

> why

Building a program language is like poetry. Everyone does it at some point, just most of us know never to share it.

saghm|26 days ago

That just moves the question to "why is this one being shared" then. I don't think "because the authors didn't know better than to avoid sharing it like 'most of us'" is a particularly good answer.

paulddraper|26 days ago

From the link:

> Key features of Lily:

> Built-in template mode

> Embed/extend in C

> Single-inheritance classes

> Exceptions

> Generics

> Algebraic data types (with Option and Result predefined).

andsoitis|26 days ago

That’s what. Not why.

poulpy123|26 days ago

99.9% of the time it will be "just because"