- Display objects as a table
- Try all the sizes
- How to find your DOM elements quickly
- Benchmark loops using console.time() and console.timeEnd()
- Get the stack trace for a function
- Quick-find a function to debug
- Black box scripts that are NOT relevant
- Find the important things in complex debugging
- Watch specific function calls and arguments
- Quickly access elements in the console
- Postman is great (but Firefox is faster)
- Break on node change
- Use page speed services
- Breakpoints everywhere
Muy interesante el artículo The Languages Which Almost Became CSS que dice:
When HTML was announced by Tim Berners-Lee in 1991 there was no method of styling pages. How given HTML tags were rendered was determined by the browser, often with significant input from the user’s preferences. It seemed, however, like a good idea to create a standard way for pages to ‘suggest’ how they might prefer to be rendered stylistically.
But CSS wouldn’t be introduced for five years, and wouldn’t be fully implemented for ten. This was a period of intense work and innovation which resulted in more than a few competing styling methods which just as easily could have become the standard.
While these languages are obviously not in common use today, I find it fascinating to think about the world that might have been. Even more surprisingly, it happens that many of these other options include features which developers would love to see appear in CSS even today.
En United States Space Force se puede ver un buen ejemplo de sitemap visual: