Re: [rust-dev] Rust discourse visibility [Was: Tail call compatibility]
Seconding the arguments of others arguing *for* a mailing list. On 29.12.2014 22:02, Kevin Cantu wrote: It had gotten pretty clear that having a catch-all mailing list wasn't going to scale. Python also uses mailing lists as the primary communication medium. The main three lists are: python-dev (for developers, discussing the advance of the language), python-ideas (for anyone, suggesting and discussing ideas which the devs might take into account) and python-list (for anyone, discussing about any python-specific issue). Of these, only python-list is *very* high traffic with very diverse topics. python-ideas is also high traffic but only with a few topics going on at a given time. This makes it easy to mentally filter and follow what happens. Same goes for python-dev, but it generally has less traffic than python-ideas. For several topics there exist sublists (e.g. the C++ special interest group), which are generally very low to medium traffic. I cannot see why rust would not be able to follow this approach, too, but instead suggesting people to use $website [1]. *That* is not going to scale, for the individuals. It is trivial to track several projects using a well-configured mailbox or mail client, but polling N websites every M minutes (for varying values of M) is quite cumbersome. I say that having tested the discourse mail interface for a few days now. I find it much harder to read than a well-behaved mailing list. It is basically 100% top-posting without threading. Very uncomfortable to read and follow. But who am I to complain. I am merely interested in a new upcoming language and have not much to contribute. regards, jwi [1]: Not to mention that that website requires unauthentictaed JavaScript from third party servers for log in. ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
Re: [rust-dev] robots.txt prevents Archive.org from storing old documentation
On 10.07.2014 16:56, Daniel Micay wrote: On 10/07/14 03:46 AM, Gioele Barabucci wrote: Hi, the current robots.txt on docs.rust-lang.org prevents Archive.org from storing copies of the old documentation. I think having the old documentation archived would be a good thing. BTW, all the documentation before 0.10 seems gone and this is a shame. Could you please allow the Archive.org bot to index the site? For the records: $ curl http://doc.rust-lang.org/robots.txt User-agent: * Disallow: /0.3/ Disallow: /0.4/ Disallow: /0.5/ Disallow: /0.6/ Disallow: /0.7/ Disallow: /0.8/ Disallow: /0.9/ Disallow: /0.10/ The old documentation is all available from the Git repository. The robots.txt rule is there to reverse the trend of searches being filled with out of date documentation. While this is a good thing /all/ software projects should be doing imo, one could still explicitly allow Archive.org by prepending: User-agent: ia_archiver Disallow: ? ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev signature.asc Description: OpenPGP digital signature ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
Re: [rust-dev] Text Mode File Reading/Writing
On 24.06.2014 06:36, Gil Cottle wrote: If not, adding a flag would be useful for text file-writing/reading when running on Windows, but it could also be a source of issues for people trying to write binary/text data depending on the defaults. Any thoughts on this? For what its worth, I think the python way is the most clean way, with respect to interoperability and platform independence. This is described in a quite convoluted way in the [documentation for the open builtin][0]. They basically implement text mode themselves and don’t let the OS know about it. On the OS side, they open all files in binary mode. In their text mode implementation, they convert all newlines to '\n' while reading and all '\n's to the platform newline while writing. [0]: https://docs.python.org/3/library/functions.html#open p.s. Don’t let your self get distracted from the “deprecated” in the mode table; this only refers to the mode string, not to the usage of universal newlines using the `newline` keyword argument, described a bit below the mode table. Thanks, Gil Cottle ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
