4 ms·

This is the one thing that makes me worried about the long term health of Rust. There seems to be so much drama, relative to the other languages. For some rea

This is the one thing that makes me worried about the long term health of Rust. There seems to be so much drama, relative to the other languages. For some reason, you don’t hear about this much drama from languages that have far larger user bases.

jowea 3y ago
But are most larger languages community driven like Rust is? Python and?
insanitybit 3y ago
Most languages don't go from having a major, centralized corporate sponsor, to having everyone from that sponsor let go over night. I think that has led to a lot of these problems, or at least seriously exacerbated them. Mozilla really fucked things up here.
Animats 3y ago
Nah. Look up the drama with Larry Wall and Perl 6. Von Rossum and the Python 3 mess. It goes back a long way. Wirth was against getting past Standard Pascal, which had no error handling or separate compilation. There was a huge feud between the Interlisp LISP people and the Symbolics LISP people, both of whom had way overdesigned the language, in incompatible ways. Scheme was a reaction to that.
- lispm 3y ago
  Wow, the Scheme people had also invented time travel when they invented Scheme in 1975. They anticipated the Symbolics people "overdesiging" the LISP language when they started the company in 1980. Then the Scheme people started to overdesign their language in reaction to the LISP people, since Scheme lacked even simple things like error handling. See https://srfi.schemers.org https://srfi.schemers.org , https://www.r6rs.org https://www.r6rs.org , https://racket-lang.org https://racket-lang.org
  - Animats 3y ago
    Yes, I had the early history of LISP wrong. There were at least three major LISP factions in the 1980s, as LISP use expanded outside of the tiny AI community of the 1970s. Much controversy. All over now-dead issues.
barkingcat 3y ago
I bet the early C and C++ iso committee meetings were just as bad if not worse. Worse cause it would be corporate entities having tamper tantrums about which pet language feature should get implemented.

jowea 3y ago

But are most larger languages community driven like Rust is? Python and?

insanitybit 3y ago

Most languages don't go from having a major, centralized corporate sponsor, to having everyone from that sponsor let go over night. I think that has led to a lot of these problems, or at least seriously exacerbated them. Mozilla really fucked things up here.

Animats 3y ago

Nah. Look up the drama with Larry Wall and Perl 6. Von Rossum and the Python 3 mess. It goes back a long way. Wirth was against getting past Standard Pascal, which had no error handling or separate compilation. There was a huge feud between the Interlisp LISP people and the Symbolics LISP people, both of whom had way overdesigned the language, in incompatible ways. Scheme was a reaction to that.

lispm 3y ago
Wow, the Scheme people had also invented time travel when they invented Scheme in 1975. They anticipated the Symbolics people "overdesiging" the LISP language when they started the company in 1980. Then the Scheme people started to overdesign their language in reaction to the LISP people, since Scheme lacked even simple things like error handling. See https://srfi.schemers.org https://srfi.schemers.org , https://www.r6rs.org https://www.r6rs.org , https://racket-lang.org https://racket-lang.org
- Animats 3y ago
  Yes, I had the early history of LISP wrong. There were at least three major LISP factions in the 1980s, as LISP use expanded outside of the tiny AI community of the 1970s. Much controversy. All over now-dead issues.

barkingcat 3y ago

I bet the early C and C++ iso committee meetings were just as bad if not worse. Worse cause it would be corporate entities having tamper tantrums about which pet language feature should get implemented.