[erlang-questions] Process scope variable

Rad Gruchalski radek@REDACTED
Thu Feb 19 18:41:10 CET 2015

On Thursday, 19 February 2015 at 16:16, Imants Cekusins wrote:
> > If you could pick between fast and wrong agile and slow and correct agile, what do you choose?
> the goal is fast and correct agile.
I started learning Erlang about 10 months ago. Frankly, I like not having state and classes.

To me it sounds like you’re reinventing Scala. Try Scala, it’s not terrible, it’s way better than Java, you can do functional or imperative, the code may look very nice if you know Scala well. You have to try hard to stay functional so it sounds like a perfect fit for you. It seems you don’t get the functional programming yet. You just need more experience.

I would suggest the following: leave what you’re doing now on the side, read “Designing for scalability with Erlang/OTP” and write the examples yourself. This is how I started. It was an eye opener.
> I may run into unexpected technical problems. Time will tell.
> Remember: when the app design is largely over, it is still possible to
> take away the "state" gs, beef up fun signatures and pass the state
> around - test & deploy the program refactored to correct way. I do not
> mind long signatures when the design is not going to change.
> Work in progress will however be faster with the "state" gs.
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED (mailto:erlang-questions@REDACTED)
> http://erlang.org/mailman/listinfo/erlang-questions

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150219/529626e5/attachment.htm>

More information about the erlang-questions mailing list