Depuración de JavaScript

En The 16 JavaScript debugging tips you probably didn’t know se explican 16 técnicas que ayudan a depurar el código JavaScript:

  1. debugger
  2. Display objects as a table
  3. Try all the sizes
  4. How to find your DOM elements quickly
  5. Benchmark loops using console.time() and console.timeEnd()
  6. Get the stack trace for a function
  7. Unminify code as an easy way to debug JavaScript
  8. Quick-find a function to debug
  9. Black box scripts that are NOT relevant
  10. Find the important things in complex debugging
  11. Watch specific function calls and arguments
  12. Quickly access elements in the console
  13. Postman is great (but Firefox is faster)
  14. Break on node change
  15. Use page speed services
  16. Breakpoints everywhere

El lenguaje que casi se convierte en CSS

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.