āBecause of ownership, we run into a wall where the design patterns of the majority language are largely unintelligible.ā
I thought to myself, āI donāt say these things anymore.
- If your future prediction tells you that there is a wall in the direction that other person A is going, whether or not you will tell it to other person A.
- Now I am.
- Might: A word to suggest a possibility
- Might be: keep a record of what you suggest.
- Do not: try to persuade if the other party is not convinced of the possibility
- After all, predicting the future is subjective and difficult to persuade
- Thereās no point in trying to persuade them, especially if theyāre not stakeholders. - Donāt persuade people you donāt need to persuade.
- Mr. A can go ahead and hit the wall.
- Maybe they wonāt bump into each other.
- Before Mr. A reaches the wall, people who hit the wall earlier than Mr. A might punch a hole in the wall.
- And in that case, for Mr. A, itās no different than if there were no wall.
- Rustās concept of ownership makes design patterns in Java and other languages infeasible or unhelpful
- I think this future prediction is almost certain.
- When Java became popular, people who came from C, etc. and could not adapt to the new concepts and used only static methods came out and were called static uncle and ridiculed.
- [static uncle https://xtech.nikkei.com/it/atcl/watcher/14/334361/122100450/#:~:text=while %E3%80%81static method calls the instance,uncle%E3%80%8D E3%80%82]
- I suspect this history will repeat itself.
I donāt get itā¦ Why do some people think Rust will catch on when Scala didnāt?
tanakahisateru I hate it when people think this is a trivial discussion about which language is better. Iām afraid that people who have a good impression of Rust are probably just āairheadsā who have only done Hello World, considering the dilemma of the industry that was always worried about Nulpo and wished there was no such a complicated language.
tanakahisateru If we actually adopt a language that is currently working in another language at the whim of a superior who has no idea what he is doing and says, āI hear it has a good reputation, so letās adopt it,ā I think we will run into a wall that will allow us to migrate as is. I think that if we do this, we will run into a wall where the design patterns of the majority language will not be understood due to ownership rights. Well, itās a statement that makes it even more combustible, isnāt it?
tanakahisateru My point is that Scala is pretty much a continuation of Java, and if you really start trying to use Rust in a big way, youāre going to get a lot more allergic reactions from a lot of people. Iām focusing on the fact that Java and Scala are pretty close, and Iām sure many people will have a more severe allergic reaction if they really start trying to use Rust in a radical way, because of all the language features related to problems that will inevitably come up in an incremental way like in Scala.
tanakahisateru var and mutable and writing exceptions would result in a compile error Scala, and then around variables and quadrature operations. I wonder what would have happened if I had been forced to branch fundamentally and put everything on a reactive framework.
This page is auto-translated from /nishio/å£ć«ć¶ć¤ććäŗčØ using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. Iām very happy to spread my thought to non-Japanese readers.