GeezerVison is showing github.com — Sort all front-end clients list to remain client framework agnostic by FossPrime · Pull Request #3128 · feathersjs/feathers
Conversation
FossPrime
commented
Mar 25, 2023
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
Minor, I know. But hear me out.
We are implying that we support or prefer angular over Vue in some way by not having an alphabetical list, or one that's not even sorted by github stars... Vue has 203k + 36k stars, over angular's 87k, which is technically lower than Node.js, but that's not a front-end framework (Unless you count webcontainers).
We can cutout Lit, Svelte and Astro as they did not exist when Feathers was released, and having 4 would violate the literary convention known as "rule of three's".
This PR also adds Angular and Vue where it's missing from a list mentioning other compatible Feathers clients.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
I would love to mention Vanilla TS, Vite, Node.js, Deno and Bun... but that would be repetitive and overly wordy.
eg: https://vite.new/vanilla-ts
FossPrime
changed the title
Sort front end clients list by popularity
Sort front end clients list by popularity or alphabetically
Mar 25, 2023
FossPrime
changed the title
Sort front end clients list by popularity or alphabetically
Sort front end clients list to remain client framework agnostic
Mar 25, 2023
FossPrime
changed the title
Sort front end clients list to remain client framework agnostic
Sort all front-end clients list to remain client framework agnostic
Mar 25, 2023
|
Why use / instead of , though?
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Why use / instead of , though?
These two have similar meaning:
- For Angular/React/Vue clients.
- For Angular, React, Vue or other clients.
The less traditional grammar encourages that the enumeration be more loosely interpreted, than a binding comma separated list. By no means do we discourage TS clients exports use with Svelte, Nuxt, Observers and Vite clients… but we have to draw the line somewhere. And, TS supporting frontend clients is needlessly generic and take too long to process when reading.
The biggest benefit is probably how easy it is to go back and change it. It's more semantic and easier to spot and remember than a plain English comma separated sentence that could easily get misremembered. As long as we're consistent, that's all that matters.
I'm also open to using the Web Component frameworks terminology, bit again, it makes the docs much harder to read. Kind of like renaming JavaScript to ECMAScript, or calling Linux, GNU/Linux, which means GNU plus Linux.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Why use / instead of , though?
These two have similar meaning:
- For Angular/React/Vue clients.
- For Angular, React, Vue or other clients.
The less traditional grammar encourages that the enumeration be more loosely interpreted, than a binding comma separated list. By no means do we discourage TS clients exports use with Svelte, Nuxt, Observers and Vite clients… but we have to draw the line somewhere. And, TS supporting frontend clients is needlessly generic and take too long to process when reading.
The biggest benefit is probably how easy it is to go back and change it. It's more semantic and easier to spot and remember than a plain English comma separated sentence that could easily get misremembered. As long as we're consistent, that's all that matters.
I'm also open to using the Web Component frameworks terminology, bit again, it makes the docs much harder to read. Kind of like renaming JavaScript to ECMAScript, or calling Linux, GNU/Linux, which means GNU plus Linux.
Thanks for the explanation. It makes sense, and I agree with you.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
This branch has not been deployed
No deployments
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|