News for hackers. Stuff that matters.
Re:Caramel: an Erlang back end for OCaml by giantDinosaur on Sunday September 27, 2020 @08:45AM (#24606232)
How does one avoid type errors in Erlang applications? If the answer is 'testing' then types are indeed an obvious gap in the language. If it's something else, I'm genuinely interested to know. What makes Erlang so special that a lack of types actually aids (or at least does not at all hinder) in long-term maintenance/refactoring or enforcing type-level constraints on values?
Re:Caramel: an Erlang back end for OCaml by loxs on Sunday September 27, 2020 @09:02AM (#24606321)
After many conversations on the topic with good to great Erlang programmers (I also have 7 years of experience under my belt) I come to the conclusion that they just "don't get it".

Probably there is a subset of extremely smart people who can write good and very reliable software in a dynamic language without going mad, but I am not among them. In the end I just left the language and now I am much happier with a mix of TypeScript, OCaml and Rust

Also the reliability they are talking about is quite different from the reliability that most people (especially ones who have not worked on erlang-y systems) think of when they hear the word. The Erlang reliability is about finding bugs and patching them (often in production) and not about avoiding them in the first place. Also it's about avoiding total system failure because of some bug in a part in it. This is a nice to have thing in all systems, but Erlang makes it easier to implement.

Of course, they also like to avoid bugs, but for that they use testing. And of course, we have to mention dialyzer which is something like TypeScript for Erlang but a lot less polished and with practically no tooling support. It is used in every significant Erlang project but the process is IMO quite sub-optimal and the price you pay (in suffering) is quite high.

Re:Caramel: an Erlang back end for OCaml by lostcolony on Sunday September 27, 2020 @10:23AM (#24606848)
'Of course, they also like to avoid bugs, but for that they use testing.'

This is kind of the key bit.

To caveat this - I'd like better typing in Erlang, and when i last used it in production I added type annotations to everything and ran Dialyzer as part of the build. But this is personal preference, and I'm not convinced it was the best use of my time; just the most conservative way to approach things for a system I needed extremely high uptime on.

You have to write tests anyway. Just because a statically typed system compiles doesn't mean your test load is reduced. While it eliminates certain classes of bugs, those same classes mostly get covered just by writing functional tests of sufficient coverage.

Between that, and Erlang's supervision tree (so that if you DO get a type error at runtime, it would be in a path you haven't adequately tested, and so not your expected 'happy path', and as such, can reasonably be restarted), it strikes me as a reasonable position to take.

Re:Caramel: an Erlang back end for OCaml by loxs on Sunday September 27, 2020 @01:25PM (#24608325)
Regarding dialyzer: Yes, it's sane to use it although it's a massive PITA, especially when you have to collaborate with people who do not write type annotations or use such libraries.

Regarding testing - I think it depends on the type of application you are writing. If you need 99.99% uptime, probably you have to have almost full test coverage.

But for the kind of software that I write (at least lately), I rely on "let's make illegal states unrepresentable" to a large degree, then write a small number of regression tests (or fix the types) when we find bugs... This has proven (at least to me) to be good enough, especially compared to my clients' previous experience, which is usually very poor: extremely buggy software in a dynamic language with almost no tests and docs. Perfect quality is usually not needed or at least not worth the price.

Re:Caramel: an Erlang back end for OCaml by coldcode on Sunday September 27, 2020 @09:34AM (#24606491)
I've never worked in Erlang, but I did use Objective-C for a long time, and switched to Swift almost 5 years ago. Strong types makes it massively easier to ship high quality applications, while I could do so in the C variant it took a lot more effort and testing. In Swift I can make the language make it almost impossible to create erroneous code.

It's not that you can't make good code in any language, but the cost is often not worth it; anything that makes it easier and more reliable saves you time and effort in the long run.

Re:Caramel: an Erlang back end for OCaml by Multicomp on Sunday September 27, 2020 @10:29AM (#24606899)
Your last paragraph is why I enjoy F# and rust as much as I do. If the computer can do more to help you make illegal States unrepresentable then why not let it?

Hence I am waiting on Gleam before I invest in Erlangy stuff. In the meantime I will explore the actor model of concurrency with F# Mailboxes.

Re:Caramel: an Erlang back end for OCaml by loxs on Sunday September 27, 2020 @01:18PM (#24608238)
Yes, for me the big revelation was when I learned OCaml (coming from Erlang) it was such a massive relief, it felt like half of my brain got freed to think about things that matter. After that, once it clicked, most languages of this caliber feel "at home" and I can use them quite easily - F#, Rust, Swift, TypeScript.
Re:Caramel: an Erlang back end for OCaml by filmor on Sunday September 27, 2020 @09:00AM (#24606314)
Erlang doesn't lack types. It's also strongly typed. You can get quite far with properly chosen guard expressions (`is_binary`, `is_number`), general pattern matching and Dialyzer to check what's checkable.

Static typing severely hinders hot code-reload, which was deemed more important for long running systems.

Re:Caramel: an Erlang back end for OCaml by loxs on Sunday September 27, 2020 @09:03AM (#24606328)
These are runtime checks and have nothing to do with what most people understand under the term "static typing/types".
Re:Caramel: an Erlang back end for OCaml by filmor on Sunday September 27, 2020 @04:36PM (#24609954)
Just to be clear, I intentionally never said anything about static types. The type system is "strong" in the sense that variables never change their type or are "interpreted" based on context, they don't even change their value after assignment.

And whether your types are runtime-checked or statically checked doesn't really matter with regard to the invariants that hold for your code. In the former case, you'll have to be able to handle type errors at runtime as well, which is reasonably easy in Erlang due to the strong isolation it provides.

Re:Caramel: an Erlang back end for OCaml by igouy on Sunday September 27, 2020 @11:11AM (#24607199)
Dialyzer is a static analysis tool.

https://erlang.org/doc/man/dialyzer.html

Re:Caramel: an Erlang back end for OCaml by loxs on Sunday September 27, 2020 @01:09PM (#24608154)
It is, but is_number is not, which I am replying to. Probably should have mentioned, my bad...
Re:Caramel: an Erlang back end for OCaml by andrenth on Sunday September 27, 2020 @11:31AM (#24607368)
Pattern matching and immutability help a lot in practice, even with dynamic types.
Re:Caramel: an Erlang back end for OCaml by loxs on Sunday September 27, 2020 @01:30PM (#24608372)
Absolutely. Somebody, somewhere used to say that Erlang is neither static, nor dynamic typing, but somewhere in the middle. I can agree to a large degree.
Re:Caramel: an Erlang back end for OCaml by toast0 on Sunday September 27, 2020 @04:33PM (#24609938)
> How does one avoid type errors in Erlang applications?

When I write Erlang, I'm not necessarily concerned with avoiding errors. The philosophy of the system is that errors will occur, and the focus is on making sure errors do not compound into system failure (supervision tree helps with this), that they're easy to see (appropriate logging of crashes), and that it's easy to deploy fixes (hotloading).

I'm sure there are many ways to avoid some errors in production, but more focus is on responding to errors than on preventing them. At least in my experience.

Re:Caramel: an Erlang back end for OCaml by didibus on Sunday September 27, 2020 @01:20PM (#24608262)
> If the answer is 'testing' then types are indeed an obvious gap in the language

Will you not be testing your code anyways? Will you not have unit tests and integ tests and have it run in a devo environment first? Before going to production?

If so, then what would the gap be? If you catch those same type errors as you test, and you will be testing anyways?

Re:Caramel: an Erlang back end for OCaml by lttlrck on Sunday September 27, 2020 @03:34PM (#24609493)
Surely catching the errors early is a benefit, or are all typed languages doing it wrong?
Re:Caramel: an Erlang back end for OCaml by didibus on Sunday September 27, 2020 @04:52PM (#24610053)
Is your argument for it being a benefit that there are lots of languages doing so? Cause there's just as many dynamic languages not doing so, so I'm not sure this argument takes us anywhere.
Re:Caramel: an Erlang back end for OCaml by loxs on Sunday September 27, 2020 @01:47PM (#24608542)
Depending on the project, I have (not) done all of these and given adequate system (mostly types) design, it's been absolutely OK.