Live data from Hacker News

Unison 1.0

unison-lang.org

91–98 of 98 posts

Re: Unison 1.0

#91
post #11

I'm so old, I thought this was about Panic's Usenet client Unison.

Same, but I knew there was a v2 as I remember upgrading but I thought this was bringing it back. Oh well, fond memories of the web back in the early 2000s when I was just getting started doing web design, coding for fun back in my highschool days.

Re: Unison 1.0

#92
post #88

Earlier quoted context omitted.

That depends. What are you wanting to accomplish more broadly with the integration? I'll mention a couple things that might be relevant - you could have the git repo reference a branch or an immutable namespace hash on Unison Share. And as part of your git repo's CI, pull the Unison code and compile and/or deploy it or whatever you need to do. There's support for webhooks on Unison Share as well, so you can do things…

> What are you wanting to accomplish more broadly with the integration? For me that would be: - not lose my stuff - share with friends - let others contribute

Use Unison Share, it's great for all that!

https://share.unison-lang.org/

It's open source, you can create a free account with GitHub OAuth, and you can push projects there and collaborate on them, open PRs, publish releases, etc. It's very quick to pick up if you're already familiar with GitHub.

Re: Unison 1.0

#93

I have been following Unison for a veeery long time. Ever since those blog posts on Paul's personal website. It has been more than 10 years already so this is a great milestone. But I am just a bit disappointed. I love programming languages. I follow every programming language, even some you probably have never heard of. I have witnessed the rise of Rust, Go, Zig and others. At the age and level of polish that Unison…

Is anything locked into Unison Cloud, which is also free for unlimited services?

What would be enough?

Re: Unison 1.0

#94

If you ever need this kind of stuff, you'll be better off building your own distributed interface by using plain regular GHC Haskell and https://haskell-distributed.github.io/

`haskell-distributed` is awesome, but the reason Unison is a new language is exactly to avoid the limitations of such frameworks, namely that they _can't_ send arbitrary code and data around like Unison can.

You should totally write up a tutorial demoing the development of the same application using each. Folks would love that.

Re: Unison 1.0

#95

Also, hi, I'm one of the language creators, feel free to ask any questions here!

To what Unison is actually compiled to and how is it ran? Gemini LLM says it compiles down to Scheme with is then ran Chez Scheme, how much of an LLM hallucination is that?

Edit: I found https://www.unison-lang.org/blog/jit-announce/

Re: Unison 1.0

#96
post #95

Also, hi, I'm one of the language creators, feel free to ask any questions here!

To what Unison is actually compiled to and how is it ran? Gemini LLM says it compiles down to Scheme with is then ran Chez Scheme, how much of an LLM hallucination is that? Edit: I found https://www.unison-lang.org/blog/jit-announce/

That information is a bit out of date, though correct at the time. We've put the Chez Scheme interpreter on ice, and we focused on runtime improvements to the Haskell interpreter. So, currently, Unison compiles to Haskell.

Re: Unison 1.0

#97
post #77

Also, hi, I'm one of the language creators, feel free to ask any questions here!

Thanks for your work! Who wrote the big idea post? https://www.unison-lang.org/docs/the-big-idea/

By and large, our CEO did, but the website content is open source and has been iterated on by many hands over the years. If you have suggestions, feel free to drop a note in a ticket: https://share.unison-lang.org/@unison/website

Re: Unison 1.0

#98

If you ever need this kind of stuff, you'll be better off building your own distributed interface by using plain regular GHC Haskell and https://haskell-distributed.github.io/

`haskell-distributed` is awesome, but the reason Unison is a new language is exactly to avoid the limitations of such frameworks, namely that they _can't_ send arbitrary code and data around like Unison can. You should totally write up a tutorial demoing the development of the same application using each. Folks would love that.

> but the reason Unison is a new language is exactly to avoid the limitations of such frameworks

by introducing another set of limitations that Unison docs don't state upfront, because it will affect their progression as the business.

> namely that they _can't_ send arbitrary code and data around like Unison can.

> You should totally write up a tutorial demoing the development of the same application using each. Folks would love that.

You should add "out of the box", and that "like Unison can" isn't the only way to implement a distributed runtime. This leads to another logical question: why should I "totally write up" the Unison way of things? At this point I'm not even sure that 99.999% of workloads need distributed runtimes of any kind, let alone the Unison one.

Post reply on HN