HN user

budwin

91 karma
Posts3
Comments23
View on HN

Just as an FYI, disconnect causes a number of login problems on a few of said sites rendering them unusable.

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...

WebOS 3.0 SDK 15 years ago

> "One of the MBAs gets in the way, makes a decision he has no place making, and hands one of HP's competitors a major competitive advantage."

This is kind of mean spirited. Why hate on the MBAs?

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.

I really feel what they said about the community and core developers:

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...

Dear Steve Ballmer 16 years ago

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?

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...

Defending IE6 17 years ago

I'm not sure exactly why there's so much controversy here.

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)