Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bikeshed "The Advanced Rust Programming Language" as a name #27412

Closed
Gankra opened this issue Jul 30, 2015 · 7 comments
Closed

Bikeshed "The Advanced Rust Programming Language" as a name #27412

Gankra opened this issue Jul 30, 2015 · 7 comments

Comments

@Gankra
Copy link
Contributor

Gankra commented Jul 30, 2015

@dherman suggested this iirc -- but I can't remember.

@brson is concerned that it is too similar

Originally it was called The Unsafe Rust Programming Language since it largely focuses on unsafe code and the stuff that matters to it.

@brson
Copy link
Contributor

brson commented Jul 31, 2015

Here are my problems with the current arrangement:

  • A second book, and one that claims to be 'advanced', diminishes both the significance of 'The Book' and its brand. It will never have the stature of 'The C Programming Language' if it has a more 'advanced' big brother looming over it.
  • Multiple separate books is a path to balkanization of the docs, where Steve gets his docs, Gankro gets his docs, I get my docs and nobody's working together.
  • Practically, if we now publish The Book, we have to exclude a big chunk of information that people would probably want included.
  • The name is misleading. 'Advanced' has many connotations. This isn't advanced concurrency, or advanced architectural design - it's advanced unsafe.

@steveklabnik
Copy link
Member

@brson and I are basically on the same page when it comes to "Advanced," I had the exact same thoughts.

@Gankra
Copy link
Contributor Author

Gankra commented Jul 31, 2015

Discussing at lunch the top contender became "The Rustinomicon" in reference to the fact that this is dark magic that mere mortals dare not tamper with.

@ghost
Copy link

ghost commented Jul 31, 2015

@gankro does it need to be separate from TRPLB? Essentially echoing what @brson said, anyone who wants to understand rust to a decent standard will probably want to know this stuff.

@Gankra
Copy link
Contributor Author

Gankra commented Jul 31, 2015

@Toby-s the important thing about this text, and indeed Rust itself, is that you don't need to know it. This is a book for all the horrible details unsafe code entails. I believe it would be a mistake to include it with THE book, which is Everything You Need To Know.

@pnkfelix
Copy link
Member

(I thought was going to be spelled "Rustonomicon", since we're implicitly making references to "Necronomicon" and "Cryptonomicon".)

@pnkfelix
Copy link
Member

(oh, oh: Gankra@7570be8 )

bors added a commit that referenced this issue Aug 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants