Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create why-move.md #776

Merged
merged 7 commits into from
Mar 17, 2022
Merged

Create why-move.md #776

merged 7 commits into from
Mar 17, 2022

Conversation

Clay-Mysten
Copy link
Contributor

No description provided.

lxfind
lxfind previously requested changes Mar 11, 2022
doc/src/learn/why-move.md Outdated Show resolved Hide resolved
@Clay-Mysten Clay-Mysten requested a review from lxfind March 11, 2022 21:57
doc/src/learn/why-move.md Outdated Show resolved Hide resolved
@gdanezis gdanezis added the Type: Documentation Improvements or additions to documentation label Mar 12, 2022
@damirka
Copy link
Contributor

damirka commented Mar 14, 2022

Stashing thoughts.

  1. Both are blockchain languages, both were created for blockchains.

  2. Languages are absolutely different in their core: Move focuses on safe operations with digital assets and was built for and around them; Solidity is more of a general purpose language put into a blockchain. (elaborate)

  3. Move composability is one of the main features of the language - everything can be wrapped into anything with ease, allowing to build assets on top of other assets, being wrapped into other etc.

@damirka
Copy link
Contributor

damirka commented Mar 14, 2022

Re complexity I wouldn't go this route. Move is not that easy to get and master; if someone is coming with a programming background, Solidity would be an easier adoption.

@Clay-Mysten
Copy link
Contributor Author

Damir, care to make this content accurate directly? If not, I will try to get to it later today but am scrambling with many tasks.

@damirka
Copy link
Contributor

damirka commented Mar 16, 2022

@Clay-Mysten I've started writing the doc and will continue soon. Please review and tell me if it matches your expectations and correct me if you want to see it written differently.

Oh and I just pushed to this branch. 🤭

damirka and others added 2 commits March 16, 2022 16:21
Make small changes to latest text
@Clay-Mysten Clay-Mysten requested a review from lxfind March 16, 2022 15:54
doc/src/learn/why-move.md Outdated Show resolved Hide resolved
doc/src/learn/why-move.md Show resolved Hide resolved
doc/src/learn/why-move.md Outdated Show resolved Hide resolved
damirka and others added 2 commits March 17, 2022 01:37
Co-authored-by: Sam Blackshear <sam.blackshear@gmail.com>
Co-authored-by: Sam Blackshear <sam.blackshear@gmail.com>
Copy link
Contributor Author

@Clay-Mysten Clay-Mysten left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Xun, can you remove the request for changes?

@Clay-Mysten Clay-Mysten dismissed lxfind’s stale review March 17, 2022 00:39

Changes have been mande

@Clay-Mysten Clay-Mysten merged commit 0b191d1 into main Mar 17, 2022
@Clay-Mysten Clay-Mysten deleted the Clay-Mysten-patch-10 branch March 17, 2022 00:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants