Add Sui & Update Move

[yanganto]

https://github.com/sui-foundation/awesome-sui

Move is a programming language for writing safe smart contracts originally developed at Facebook in 2019 as part of the Diem project, and it is active and keep maintained now. We update the link of awesome-move, because current one from MystenLabs will be deprecated, and Sui Foundation will take care about this in the future.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

• Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
• Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
• You have to review at least 2 other open pull requests.
  Add F# #3259 (review)
  Add Yazi #3232 (review)
• You have read and understood the instructions for creating a list.
• This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
  • ✅ Add Swift
  • ✅ Add Software Architecture
  • ❌ Update readme.md
  • ❌ Add Awesome Swift
  • ❌ Add swift
  • ❌ add Swift
  • ❌ Adding Swift
  • ❌ Added Swift
• Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
  • ✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
  • ✅ - [Framer](…) - Prototyping interactive UI designs.
  • ❌ - [iOS](…) - Resources and tools for iOS development.
  • ❌ - [Framer](…)
  • ❌ - [Framer](…) - prototyping interactive UI designs
• Your entry should be added at the bottom of the appropriate category.
• The title of your entry should be title-cased and the URL to your list should end in #readme.
  • Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.
• No blockchain-related lists.
• The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

• Has been around for at least 30 days.
  That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
• Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
• The default branch should be named main, not master.
• Includes a succinct description of the project/theme at the top of the readme. (Example)
  • ✅ Mobile operating system for Apple phones and tablets.
  • ✅ Prototyping interactive UI designs.
  • ❌ Resources and tools for iOS development.
  • ❌ Awesome Framer packages and tools.
• It's the result of hard work and the best I could possibly produce.
  If you have not put in considerable effort into your list, your pull request will be immediately closed.
• The repo name of your list should be in lowercase slug format: awesome-name-of-list.
  • ✅ awesome-swift
  • ✅ awesome-web-typography
  • ❌ awesome-Swift
  • ❌ AwesomeWebTypography
• The heading title of your list should be in title case format: # Awesome Name of List.
  • ✅ # Awesome Swift
  • ✅ # Awesome Web Typography
  • ❌ # awesome-swift
  • ❌ # AwesomeSwift
• Non-generated Markdown file in a GitHub repo.
• The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
• Not a duplicate. Please search for existing submissions.
• Only has awesome items. Awesome lists are curations of the best, not everything.
• Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
• Includes a project logo/illustration whenever possible.
  • Either centered, fullwidth, or placed at the top-right of the readme. (Example)
  • The image should link to the project website or any relevant website.
  • The image should be high-DPI. Set it to a maximum of half the width of the original image.
  • Don't include both a title saying Awesome X and a logo with Awesome X. You can put the header image in a # (Markdown header) or <h1>.
• Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
• Includes the Awesome badge.
  • Should be placed on the right side of the readme heading.
    • Can be placed centered if the list has a centered graphics header.
  • Should link back to this list.
• Has a Table of Contents section.
  • Should be named Contents, not Table of Contents.
  • Should be the first section in the list.
  • Should only have one level of nested lists, preferably none.
  • Must not feature Contributing or Footnotes sections.
• Has an appropriate license.
  • We strongly recommend the CC0 license, but any Creative Commons license will work.
    • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).
  • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
  • Place a file named license or LICENSE in the repo root with the license text.
  • Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
  • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
• Has contribution guidelines.
  • The file should be named contributing.md. The casing is up to you.
  • It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
  • The section should not appear in the Table of Contents.
• All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
• Has consistent formatting and proper spelling/grammar.
  • The link and description are separated by a dash.
    Example: - [AVA](…) - JavaScript test runner.
  • The description starts with an uppercase character and ends with a period.
  • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
• Does not use hard-wrapping.
• Does not include a CI (e.g. GitHub Actions) badge.
  You can still use a CI for linting, but the badge has no value in the readme.
• Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

[sindresorhus]

It's weird to click a link called "Move" and end up on a list called "Sui". The relation to "Move" needs to be made clearer in the list.

[yanganto]

Yeh, Move is a generic language, and the library(package) is platform specific. I specify the term Move on Sui, because the libraries we care are in Sui ecosystem. I hope this is clear enough for current situation.

[yanganto]

Hi @Cremetruck Thanks for review.

[thisisisa]

Not a requirement, but I suggest linkifying Sui in the readme to point to the official website and updating the repo description to focus on Sui instead of Move. Looks great otherwise. Good job!

[lutzh]

I suggest to change the title of the PR to follow the standard
"Add [topic]", i.e. "Add Sui".

This pull request has a title in the format Add Name of List.

[lutzh]

Sorry, I wasn't attentive enough in my first review where I suggested to change the name. I only now realize your PR contains two unrelated changes. So I suggest to split it up into two:

1. Add Sui
2. Update Move (or "change link for move"

In the second, you should explain why the new link is better / more relevant than the old.

[yanganto]

In the second, you should explain why the new link is better / more relevant than the old.

"current one from MystenLabs will be deprecated, and Sui Foundation will take care about this in the future." This is already in the top section of PR description.

We work really closely, and the foundation take over and keep maintaining ecosystem facing tasks, so there is less distracting things for MystenLabs.

Also, just wonder if we can do thing in one PR clearly and efficiently why we do two. Because move is become one section, and it needs library and platform. I believe one PR is good here.

If you think we need extra 2 pr reviews for this PR, I am happy to do so, but split PR will easy to make thing in a mess and wast community energy. I hope you can kindly understand.

[yanganto]

@sindresorhus Does this PR good to merge?

[sindresorhus]

The repo description is still incorrect.

---

⚠️ This warning icon means that the tool may not be functioning correctly at the moment. Please check these tools carefully.

Non-working tools should not be included.

---

Linkify Sui in Sui is the first blockchain built for internet scale, enabling fast, scalable, and low-latency transactions. to its project website.

[yanganto]

Hi @sindresorhus Thanks for review 🙏, and kindly point out the issue why we can not move forward. Unfortunately, I am not working at Sui Foundation now, and have no position to take care about awesome-sui, people still in foundation may take care the awesome list in the future.

CC. @wriches