3 ms·
The author prioritised benchmarks and "creativity" in code rather than making sure the library was safe. That's fine, it was their code after all. However, man
by M2Ys4U 7y ago
The author prioritised benchmarks and "creativity" in code rather than making sure the library was safe. That's fine, it was their code after all.
However, many people saw that this was a caviller attitude to take, especially as it wasn't signposted, and gave the author grief for this.
The problem was, though, that the cumulative effect of these "unsafe is bad, therefore you are bad" comments (which shouldn't have been made) was that the author was dismissive towards reports of actual unsafe behaviour in their library which could have caused security issues.
The author got frustrated and moved the repos to his own personal account and left a patronising message in its place.
Bare in mind that Atix had been built up as one of (if not the) best Rust libraries for HTTP servers, partly off the back of the benchmarks (for which safety had been sacrificed) and partly from the fact it ran on stable (non-nightly) Rust.
- ay 7y agoI tried to make sense of it and it didn’t seem to be that much more convenient compared to running iron + appropriate middleware packages (session storage; multipart; etc). They seem a bit “stale” but work absolutely fine. Source: 33KLOC stable rust web project.
- iudqnolq 7y agoWhere is rust being used for 33kLOC projects?
- steveklabnik 7y ago33kloc is pretty small; rustc is over a million lines of code, for example.