zuloonh.blogg.se

Rust language want to take into
Rust language want to take into





rust language want to take into
  1. #RUST LANGUAGE WANT TO TAKE INTO PATCH#
  2. #RUST LANGUAGE WANT TO TAKE INTO CODE#

But I do believe everyone that cares about Rust should begin to worry. I don't think we're anywhere near Scala-level problems (or drama) yet, and I don't think Rust is existentially threatened. I still don't know what was true and who, if anyone, was in the right. Some of the accusations were quite serious. It's been along time and I can't recap in detail, but basically leading community figures– who I had respected– were sniping and insulting and slandering each other both technically and personally. I was really not looking forward to learning a new language and rewriting all of my projects, especially since they were at points considering cutting some of the features I really liked. Features you might have been looking forward to– or even using with Scala 2- could be cut. Not only that, but the exact nature of the "new" language changed pretty significantly over the course of development.

rust language want to take into

Scala 3 was also essentially a rethink of the entire language. But it lost a lot of that momentum and excitement as competitors sprang, up, notably Kotlin. Scala gained a lot of its momentum and excitement primarily as a JVM language that could work with Java libraries, but that was not Java. I quit Scala largely because of the drama, but I don't think that was the only or even the main headwind Scala faced. We also see that with plain Java in the big data world. Databricks has been a huge drag on the ecosystem and isn't even targeting Scala 2.13 by default. Unfortunately even assuming good faith and unlimited resources, industry adoption also depends on industry players themselves.

rust language want to take into

Here I think the Scala Center should have tasked someone doing just that.

#RUST LANGUAGE WANT TO TAKE INTO CODE#

The main issue here is what happens with abandoned libraries: without macros, porting code that was written even 15 years ago is not insurmountable, with macros, now you need someone who understands old and new macros. Scala 2 macros were always experimental, new macros and metaprogramming features are better and saner.

#RUST LANGUAGE WANT TO TAKE INTO PATCH#

Scala 2 broke compatibility with every minor version, at the beginning even with patch versions! That is not the case anymore: Scala 3 can consume Scala 2.13 binaries and all the 3.x minor versions are backwards compatible. I'm the first to complain about Scala 3's initial release and questionable feature prioritization but the picture here is not entirely fair. I believe that as long as the Rust language stays great with all its awesome features that set it apart and us the community & companies believe in it and stay strong as we are now, it has a brighter future ahead. I guess, after giving some thought about this and going through some of the comments here, my optimism about the future of Rust stays high. I mean, I'm not familiar with Scala, but if the transition from 2 to 3 was one of the signifcant factors for its less industry-wide adoption, it does sound similar on surface to Python's transition from 2 to 3, but Python in general is huge everywhere even to this day. It's interesting to see how there could be quite a lot of variables about how something like this can lose some of its steam, but in this particular piece of the story for Scala, it sounds a bit more closer to a tech related problem than organizational/human/drama problem behind it, not that it might have not had any. We'll do our best to keep these links up to date, but if we fall behind please don't hesitate to shoot us a modmail. This is not an official Rust forum, and cannot fulfill feature requests. Err on the side of giving others the benefit of the doubt.Īvoid re-treading topics that have been long-settled or utterly exhausted. Please create a read-only mirror and link that instead.Ī programming language is rarely worth getting worked up over.īe charitable in intent. If criticizing a project on GitHub, you may not link directly to the project's issue tracker. Post titles should include useful context.įor Rust questions, use the stickied Q&A thread.Īrts-and-crafts posts are permitted on weekends.Ĭriticism is encouraged, though it must be constructive, useful and actionable. For content that does not, use a text post to explain its relevance.

rust language want to take into

Posts must reference Rust or relate to things using Rust. We observe the Rust Project Code of Conduct. Strive to treat others with respect, patience, kindness, and empathy. Please read The Rust Community Code of Conduct The Rust Programming LanguageĪ place for all things related to the Rust programming language-an open-source systems language that emphasizes performance, reliability, and productivity.







Rust language want to take into