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

Add a language comparison page #696

Open
sonnyp opened this issue Oct 21, 2023 · 5 comments
Open

Add a language comparison page #696

sonnyp opened this issue Oct 21, 2023 · 5 comments

Comments

@sonnyp
Copy link
Contributor

sonnyp commented Oct 21, 2023

Similar to the "Extensions" window, we should have a "Languages" window with a comparison table and links.

Similar to https://developer.gnome.org/documentation/introduction/languages.html but with a bit more focus on Workbench and developer experience

This will have 2 objectives

  1. Help newcomers decide which language to use in Workbench
  2. Encourage language maintainers to implement features

Here is an example

Formatter Linter Library demos Support Recommended for
JavaScript Yes Yes 100 100% Beginners
Vala No Yes 90 80% Intermediate
Rust Yes No 90 80% Intermediate
Python No No 0 50% Beginners

Support would refer to UX, APIs and features, for example

Note that these aren't Vala specific anymore.

@sonnyp
Copy link
Contributor Author

sonnyp commented Oct 21, 2023

Design wise we should have a little description for each language and an intro that says "Use what you are familiar with".

@sonnyp
Copy link
Contributor Author

sonnyp commented Oct 21, 2023

@bragefuglseth would you be interested in designing something like this?

@bragefuglseth
Copy link
Contributor

Yeah! I think this should be in the already existing Extensions window, though, below the list of installed extensions. Seems like this is the place where it would be most relevant.

@sonnyp
Copy link
Contributor Author

sonnyp commented Oct 21, 2023

If you can find a way to merge both dialogs that's not confusing - I'm happy to :)

Remembers the Extensions window is currently used for "user attempts to do something they don't have the sdk for".

For the Languages window I had in mind to make it accessible via an info button here

image

and from the Library window "About Languages" or something.

But yeah there is a lot of overlap.

@gregorni
Copy link
Contributor

I feel like there should also be links to the language API documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants