Generators to create

[unbalancedparentheses]

Generators to create

[unbalancedparentheses]

@igaray y @jfacorro can you help me on this while i finish gutenberg code?

You can use https://github.com/unbalancedparentheses/genserver-gutenberg-generator and https://github.com/unbalancedparentheses/supervisor-gutenberg-generator as examples for file generation.

[jfacorro]

@unbalancedparentheses I can do gen_fsm, gen_event and lasse cowboy. I'm not really sure what worker_pool is supposed to include.

[igaray]

@jfacorro lets sync up in the gitter room

[igaray]

@unbalancedparentheses @jfacorro
please review two new generators:
https://github.com/igaray/cowboy-rest-basic-gutenberg-generator
https://github.com/igaray/cowboy-rest-full-gutenberg-generator

[unbalancedparentheses]

No records please. In 99% cases they are superseded by maps. Since gut needs Erlang 17, we can use them.

[unbalancedparentheses]

I think it is better to add the comments of what a function do in top of the header of the function and not inside of it:
https://github.com/igaray/cowboy-rest-full-gutenberg-generator/blob/master/name.erl#L73

[igaray]

I disagree, as you said, maps do not replace all record use cases, and IMHO maintaining process state is precisely the 1%.

edit: comments moved outside of functions.

[unbalancedparentheses]

Why a reacord would be better for managing the state of a handler? It has the same feautres as a map but with much more cubersome syntax. Cowboy 2 will even use maps as the default.

We were using maps for managing state in all the new projects. Even brujo was the one that told me to migrate everything.

[unbalancedparentheses]

Why the long wait? - we wanted maps to be a replacement for records and to be as efficient as records, and its not blindingly obvious how to do so.
https://joearms.github.io/2014/02/01/big-changes-to-erlang.html

[unbalancedparentheses]

"Maps is the only dynamic key/value data structure in Erlang that we can match directly to extract values, allowing users to greatly simplify their code as they don't need to call functions to do everything anymore."
http://ninenines.eu/articles/cowboy2-qs/

Maps let's you code the same thing a lot less lines of code and you with a better syntax than records.

[unbalancedparentheses]

The only advantage of the records is that all keys are known at compile-time. In a LOT of cases you do not know all the keys at compile time in a http handler.

[jfacorro]

I think using maps makes the code a lot more readable. In my opinion there is no advantage to using records over maps, at least not when maintaining a process' state. Records are awkard to work with, maps are more flexible in all regards. There might be some use cases where records are preferable to maps, but I can't think of any.

That said, at the end of the day, 'tis all love.

[unbalancedparentheses]

We need an elli https://github.com/knutin/elli project. @jfacorro can you create one?

[unbalancedparentheses]

You can check: https://github.com/unbalancedparentheses/tinyerl/tree/master/elli

[unbalancedparentheses]

@jfacorro let me know when you have done elli project, gen event and worker pool so that I close the issue