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

I think a better question is what problems they haven't faced.


This is an extremely frustrating thread to follow. We have some people who have run a Tableau server with no issues, and now two people who are effectively saying "oh, it's awful but I have no interest in telling you why".


five people telling in detail horror stories that make every other devop feel the pain? (except those seasoned exchange-experts of course)

did you ever consider there might be valid reasons some folks prefer *nix based servers?


five people telling in detail horror stories that make every other devop feel the pain?

Check the timestamps of those messages vs mine. At the time there were only the two responses I mentioned.


you have a point there


I wouldn't even know where to start to be completely honest.


Thanks for your honesty, but I hope you understand that's completely useless. I might have preferred if you lied.


To be completely honest I've never even heard of Tableau.


> I think a better question is what problems they haven't faced.

Deploying visualizations without having to develop any HTML or JavaScript code.

Publishing to the desktop (Windows or Mac), to the web, to the cloud, or mobile devices (iOS and Android). Publish to the server once, consume on all supported platforms.

Deploying a copy of a current site for redundancy, testing or development. Install the app, backup the primary Tableau database with its admin utility (command line), restore it on the new box. All data, visualizations, users and permissions are contained in that single restore step.

Tableau means I spend time working with my data, instead of the presentation of it. Its not a perfect product by any measure, and could obviously use some improvements, but is a timesaver in many areas.


+1




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

Search: