News for hackers. Stuff that matters.

aryairani

Re:Unison 1.0 Release on Sunday November 30, 2025 @01:20AM (#46094336)
`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 Release on Friday November 28, 2025 @01:19PM (#46081230)
Is anything locked into Unison Cloud, which is also free for unlimited services?

What would be enough?

Re:Unison 1.0 Release on Tuesday November 25, 2025 @07:45PM (#46052750)
I don’t totally understand the question (what’s a regular cycle?), but the only sort of cycle that matters is a strongly connected component (SCC) in the dependency graph, and these are what get hashed as a single unit. Each distinct element within the component gets a subindex identifier. It does the thing you would want :)
Re:Unison 1.0 Release on Tuesday November 25, 2025 @07:36PM (#46052700)
(All Unison values can also be decompiled into an AST anyway.)
Re:Unison 1.0 Release on Tuesday November 25, 2025 @03:49PM (#46050605)
There's an algorithm for it. The thing that actually gets assigned a hash IS a mutually recursive cycle of functions. Most cycles are size 1 in practice, but some are 2+ like in your question, and that's also fine.
Re:Unison 1.0 Release on Tuesday November 25, 2025 @03:46PM (#46050561)
No, Unison has its own native version control, and a code sharing platform at https://share.unison-lang.org
Re:The Programmer Identity Crisis on Wednesday October 22, 2025 @10:36AM (#45669772)
> There aren’t enough swear words in the English language to adequately describe how frustrating computers and programming can be, but we have at least always been able to count on them for precision: to perform exactly as instructed through programming.

This is so true. That feeling when you're debugging an issue in your code, only to rule out all the possibilities and have to expand your search to include not-your-code: the tooling, the libraries, the operating system, the hardware. This is the worst feeling in debugging, when the problem and the solution /might/ be outside of your control. With LLM/GenAI, the primary problem solving surface is nondeterministic by design, very much out of your control, and you will likely be gaslit into believing that you're just not hitting it right. Like a tube tv that has to be slapped just the right way to restore proper reception. (Sorry, bots, no offense intended.)

> What’s next, TPS reports?

I bet LLMs are really good at producing TPS reports w/ cover sheet.