The Unison language
21–30 of 144 posts
Re: The Unison language
#22The name is already pretty taken.... https://en.wikipedia.org/wiki/Unison_(disambiguation)
Re: The Unison language
#23Re: The Unison language
#24Re: The Unison language
#25I really like the idea, I like the language, but the world will not be rewritten in Unison. A web assembly FFI story is needed for Unison to succeed.
Is this satire? Web assembly has no real adoption on the browser yet, is waiting for a standard I/O interface on the desktop to be useful and is itself the nth iteration of an old concept.
Large quantities of code can already be compiled to WASM. Since Unison works best with pure functions, most system interfaces would presumably be emulated. This emulation is already possible with Browsix.
Re: The Unison language
#26Seems like this could be implemented in other languages though, and don't really understand why we need yet another new language.
For instance, can I not build my JavaScript code in similar ways: I would need a compiler that stores things in trees rather than dirs.
Re: The Unison language
#27No, as I keep insistently repeating: Code is content-immutable and addressed.
Also, Urbit is a lie, Surface detail is true and you are a lie and your code is retarted.
Re: The Unison language
#28>>code is content-addressed and immutable. No, as I keep insistently repeating: Code is content-immutable and addressed. Also, Urbit is a lie, Surface detail is true and you are a lie and your code is retarted.
Re: The Unison language
#29Kudos to them for not using the buzzword, but if you believe in the notion that 'blockchain is just a fancy buzzword that gives developers the ability to get managers to agree to larger budgets to clean up tech debt', this is.. blockchain programming. One problem I did find: Somewhat deeper into the tour, the tour makes the claim: > a Unison codebase can be versioned and synchronized with Git or any similar tool and…
Re: The Unison language
#30Kudos to them for not using the buzzword, but if you believe in the notion that 'blockchain is just a fancy buzzword that gives developers the ability to get managers to agree to larger budgets to clean up tech debt', this is.. blockchain programming. One problem I did find: Somewhat deeper into the tour, the tour makes the claim: > a Unison codebase can be versioned and synchronized with Git or any similar tool and…
" I make the green 'OK' button now red, and you make it blue" I did not fully read the introduction yet, but in my mind, in a truly content-addressed system this is not a conflict: you have the hash of a main() function which ultimately makes the button red, and the other guy has a main() function that makes the button blue. No conflict in the physical sense. Yes, philosophycally there is a conflict, which is resolve…