neut
Languages and libraries
programming language
SHOW HN2020
How HN took it
9 positive, 17 neutral or asking, 0 mixed, 8 critical, out of 34 comments about the project. Thread score +0.01.
Docs: 6 for, 1 againstIdea: 2 for, 2 againstDesign: 0 for, 3 againstPerformance: 0 for, 2 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Readme introduction is clear and approachable
From 3 comments
The introduction at the top of the Readme is great – it succinctly explains what the project does, how it relates to existing languages, and why the reader should care. Way too…
doersino on HNPersonally, I found the initial intro surprisingly easy to read and digest. I got double surprised when I noticed this is written in Haskell (IIUC) - for a thing created by a…
akavel on HNHeh, sorry, you're totally right, parts are definitively 100% Haskell-speak for sure (and I totally jumped over them with 0 understanding); what I really meant and failed to…
akavel on HN
Impressive commit history and dedication
From 1 comment
You are almost 3500 commits in to this project already, with no other contributors? The dedication to this is incredible. It sounds super compelling and I wish you luck! I hope…
lukevp on HN
Important research direction for memory management
From 1 comment
From a Rust perspective, this may be true. But from a Haskell perspective, this language promises to completely eliminate the garbage collector, which is a big deal.
amelius on HN
Objections
Readme is heavy on formalism and hard to follow
From 2 comments
It's kind of hard to decode the explanation given that it spends a lot of text on useless formalism instead of substance, but it seems like this language has three fatal…
devit on HNThe parent comment comes off as arrogant but so does this one. Oftentimes concepts like these are presented in language that's more impenetrable than necessary. I don't know if…
_bxg1 on HN
Lacks linearity in user-facing language and implicit allocation
From 2 comments
I'm pretty sure you're right on all counts; I'm not even sure that shared immutable borrows would work under the very simple transform given in the README. Edit: Also, the…
h-cobordism on HNyes, i found the first example quite surprising. there doesn't seem to be any request to copy the string; it is simply unintuively copied/produced three times. i would prefer the…
ferzul on HN
Shared mutable data and borrowing unclear or unsupported
From 1 comment
It's kind of hard to decode the explanation given that it spends a lot of text on useless formalism instead of substance, but it seems like this language has three fatal…
devit on HN
Requests
Clearer marketing and summary of key benefits
From 1 comment
You are almost 3500 commits in to this project already, with no other contributors? The dedication to this is incredible. It sounds super compelling and I wish you luck! I hope…
lukevp on HN
Explain how stack-allocated variables and borrowing work
From 1 comment
I didn't find an explaination of how it deals with variables (e.g. strings) allocated on the stack, does/how borrowing work for those?
rehemiau on HN
Mention linearity in the introduction
From 1 comment
The concept of linearity is referenced 21 times in various sections, but not in the introduction. As a first-time reader, I would appreciate if the introduction were to mention…
runeks on HN
Questions
How does it compare to Haskell/OCaml translation feasibility
From 1 comment
This looks amazing, albeit waaay over my head. The introduction says it "is made possible by translating the source language into a dependent variant of Call-By-Push-Value.".…
akavi on HN
How big is the runtime and can it be libc-free
From 1 comment
Super cool! Any idea how big the runtime is? Is it easy to run a libc free version? I honestly feel like the embedded/firmware slice of the stack desperately needs a next gen…
aey on HN
Is it based on CIC rather than pure CoC
From 1 comment
Since this seems to support inductive types, would it be correct to say that it's based on the calculus of inductive constructions (CIC), not the plain CoC? Basing a…
logicchains on HN
Alternatives named
Rust
From 2 comments
Jean Yang made a great analogy here: https://twitter.com/jeanqasaur/status/1262833050473259009 > Programming languages researchers are like fashion designers and "research…
panic on HNIt's kind of hard to decode the explanation given that it spends a lot of text on useless formalism instead of substance, but it seems like this language has three fatal…
devit on HN
Zig
From 1 comment
You are almost 3500 commits in to this project already, with no other contributors? The dedication to this is incredible. It sounds super compelling and I wish you luck! I hope…
lukevp on HN
Carp
From 1 comment
This reminds me a lot of Carp: https://github.com/carp-lang/Carp
milkey_mouse on HN
Cyclone
From 1 comment
Jean Yang made a great analogy here: https://twitter.com/jeanqasaur/status/1262833050473259009 > Programming languages researchers are like fashion designers and "research…
panic on HN