As the author of at least one HTTP server library ( https://github.com/andreaferretti/rosencrantz ) do you find anything missing in its documentation?
Re:Nim in 2018: A short recap
by StreamBright on Wednesday January 09, 2019 @10:36AM
(#18865459)
It is actually really nice. Thanks for the link!
- As far as I know Jester is the go-to for your webservers and you could use the httpclient in the standard library.
- This is true and there are plans to improve it, if you have any feedback on what could be clearer, you can share your thoughts here: https://forum.nim-lang.org/t/4523
Re:Nim in 2018: A short recap
by StreamBright on Wednesday January 09, 2019 @10:38AM
(#18865476)
Jester is great if you can ask the author why does it do what is does. There are lots of implicit stuff going on and I had no time to figure out why the server starts up once I create routes.
Seconded, but I had the same problem with Elixir and Plug/Phoenix. It looks like the communities of new languages with macros need some time to mature and settle on some kind of style guide for when and how to use them. In all the Lisps I know - Clojure, Common Lisp, Emacs Lisp, Scheme, Racket - the use of (new) macros is discouraged for the most part (at least on the surface, I'm not counting using `loop` in CL or `for` in Racket). It will get much better with time, I think, but I guess there is some truth to people saying that including macros in the language can be "dangerous" :)
I agree also on the point about documentation, this practice was also extended to the community modules (but everything was new and hacky so I thought it was OK, but it ended up being the rule a the ecosystem).
Re:Nim in 2018: A short recap
by StreamBright on Wednesday January 09, 2019 @10:40AM
(#18865501)
If you develop a new piece of software, especially a new language, documentation should be there so that the users can get in as fast as possible. I think Elixir is a great example in this regard that Jose paid attention to this feedback early and there is decent documentation for most of the things nowadays (minor exceptions). I have limited time and there are so many new languages, I will go with the one which has the lowest entering barrier.
I would like to add 2 more things:
- there are at least 3 incomplete logging and http server libraries (please provide documentation if you want anybody to use your library)
- documentation is not always clear how to use the language