26 ms·

For systems programming languages, safe by default with scoped unsafe code is a Pareto improvement on unsafe everywhere.

by User23 8y ago

pjmlp 8y ago
A feature that exists since 1961, across several systems languages.
- kiriakasis 8y ago
  I never understood this type of comments, is what you are trying to say something like: "It was already tried and failed, why is this time better" "Mainstream languages always end up not using it" "People should reference more the original works of the past" ... One of the many explainations of the name Rust is that it represents a collection of old ideas. What was the point you were trying to convey in specific?
  - pjmlp 8y ago
    People should reference more the original works of the past instead of rediscovering them
    - kaens 8y ago
      I think more rediscoveries may be references than you suspect, but in the cases that are rediscoveries there is a bit of a knowledge and discoverability issue for PL features for people who aren't PL nerds already. I'd love it if more people had a more solid understanding of the ideaspaces that have been covered in the PL landscape, but considering that most common paths to working in software (and even to creating and contributing to langs) don't involve needing to know PL history I'm not sure how to get there from here. If you have resources you think people should be utilizing here, please speak up.
      - pjmlp 8y ago
        I keep posting them here. How I got to learn about them? Having a solid Informatics Engineering degree, with focus on systems programming, graphics and compilers, and a very nice university library. That was it, we had to hunt for books, compuserve, gopher and BBS were still a thing. Nowadays learning about the history of PL is a google/bing/... search away, a couple of seconds with access to plenty of scanned papers and conference proceddings since the early 60's, so one has to be quite lazy not to research them.

For systems programming languages, safe by default with scoped unsafe code is a Pareto improvement on unsafe everywhere.

by User23 8y ago

For systems programming languages, safe by default with scoped unsafe code is a Pareto improvement on unsafe everywhere.

pjmlp 8y ago

A feature that exists since 1961, across several systems languages.

kiriakasis 8y ago
I never understood this type of comments, is what you are trying to say something like: "It was already tried and failed, why is this time better" "Mainstream languages always end up not using it" "People should reference more the original works of the past" ... One of the many explainations of the name Rust is that it represents a collection of old ideas. What was the point you were trying to convey in specific?
- pjmlp 8y ago
  People should reference more the original works of the past instead of rediscovering them
  - kaens 8y ago
    I think more rediscoveries may be references than you suspect, but in the cases that are rediscoveries there is a bit of a knowledge and discoverability issue for PL features for people who aren't PL nerds already. I'd love it if more people had a more solid understanding of the ideaspaces that have been covered in the PL landscape, but considering that most common paths to working in software (and even to creating and contributing to langs) don't involve needing to know PL history I'm not sure how to get there from here. If you have resources you think people should be utilizing here, please speak up.
    - pjmlp 8y ago
      I keep posting them here. How I got to learn about them? Having a solid Informatics Engineering degree, with focus on systems programming, graphics and compilers, and a very nice university library. That was it, we had to hunt for books, compuserve, gopher and BBS were still a thing. Nowadays learning about the history of PL is a google/bing/... search away, a couple of seconds with access to plenty of scanned papers and conference proceddings since the early 60's, so one has to be quite lazy not to research them.