3 ms·
Mercury is probably developed and maintained by a very small, even single-perrson team, at this point, so there's most likely an issue of how to best allocate r
by YeGoblynQueenne 8y ago
Mercury is probably developed and maintained by a very small, even single-perrson team, at this point, so there's most likely an issue of how to best allocate resources. Perhaps the language designers just can't afford a sleek, web-based documentation system, such as other languages have.
Let's also not forget that, just because someone understands how to design and implement a really cool programming language, doesn't mean they understand how to perform "marketing and good communication". And vice-versa. These are often very different skillsets, like designing a racing car and actually racing it.
Again, it's not a given that a small team will have both those sets of skills readily at hand. Which of course, can stunt its growth, further compounding the problem.
- gus_massa 8y agoI don't mind that it has or not a sleek documentation or just plain html. I just want one or two snippets of code in the main page. I tried reading the docs (in the html version), and the first example is in the fourth or fifth page.
- YeGoblynQueenne 8y agoThere is a tutorial in pdf format, that pretty much starts with hello world: https://www.mercurylang.org/documentation/papers/book.pdf https://www.mercurylang.org/documentation/papers/book.pdf :- module hello. :- interface. :- import_module io. :- pred main(io::di, io::uo) is det. :- implementation. main(IOState_in, IOState_out) :- io.write_string("Hello, World!\n", IOState_in, IOState_out). Is the problem that this is pdf, rather than html?
- gus_massa 8y agoI usually try the html version first if available (and I asume that the pdf version is equal).