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].
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.
As far as I can tell, the only languages with Haskell-like syntax that have tried for serious industry adoption are Haskell, Scala, and perhaps Elm. (Idris is a borderline case, but it’s young and in any case I think we’re still a couple generations away from viable total languages.) Each of these has unconventional and similar semantics, different but complex type systems, and is trying for general applicability, while Nix has somewhat different semantics and no static type system at all, and is also trying to cover a very limited application area. Even Nix’s syntax, to my eye, is about as ML-like as it is Haskell-like.
How can we be so sure it’s the syntax, specifically, that is the problem? Are we controlling for these differences in any way at all?
It would be another matter if F# or OCaml or even Dylan was a runaway success while Haskell was not; while strict vs lazy is a hell of a difference I could be convinced that the syntax is the problem if people from the industry tried one after the other and consistently backed off in disgust, but that is not happening as far as I can tell.
I really don’t see how the verdict here could be anything but a definite “inconclusive”.
Finally, I’m also not seeing why I want industry acceptance. (I don’t think Xe’s post discusses it at all.) I want to use it, I want other users to discuss it with, I want it not to die a slow unmaintained death in five to ten years, but otherwise... Meh?
Advocating it to a single organization seems like a limited task (which I might fail), but advocating it to “the industry” seems like arguing with a force of nature (and I will fail). There would be some advantages to me if it were adopted, but then again it’s a first-generation system that has already accumulated substantial legacy cruft, so maybe I don’t want it to be adopted as it is now? Exploring the solution space? Definitely. Adoption at this particular stage? Not really sure, hard to get worked up about it.
P.S.
>> 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 [...]
Wrong kind of “respect”, sorry: not how much I trust it, but how much concrete information I can expect to squeeze out of it (complete trust helpful, but neither necessary not sufficient). Opinions of large groups of people, even if reliably known, are notoriously hard to turn into actionable insights.
What?? Galois, Facebook, IBM, Twitter, AT&T, Bank of America, Barclays Capital, NVIDIA, Microsoft and GitHub use Haskell.
So? The usage of Haskell within the entire industry is so small it's not even a rounding error.
It's hard to make the argument that the industry has accepted it when the industry usage is too tiny to even measure properly.
Programmers, and the work they do.
> and explain what credentials you have to know what "they" want.
It sounds ridiculous that you need "credentials" before you'd believe that Javascript, Python, Java or C# programmers, programs, projects and work doesn't each outnumber Haskell roughly 100 to 1.
Just about any metric you choose to use to evaluate what the industry uses, Haskell has so little usage that it's literally difficult to measure.
Job postings, TIOBE, RedMonk, SO survey, google-fight, you name it - Haskell is nowhere near rounding error percentages.
Maybe you should ask yourself why it doesn't show up in significant numbers on any metric rather than asking people what credentials they have.
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.
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.
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/ > 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 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.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.
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.
Before the iPhone no one knew they wanted a good camera and "apps" on their phone.
See the important point here -> "knew they wanted"
> 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.
I literally claimed otherwise, elsethread
> It's a reflection of what the programmers want. Apparently they wanted syntax with braces and semicolons.
Javascript, C, C++, C#, Python and Java have seen and are still seeing heavy use in the industry. Go has gotten traction too, now.
Any language that can be seen on a common metric to be more than low single-digits (and, in some cases, fractions) of a percentage can be safely said to be "used in industry". I cannot think of any survey amongst programmers which shows Haskell usage outside of 1%-3%.
I really don't know why you think that true:
https://wiki.haskell.org/Haskell_in_industry
And i really don't know why you speak for "programmers", just speak for yourself...maybe?
> 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.
FWI HN was not written in JavaScript or PHP but you can lookup that for yourself.
Nowhere did I claim that - you're reading things I did not say.
Claiming that something is rejected by everyone does not make any statement on the quality of that thing.
[EDIT: It's kinda common knowledge that Haskell is barely used in industry. I cannot remember coming across a single non-academic programmer in the workplace who actually wanted to use it, other than myself]
It should be clear now, that this is a wrong statement.
> It should be clear now, that this is a wrong statement.
You're correct - it's rejected by roughly 999 out of every thousand programmers.
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.
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.
> 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.