Live data from Hacker News

Introducing Quip

quip.com

151–160 of 164 posts

Re: Introducing Quip

#151
I tuned out when I read "beautiful". If only writing something beautiful were as easy as picking the right word processor.

I'm amazing that anyone would enter the word processing space when we already have dominant players with years of experience doing the same.

I'm sticking to Google Drive. I don't see any advantage of Quip and like that google drive has many other features beyond Quip.

Re: Introducing Quip

#152

It's always surreal to read Hacker News threads about the stuff you make. Harsh, but realistic. Anyway, I am Bret Taylor, co-founder of Quip. I am here if you have any questions, etc. (Also posted responses on the existing thread already). Just to clarify a couple of points I have read: 1. We do support desktops. We have a really nice web app. It is Chrome/Firefox only right now. 2. We have an Android app. It is a "p…

Bret - product question for you.

The Quip blog goes to great lengths to explain why the PC is going away, and phones/tablets are the future. I agree.

Why put support into a web app vs. native apps? I get the platform argument, but that also comes at the "general" expense of user experience. Given the early stage, that seems like a division of resources.

Curious how you came to the decision to support broadly vs. platform focused.

Re: Introducing Quip

#153

It's always surreal to read Hacker News threads about the stuff you make. Harsh, but realistic. Anyway, I am Bret Taylor, co-founder of Quip. I am here if you have any questions, etc. (Also posted responses on the existing thread already). Just to clarify a couple of points I have read: 1. We do support desktops. We have a really nice web app. It is Chrome/Firefox only right now. 2. We have an Android app. It is a "p…

I think the first thing that comes to mind when you mention "word processing" is compatibility. Most of us in the real world depend on Microsoft Word - can you guys promise not to mangle doc/docx files as soon as we open it or save edits from Quip? :)

Your attitude is what makes Microsoft so prone to mangle their own doc/docx files in ways only they can understand.

By doing that, they can prevent you and everyone else from using any competing product, including this one.

I will say it again: if your document breaks it is not the fault of Quip or whatever, it is a feature of using Microsoft formats, and Microsoft revenue comes from that feature.

Re: Introducing Quip

#154
One suggestion I would like to see is a public permissions mode where anyone I share a link with can create an account and then be able to edit the doc. Looks great, very clean UI. I have been waiting for something like this!

Re: Introducing Quip

#155
post #82

Boy, Hacker News has gone in a strange direction. Killer new product from legendary engineers. Let's all get together and shit on it!

I don't see the obsession with calling this feedback harsh. I'd kill to have the feedback shared on this site (it's not like you are obligated to listen to anything), and it doesn't offend me in anyway. I actually like when people get straight to the point.

If someone were to have a mightier-than-thou attitude when giving the feedback, then maybe that would throw me, but I would more likely get annoyed because feedback from people like that tend to be redundant or just complete shit.

Re: Introducing Quip

#156

It's always surreal to read Hacker News threads about the stuff you make. Harsh, but realistic. Anyway, I am Bret Taylor, co-founder of Quip. I am here if you have any questions, etc. (Also posted responses on the existing thread already). Just to clarify a couple of points I have read: 1. We do support desktops. We have a really nice web app. It is Chrome/Firefox only right now. 2. We have an Android app. It is a "p…

Why do you need to manage my [Google] contacts for me to signup? A plain email + password signup alternative would be nice!

Tried to opt out of the contacts sharing, but I got stuck in an infinite loop and couldn't find a signup option without the Google oAuth.

The product itself looks awesome, but I can't try it out because I don't want to give away access to my entire Google account.

Re: Introducing Quip

#157
post #153

Earlier quoted context omitted.

I think the first thing that comes to mind when you mention "word processing" is compatibility. Most of us in the real world depend on Microsoft Word - can you guys promise not to mangle doc/docx files as soon as we open it or save edits from Quip? :)

Your attitude is what makes Microsoft so prone to mangle their own doc/docx files in ways only they can understand. By doing that, they can prevent you and everyone else from using any competing product, including this one. I will say it again: if your document breaks it is not the fault of Quip or whatever, it is a feature of using Microsoft formats, and Microsoft revenue comes from that feature.

You still won't be able to print that last minute contract/grant/whatever from your high horse.

You not distributing closed formats (that's why i don't use M$ office, apple products or buy sony weird media that came out every now and then) is the right thing

You preventing yourself from accessing those formats are not harming them, just yourself.

Re: Introducing Quip

#158

It's always surreal to read Hacker News threads about the stuff you make. Harsh, but realistic. Anyway, I am Bret Taylor, co-founder of Quip. I am here if you have any questions, etc. (Also posted responses on the existing thread already). Just to clarify a couple of points I have read: 1. We do support desktops. We have a really nice web app. It is Chrome/Firefox only right now. 2. We have an Android app. It is a "p…

Bret - product question for you. The Quip blog goes to great lengths to explain why the PC is going away, and phones/tablets are the future. I agree. Why put support into a web app vs. native apps? I get the platform argument, but that also comes at the "general" expense of user experience. Given the early stage, that seems like a division of resources. Curious how you came to the decision to support broadly vs. plat…

Downvote?

Re: Introducing Quip

#159
post #153

Earlier quoted context omitted.

I think the first thing that comes to mind when you mention "word processing" is compatibility. Most of us in the real world depend on Microsoft Word - can you guys promise not to mangle doc/docx files as soon as we open it or save edits from Quip? :)

Your attitude is what makes Microsoft so prone to mangle their own doc/docx files in ways only they can understand. By doing that, they can prevent you and everyone else from using any competing product, including this one. I will say it again: if your document breaks it is not the fault of Quip or whatever, it is a feature of using Microsoft formats, and Microsoft revenue comes from that feature.

I could not possibly care less. I choose software based on what works (insofar as it is a tool, and that is the foremost metric by which it is just judged), and part of working involves being compatible with the rest of the documents I handle, the vast majority of which are not produced by me (or my software choices.)

If you want to compete with Word, make it righteous and compatible, and I will purchase a copy immediately.

However, given the choice between the moral high ground or a text editor that does what I need it to do (including compatibility), I will choose the latter every last time.

Re: Introducing Quip

#160
post #153

Earlier quoted context omitted.

I think the first thing that comes to mind when you mention "word processing" is compatibility. Most of us in the real world depend on Microsoft Word - can you guys promise not to mangle doc/docx files as soon as we open it or save edits from Quip? :)

Your attitude is what makes Microsoft so prone to mangle their own doc/docx files in ways only they can understand. By doing that, they can prevent you and everyone else from using any competing product, including this one. I will say it again: if your document breaks it is not the fault of Quip or whatever, it is a feature of using Microsoft formats, and Microsoft revenue comes from that feature.

Well, I'd rather get my shit done smoothly with my co-authors rather than take a principled stand and all that. Most in the academia do not wanna change their authoring tools, especially if they are 50+. And all of this is driven by one thing: most of the conferences and journals in our field want Word submissions. I don't have the hallow effect to change that. So we'd rather everybody dance to Microsoft's tune than the other way around.
Post reply on HN