Skip to content

Instantly share code, notes, and snippets.

@captainbrosset

captainbrosset/frustrations.md

Created January 4, 2023 10:30
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save captainbrosset/01a5306525ed377e619a85515eb6c667 to your computer and use it in GitHub Desktop.
Save captainbrosset/01a5306525ed377e619a85515eb6c667 to your computer and use it in GitHub Desktop.
Download ZIP
List of frustrations when working with the web
Raw
frustrations.md
  • Having to support specific browsers.
  • Avoiding or removing a feature that doesn’t work across browsers.
  • Making a design look/work the same across browsers.
  • Achieving visual precision on stylized elements (e.g., buttons).
  • Lack of capabilities to implement specific use cases.
  • Making web sites/applications accessible.
  • Making web sites/applications performant.
  • Making web sites/applications secure.
  • Using web technologies in a native or hybrid context (e.g, using WebViews, Electron, CEF).
  • Working with different tracking protection and data storage policies in browsers.
  • Outdated documentation for HTML, CSS and JavaScript.
  • Knowing what browsers support a specific technology.
  • Keeping up with changes to the web platform.
  • Testing across browsers.
  • Running automated tests.
  • Pinpointing existing performance issues.
  • Determining the root cause of a bug.
  • Keeping up with a large number of new and existing tools or frameworks.
  • Outdated or inaccurate documentation for frameworks and libraries.
  • Supporting multiple frameworks in the same code base.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment