3 ms·
I can't find any empirical evidence that adding features in the next version dooms the language. The opposite is true. All successful languages started small.
by lukasm 12y ago
I can't find any empirical evidence that adding features in the next version dooms the language. The opposite is true. All successful languages started small.
- codygman 12y agoPython is being hurt by Python 3.0 changing so much.
- lukasm 12y agoBy breaking backward compatibility. Not forward.
- keeperofdakeys 12y agoThe changes that are currently being done in Rust for 1.0 are those kinds of breaking changes. Many things that are being changed have been in a state of semi-decay from old experiments, and old features of the language. As an example, the IO subsystem had lots of generality designed for when lightweight tasks were still a feature. By ripping them out, the library is both easier to use, and simpler for future expansion. It was also changed to support the general error-handling facilities that Rust now has (which are partly similar to the old IO-specific error handling features, but wouldn't work well with other libraries). Others like the collection-api cleanup were badly needed, because of inconsistency and a lack of direction over time. Now the collection-api is much cleaner, and consistent between different types of collections. This allows them to add things like collection-api traits in the future, and newer collections that can follow the same api conventions