HN user

GroSacASacs

29 karma
Posts4
Comments58
View on HN

incorrect

     try {
        throw new Error("catch me !"); // force try to fail
      } catch (catchedError) {
        console.log("inside catch");
        // throw new Error("hmm");
      } finally {
        // always executed         
        console.log("inside finally");
      }
      // always executed
      console.log("after try catch finally");


the finally statement can be useful when another error is thrown inside the catch block, in which case you have more serious problems in your code

Because reasons ... First every CRUD app has specific differences in: the UI, authorization system, rules,

It is not taught enough in classic computer science classes (what I did) to reuse existing patterns/RAD/frameworks

Also it is to an extend automated: ui libraries, widgets, SQL/NOSQL, admin interfaces etc are existing and could be viewed, as automation.

How does this compete with putting a big script tag at the end of the body in the HTML that contains all the code necessary ? What settings can make this way of requiring scripts useful ?

I guess this can be useful, to load extra functionality at run time, in very big single page application.

Compressed version

We say that history is written by the winners. That is sometimes true. We have no Carthaginian accounts of their war with Rome; few historians today have much sympathy for Hitler. But the thread that seems to connect many of the great histories of the pre-modern world is that they were written by the losers.