7

The problem: callback hell. Code would be indented by three hundred fucking spaces just to do some async work. Your code would end with thirty lines of closing curly brackets

Solution: async and await.

The problem, reborn: NoSQL. Code is indented by three hundred fucking spaces just to run a query. Your query ends with thirty lines of closing curly brackets.

Comments
  • 1
    The solution: SQL
    If you want to do complex operations on structured data, you want SQL. The only thing nosql excels in is scalability.
  • 1
    @Lor-inc Hehe, Excels.
  • 1
    @Lor-inc It's not even complex operations. Stuff that would be "SELECT <column> FROM <table> WHERE id=1" is ridiculously long
  • 0
    Ohh... I get it now, your saying the elastic searches.

    Yes pure json is a pain, even I don't quite get it. The first time I just created visualizations in kibana and then got the query from the async JS requests.

    Then switched to Java app do used the API which users Builder classes to construct the query...
Add Comment