3 ms·
Language maturity is not a one-dimensional problem and it's also not equal to the age of the language. To name just two ways in which I consider Rust more matu
by tazjin 9y ago
Language maturity is not a one-dimensional problem and it's also not equal to the age of the language.
To name just two ways in which I consider Rust more mature than Java:
* It has a lot of fundamentals that are based on more academic languages which have explored some specific PLT space for a long time and let it mature. The fruits of that are now in Rust (many aspects of its type system for example).
* Rust's community has an almost absurd ability (contrasted with most other languages) to focus on specific core libraries and tooling. For example serde[1], the Rust serialization library, is well-understood, simple, mature and supported in basically every Rust library out there.
The second point is extremely impressive when contrasted with the state of things in Java-land, where you often have many different solutions for the same problems. Sometimes even the well-known and used ones are of very questionable quality[2].
[1]: https://serde.rs/ https://serde.rs/
[2]: https://github.com/FasterXML/jackson-databind/pull/1423 https://github.com/FasterXML/jackson-databind/pull/1423
- blub 9y agoThe type system has no relationship to language maturity. It's just a different type system with different trade-offs. Your second point is invalidated by the blog itself: "Many libraries are still early".
- dkarl 9y agoJackson's status as the de facto Java standard for reading and writing JSON really reflects poorly on the Java community. Too often the biggest, hairiest solutions get anointed as the safe "best practices" choice for all new development when really they should only be used if you know specific reasons why they will pull their weight relative to simpler solutions. Jackson is an 800lb gorilla with an impressive arsenal of features, but there's no way in hell it should be the default choice for a simple greenfield CRUD application.
- abalone 9y agoWithout turning this into a long tangent subthread.. could you point to some support for this? The comparisons I've seen are more nuanced.[1] [1] https://blog.takipi.com/the-ultimate-json-library-json-simple-vs-gson-vs-jackson-vs-json/ https://blog.takipi.com/the-ultimate-json-library-json-simpl...
- dkarl 9y agoThat's a performance comparison that ignores all other aspects such as simplicity, readability, and ease of maintenance. It also shows Jackson coming in last for parsing small files.