Question: where is it used today?
It's not; it's incredibly alpha quality. Like, I'm working on a parser combinators library and step 1 was "add characters to the compiler."
Unison – A statically-typed purely functional language
21–26 of 26 posts
Re: Unison – A statically-typed purely functional language
#22Re: Unison – A statically-typed purely functional language
#23Earlier quoted context omitted.
When I read this: > If you look at what programmers spend their time doing when programming (other than thinking of course), it’s actually stuff like: > > - Adding imports to the code to be able to resolve names > It makes me wonder whether the authors have used a modern IDE in the past ten years. The video in this page is also showing nothing that hasn't existed for years in pretty much all IDE's under the sun.
If you skim it, it will look that way. What the editor is tackling has some overlap with common IDE features, but it’s taking a deeper approach to addressing them. You listed one item from a big list of tasks, but the more interesting thing is what’s written after the list about how unison addresses the items. And before demeaning the creators it may be worth it to look into their background a bit and see if it’s mor…
I am well aware of their background (I own their book) and this is precisely why I think they haven't used a lot of IDE's. Actually, these past years, I've heard a few times from one of them claiming that with a good language, one doesn't need an IDE.
Re: Unison – A statically-typed purely functional language
#24Re: Unison – A statically-typed purely functional language
#25Also a file syncing tool by the same name, written in the ... functional language Ocaml.
Re: Unison – A statically-typed purely functional language
#26Earlier quoted context omitted.
No, but it's also in the space of functional programming language research.
I don't think a file sync tool that happens to be written in OCaml qualifies as FP research.
That's fair, but it was written by Ben Pierce of the FP research community. It's nice not to have two projects named the same thing within the same community.