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.

Sign up for GitHub

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

Jump to bottom

add section 2: methodology for approaching & evaluating solutions #23

Merged
merged 3 commits into from
Aug 9, 2024
Merged

add section 2: methodology for approaching & evaluating solutions #23

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
80a7802
+2 methodology for approaching & evaluating solutions
tantek Aug 6, 2024
4ce02de
simplifying edits from mt
tantek Aug 7, 2024
e04e688
100% reliable like a calculator
tantek Aug 8, 2024
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
simplifying edits from mt 
Incorporate simplifying suggested changes from mt

Co-authored-by: Martin Thomson <mt@lowentropy.net>
  • Loading branch information
@tantek @martinthomson
tantek and martinthomson authored Aug 7, 2024
commit 4ce02de94b47208cff3af9fb90babd005ad1cfa3
2 changes: 1 addition & 1 deletion amount.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,4 +11,4 @@ then browsers could offer a privacy-respecting user-interface to display these a

## Methodology for approaching & evaluating solutions

Per the priority of constituencies, we should look for solutions that users can trust (like if there is an affordance to convert units, it should be 100% reliable when present), and second, solutions that are more dependable and robust for developers. In particular, we should look for and prefer declarative approaches over imperative approaches per [the Mozilla Web Vision, e.g. for more “robust & predictable fallback behaviors”](https://www.mozilla.org/en-US/about/webvision/full/#thedeclarativeweb). Among such solutions, we should see if there have been past proposals, especially by web developers, and see if we can re-use any part of their ideas, semantics, or syntax.
Per the priority of constituencies, we should first look for solutions that users can trust (like if there is an affordance to convert units, it should be 100% reliable when present) and, second, solutions that are more dependable and robust for developers. In particular, we should look for and prefer [declarative approaches](https://www.mozilla.org/en-US/about/webvision/full/#thedeclarativeweb) over imperative approaches.