5 ms·
>> Using Haskell as a base for the syntax > I don’t really think this is a problem at all? Of course it's a problem. You shouldn't use a syntax that has been
by lelanthran 5y ago
>> Using Haskell as a base for the syntax
> I don’t really think this is a problem at all?
Of course it's a problem. You shouldn't use a syntax that has been soundly rejected by the industry.
- rowanG077 5y agoBecause industry makes good decisions? Decisions like adopting python, dooming a large part of the world software to be bug ridden slow messes. Or to elevate CUDA to the facto machine learning backend? Besides it's not clear that Haskell isn't adopted by industry due to the syntax.
- lelanthran 5y ago> Because industry makes good decisions? That's irrelevant - if you want uptake, you need to support what user's want. It's been clear for at least a decade now that programmers don't want Haskell syntax. Whether it's a good syntax or not is irrelevant.
- rowanG077 5y agoWhy do you think it's Haskells syntax that is the problem? The syntax is not so weird. I'd say the semantics are the hangup. 100% purity and lazy evaluation are a much harder pill to swallow then the syntax.
- lelanthran 5y ago> Why do you think it's Haskells syntax that is the problem? The syntax is not so weird. I'd say the semantics are the hangup. 100% purity and lazy evaluation are a much harder pill to swallow then the syntax. Could very well be - either way the language has been rejected. Boasting of Haskell characteristics[1] is, IMO, a great way to turn off prospective users. [1] I don't really know if the Nix project actually does blog posts and reachouts where they boast of Haskell-ish similarities.
- rowanG077 5y agoI don't really see that industry has rejected Haskell at all. Haskell target simply wasn't (or isn't) industry. You can't really be rejected if you aren't trying to get into that niche. And Haskell has seen significant industrial use. So they succeeded at something they didn't even want to succeed at.
- nix23 5y ago>if you want uptake, you need to support what user's want Before the iPhone no one knew they wanted a good camera and "apps" on their phone. See the important point here -> "knew they wanted"
- lelanthran 5y ago> >if you want uptake, you need to support what user's want > Before the iPhone no one knew they wanted a good camera and "apps" on their phone. > See the important point here -> "knew they wanted" Haskell has been around now for something like 25 years. You'd have a point if the iPhone was unpopular for 25 years before users finally decided to like it. It wasn't. Users saw the iPhone and wanted it the minute they saw it. Programmers have been looking at Haskell for 25 years and rejecting it.
- nix23 5y ago>Programmers have been looking at Haskell for 25 years and rejecting it. I really don't know why you think that true: https://wiki.haskell.org/Haskell_in_industry https://wiki.haskell.org/Haskell_in_industry And i really don't know why you speak for "programmers", just speak for yourself...maybe?
- lelanthran 5y ago>> Programmers have been looking at Haskell for 25 years and rejecting it. > I really don't know why you think that true: Because it doesn't show up any any metric as having significant usage. A list of 100 companies using it doesn't make the hundreds of millions of other companies not using it go away.
- nix23 5y agoYour argumentation is just completely wrong, you think that "significant usage" is some kind of "quality". You try to argue that a hammer and a screwdriver are of significant usage, when i fact the best tool for the job is a scalpel. FWI HN was not written in JavaScript or PHP but you can lookup that for yourself.
- tiew9Vii 5y ago> That's irrelevant - if you want uptake Haskell's slogan is "avoid success at all costs". Haskell isn't aiming for mass adoption. It wants to be a language for researching functional programming, it just so happens it's a useful language, and people write real software with it too. From https://haskell.foundation/whitepaper/ https://haskell.foundation/whitepaper/ > Haskell's slogan of "avoid success at all costs" was a clever and cheeky way of saying that innovation and research in programming languages, especially in functional programming, needed some insulation to succeed Nix doesn't have such a slogan as far as I know. It, however, started as a thesis to try and research and innovate new ideas. https://edolstra.github.io/pubs/phd-thesis.pdf https://edolstra.github.io/pubs/phd-thesis.pdf The Purely Functional Software Deployment Model. Twenty years later, it's been rather successful as a research project, one of the most active repos on GitHub. It has gained a lot of usage and support without trying to be successful, popular or market itself. The Nix language has helped it achieve what it set out to achieve. It's appealing to people who are interested in purely functional software. If that doesn't appeal to Javascript / PHP devs that's ok as it isn't trying to appeal to them. The Nix expression language is small and pretty simple; everything is an expression. The difficult bit is there are no javadoc/jsdoc/pydoc type docs beyond https://nixos.org/manual/nix/stable/expressions/builtins.html https://nixos.org/manual/nix/stable/expressions/builtins.htm... where you can go search easily. You have to go through the source code to find functions and see how they work. Also, you have to accept Nix is a ML style language, not a C style language. It's different to what you may know, but that isn't a fault of the language if someone only knows C style languages. The language is as it needed to be like that to achieve the design it wanted. Personally, I hate using Ansible firstly because of YAML. Secondly, Ansible is a task runner, often feeling like you are over abusing Ansible for things that are not a natural fit, and the debug headache dealing with determinism by convention only. I think it comes down to Nix isn't for you. That's ok.
- lelanthran 5y ago> Haskell's slogan is "avoid success at all costs". Haskell isn't aiming for mass adoption. It wants to be a language for researching functional programming, it just so happens it's a useful language, and people write real software with it too. This isn't well-known - read through this thread - their are many people in this thread who deny that Haskell usage in industry is insignificantly small.
- ge96 5y agoHeh, there's a project I'm trying to get into and it's written in Haskell, I gotta learn it... if possible I'm probably going to port it to something else.
- mananaysiempre 5y agoOK, fair enough, not an—independent? terminal?—problem: the syntax is largely forced upon us by the semantics, it’s not a Common Lisp vs Dylan or a Python vs Lua vs Ruby thing; and the semantics is the crux of the implementation approach (though not of the packaging organization being implemented). If you want to argue against the semantics, by all means, but “industry doesn’t think it looks pretty” does not cut it, even “I don’t think it looks pretty” would afford more respect on my part (not least because the speaker is then able to explain what specifically they find off-putting or annoying, while “the industry” isn’t). More details on syntax vs semantics in sibling comment[1]. [1] https://news.ycombinator.com/item?id=31143616 https://news.ycombinator.com/item?id=31143616
- lelanthran 5y ago> If you want to argue against the semantics, by all means, but “industry doesn’t think it looks pretty” does not cut it I'm not arguing against semantics, and "the industry doesn't think it looks pretty" is not my argument either. My argument is that, if you want the industry to accept something, it needs to be acceptable to the industry. Haskell-ish syntax[1] has clearly been unacceptable to the industry for a long time. It's been rejected, again and again. At this point, it is pretty much guaranteed that attaching Haskell syntax to your new config format/language/application/whatever is a recipe for failure. It's not that the industry just thinks it looks ugly, it's that the industry has outright rejected how it looks. > even “I don’t think it looks pretty” would afford more respect on my part My opinion on Haskell syntax, and whether or not you respect my opinion, is also pretty much irrelevant if the industry has already rejected it. I could be thinking that it's the best thing since sliced Jesus, but that won't change the fact that the syntax of Haskell has been rejected by the industry. [1] Amongst others.
- nix23 5y ago>has clearly been unacceptable to the industry for a long time. What?? Galois, Facebook, IBM, Twitter, AT&T, Bank of America, Barclays Capital, NVIDIA, Microsoft and GitHub use Haskell. https://wiki.haskell.org/Haskell_in_industry https://wiki.haskell.org/Haskell_in_industry
- tasuki 5y ago> soundly rejected by the industry That same industry which embraced PHP and JavaScript? Is that an authority, on what? Also, the industry hasn't rejected Haskell, it has just been learning from it very slowly. My prediction is this trend will consistently continue at the same glacial speed.
- lelanthran 5y ago> That same industry which embraced PHP and JavaScript? Is that an authority, on what? It's a reflection of what the programmers want. Apparently they wanted syntax with braces and semicolons. Someone else pointed out elsethread that maybe it's not the syntax, but the semantics, that is being rejected here.
- taktoa 5y agoNix syntax has braces and semicolons... the only similarity to haskell is in using juxtaposition for function application (though this is technically optional; nothing is stopping you from typing f(x))