91 karma · joined November 19, 2008
This is kind of mean spirited. Why hate on the MBAs?
It's extremely useful for the "evented" part, but I get the sensation of using node for hosting webpages might be overkill and not the appropriate tool. Instead, I've got the node.js core proxied behind an nginx server hosting static files and ruby rack (for when dynamic content is necessary).
Does anyone see an advantage of using Node to host templated webpages?
anyone have any kind of measure on how bytecode compares to machine code these days? (most "interpreted" languages have a hidden compile step these days). I understand that this question is largely subjective to the runtime and the task being executed.
Reading the correspondence on the following bug really turned me off to the project. http://code.djangoproject.com/ticket/5172.
Specifically: "Please do not reopen a ticket that's been marked "wontfix" by a core developer;"
I'm not sure how the issue jives with the whole Django philosophy, but with that much interest in changing the templating language, I found that a bit harsh...
And at that point, I guess I might as well write good ole html... Unless browsers _universally_ supported a new better language, I'd hate to have to think of browser nuance in two different markups...
The customers of your website should always come first, and if they use IE6, support IE6. Making them upgrade is a surefire way to alienate them or encourage them to go somewhere else. (not to mention, if you already support IE7, supporting IE6 is not that big of a stretch)