simanyay's comments

Back in the days, IE6 was the best browser out there.

Firefox already ships with some (most?) of these features.

Except that you did:

> I know you pretend like you don’t care, but I’m sure that down deep you’re wondering why NodeJS is getting all the attention instead of you.

(For some reason I can't reply to the reply so will have to post here.)

> But why couldn't you have both?! That's what I mean when I'm talking about a false dichotomy, you're just using a strawman argument.

You can't have both because people don't have unlimited amount of time and resources. I'm not sure why I have to explain this.

Why don't you link to git-scm circa 2009 (when Git started getting popular): http://web.archive.org/web/20090303081943/http://git-scm.com... No brand identity? Mascot (or whatever it is in the header) looks amateurish? No thought given ot typograph? And somehow Git managed to kick everyone's ass. Here's a hint how: by being better than all other version control systems and not by having the prettiest website.

Look at this site: http://kernel.org/ Design is plain, the mascot looks amateurish, there is no logo to establish brand identity. They don't know how to sell anything, this will never catch on.

The first thing you should always do is create a ticket. There you can discuss if its worth spending time on a patch and what the best implementation could be. Pull requests that come up out of nowhere usually end up in the end of maintainers' queue.

Or you can continue calling people who maintain free and open source projects in their spare time douchebags and neckbeards.

Crock made a post about JSON comments?

Anyway, I wouldn't focus on JavaScript engines because JSON is now a universal format so for languages other than JavaScript you will have to define a formal specification.

Three things:

* Comments in JSON files are not a great idea because people might (will?) abuse them to add special instructions for their own serializers. As soon as this happens we'll have a format that is not compatible with other serializers.

* JSON today is a universal format. So, what are special characters? Should '1hello' be quoted? If no, then its not a subset of JavaScript anymore. If you're writing a new specification you have to define all those things. Same with multiline strings: space after backslash?

* Why? I know that hand-writing JSON can be annoying but is this really the biggest problem we have?

Create an issue!

Our current goal is to make positive impact on TC39 (the only group working on the spec) and not to create an alternative.

However, your comment is applicable to the whole ES.Next and I share it as well.

I used to have this problem, now I just wait until the missing semicolon costs someone a day of debugging or a broken deploy.

Facebook does only talent acquisitions. They never buy products.

You don't need to log in to post anonymously. Sites, however, can disable anonymous posting if they wish to do so.

You can export your data whenever you want and the process is as easy as clicking one button: http://dl.dropbox.com/u/447925/Screenshots/ao8k.png

Nothing changes when you comment on a website using Disqus—your comment is published on someone's website and becomes their data. That said, if a comment was not originally anonymous, you have an option to anonymize it so that it is not associated with your profile and name anymore. We are and will always be on commenters' side.

This is what I can authoritatively say as a Disqus engineer. If you want more information, email to [email protected] and folks here will be happy to answer all your questions.

Anton

Things like HackerNews, Reddit, GitHub and Disqus are more useful to everyone using them when they are provided as a hosted service and not a deployable software.

We give site owners a hassle-free discussion platform that can be integrated into their websites with additional perks such as moderation tools, analytics, spam filters (trained on the whole network of websites and not just one) and others.

And people leaving comments on different websites are now able to manage and control their comments across the web, and use their Twitter/Facebook/Google accounts knowing that Disqus will never abuse their trust. Boxed software installed on different sites managed by different people would likely never be able to provide neither the integration nor the trust.

But don't get me wrong, we absolutely love open source. Check out our Code page[1] or our public account on GitHub[2]. We released many different projects, some of which are adored by the Python/Django community (e.g. Django Sentry). I think Disqus as a product is better when it is a service and not a boxed software.

Anton

[1] — http://code.disqus.com/code/ [2] — https://github.com/disqus/

Engineer from Disqus here, I work on the front-end side of our product.

Disqus doesn't slow down page load times because we use a non-blocking technique to load required files. We work hard to make sure that we don't add any performance regressions to sites using Disqus.

We are also working on making comments made via our product indexable by search engines.

As for the open source version of Disqus, I am not sure what you mean by that since Disqus is a service and not a program that you can download and install. People prefer Disqus because they don't want to spend time implementing and hosting discussion platforms for their websites just like people using GitHub don't want to spend time implementing and hosting developer collaboration software.

Anton

P.S. If you are having problems with Disqus slowing down your page, email me at [email protected] and I will check it out.

Indeed, JSHint is designed to catch those kind of mistakes. Here is the offending code and its JSHint report: http://www.jshint.com/reports/57010

Why do you need to make it at the same time as the I/O?

If you want just to comment you don't need to create a Disqus account (this behavior was from day one). You can go to any website that has Disqus enabled and comment with just your OpenID account.

However, if you want to install our widget on your own sites or become a moderator you will have to create a Disqus account. Mainly because we need to verify those accounts via email.

Hope that helps.