You are right that it is part of business calculation, in the same way as every supermarket assumes that certain percentage of customers will steal something. But does it justify stealing?
Is it so difficult to understant? I offer you a content which was paid by advertiser. You pay by watching these adverts. If you block my adverts it is like you sneaked to the cinema without bying a ticket.
You do not like adverts on my site, ok fine, just do not read/watch my content. Or as another option, just pay me directly the same money I would get from adverts. It is a small amount anyway, and you and I will be happy
Really? You were happy without search engines, without google maps, without Microsoft or Apple download pages, without any social sites, without wiki?
Maybe you were, I was not.
Really? You were happy without search engines, without google maps, without Microsoft or Apple download pages, without any social sites, without wiki?
Maybe you were, I was not.
This article is about rendering HTML using template engine on the server. I believe this can be (and probably should) be done using existing server side engines, while javascript templates are to be used on the client.
Of course if someone is using node.js as a server, then my arguments are not valid, but choice of server is another huge subject to discuss.
I am sorry, maybe I am missing something important, but what is a logical difference between what you propose and concepts like ASP, PHP, ASP.NET?
I am using templates in all pages, but only because data is known only on a client, i.e. I get data from AJAX call and fill-in a template (jsrender, knockout, others)