In this entry, I'll give my thoughts on the paper Building Server-Side Web Language Processors, by Ariel Ortiz, going for the repeat in the blog lecture material.
In the abstract, I couldn't help but wonder why web development and language processing should go together. Maybe it's for some special reason I'm not aware of. Turns out, it's more akin to advice given from one professor to a broader community of CS educators. Sadly, many of us will end up coding websites and focusing on web development. Another, more uplifting reason to this language processing approach is the combination of courses. I really like this notion, as I too felt that my web course (Web I to be specific) felt a bit like a missed opportunity when, in another course, I was working on web security and SSL. I felt like both could have been combined into a larger, much more fun project.
The proposal to integrate language design into web development is something that I'd be compelled to explore in a classroom setting, and these suggestions are quite interesting. Personally, I would enjoy programming my own web server in order to implement the language processor. Although I can't say I enjoy using Python, the proposal to use sockets and the SimpleHTTPServer API is something I would see myself doing.
A really interesting part in this paper is to see the results different implementations of this concept in multiple CS courses. Building a MVC web framework is something that would have a lot more potential, in my opinion, than making an app in a language that got discontinued one semester after we took the course, welp. As the testimony said, making an application that can be used to make applications is one of those things that personally sparks a lot of creativity.
http://34.212.143.74/publicaciones/weblang.pdf
In the abstract, I couldn't help but wonder why web development and language processing should go together. Maybe it's for some special reason I'm not aware of. Turns out, it's more akin to advice given from one professor to a broader community of CS educators. Sadly, many of us will end up coding websites and focusing on web development. Another, more uplifting reason to this language processing approach is the combination of courses. I really like this notion, as I too felt that my web course (Web I to be specific) felt a bit like a missed opportunity when, in another course, I was working on web security and SSL. I felt like both could have been combined into a larger, much more fun project.
The proposal to integrate language design into web development is something that I'd be compelled to explore in a classroom setting, and these suggestions are quite interesting. Personally, I would enjoy programming my own web server in order to implement the language processor. Although I can't say I enjoy using Python, the proposal to use sockets and the SimpleHTTPServer API is something I would see myself doing.
A really interesting part in this paper is to see the results different implementations of this concept in multiple CS courses. Building a MVC web framework is something that would have a lot more potential, in my opinion, than making an app in a language that got discontinued one semester after we took the course, welp. As the testimony said, making an application that can be used to make applications is one of those things that personally sparks a lot of creativity.
http://34.212.143.74/publicaciones/weblang.pdf
Comments
Post a Comment