What a wonderful idea. Just FYI, I went to share this on facebook, and the thumbnail was white on white. You might want to put a few metadata tags in there.
let's please just celebrate our differences rather than tear each other down. This is a real insult to anyone who doesn't consider themselves introverted...
I've used Node.js to power a little "social doodling" pet project I made: http://letsdrawit.com and I find it a useful way to think about concurrency because there are certain types of race conditions you don't have to consider (for example any critical regions in memory)
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?
"- It is compiled into machine code (no interpreter, unlike Python)."
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.
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...
Maybe I missed something, but is this really how Firefox's location services work? By phoning google with the MAC address? I understood google was logging them, but didn't know they were _using_ them...
The Mozilla blog is the mouthpiece of the Mozilla foundation right? Unless I totally missed something, didn't the author on behalf of their organization, offended both of their largest platforms owners?
Definitely unprofessional for both companies involved :-/. Zoho could have taken the high ground here, but instead just sank to the same kind petty name calling.
I wouldn't feel comfortable using something like markdown until I had a firm grasp of how it works and the kind of html it writes.
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...