Building Server-Side Web Language Processors

Building Server-Side Web Language Processors

OK … I can undestand why but honestly i do not like web development. That is fun because I prefer using web applications than real apps stored in my hard drive. (why every service needs an app? It has no sense).

But it has sense, nowdays is required for all the entrprices to have a web page and some of the requirements for (lots of) jobs  are web experience or web development skills. One of my partners is a little bit obsessed about web design and development, I am sure hi will be In total agreement with the article.

However, even if the purpose is the same (compilers here, compilers there) in web the expecting result is an HTML page but (opposite of my sister thought, she is not well informed about, not her fault) it is not most easy than grite a local version of the same language processor. It is necesary to transform the input to one with delimitator used to pull apart the static code used for the output and the code that will be calculated and finally  to something usable for the browser.

I like the idea of having specific conventios for variables. But honestly i think it could not be the best idea, even if you write abot if another developer needs to check the performance of the compiler/ interpreter it is posible to have nonsense or to be complicated to adapt.

I did not have idea of how to use customized tags for specif language web implementation, but it sound like an usefull tool. Now (I think I undesrtand a little more how it works), It requires a Tag Library Descriptor file, a XML file, which needs to contain information of the library and the tags it contains.

I have a confuse opinion of the article, I half agree about the interest to meke something in a web version because “instead of a processor that just runs on a command-line shell.”it is more interesting fore most of students but if it was the case for me it will be like hell. (my fault, not the proyect´s but… )