Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

When you run a website, you have two choices: spend a bunch of time implementing log analysis and paying for all the storage necessary, or using GA, which already exists and is free. If log analytics isn't my core business, why should I spend time implementing it?


And if you choose GA, you accept that some people will block it, the same way they might block your javascript, your cookies, your css, your images, or anything else they don't want to download.


No, you should buy something that does log analytics for you without shafting your viewers. The existence of deceptive-but-gratis services like GA means there is almost no market for proper analysis software, which is a scandal.


Not to mention that GA much more elegantly handles the case of N > 1 webservers behind a front end.


If those are your only two choices, then you'll presumably choose the better of the two, right? So what exactly is the problem?


Depends on what variable you're optimizing for. If you're optimizing for cost, then you're right, the choice is clear.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: