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

Principle against tying APIs too closely to hardware #308

Closed
LeaVerou opened this issue Apr 19, 2021 · 2 comments
Closed

Principle against tying APIs too closely to hardware #308

LeaVerou opened this issue Apr 19, 2021 · 2 comments
Assignees

Comments

@LeaVerou
Copy link
Member

This was brought up in our breakout today while reviewing Compute Pressure

@hober had some interesting examples from past reviews, could you share them here please?

@cynthia cynthia self-assigned this May 13, 2021
@cynthia cynthia added Status: Consensus to write We have TAG consensus about the principle but someone needs to write it (see "To Write" project) WRITEMEASAP labels May 13, 2021
@cynthia
Copy link
Member

cynthia commented May 13, 2021

I think this is related to #39 so I'll see if I can write a PR that deals with both of these issues.

@cynthia
Copy link
Member

cynthia commented Dec 8, 2021

I think this should be covered here, let me know if you there is something that we missed.
https://w3ctag.github.io/design-principles/#usecase-oriented-apis

@torgo torgo removed the WRITEMEASAP label Jan 5, 2022
@cynthia cynthia removed the Status: Consensus to write We have TAG consensus about the principle but someone needs to write it (see "To Write" project) label Mar 24, 2022
@cynthia cynthia closed this as completed Mar 24, 2022
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