Live data from Hacker News

With great sadness we announce the closing of Fluent.io

fluentmail.tumblr.com

41–48 of 48 posts

Re: With great sadness we announce the closing of Fluent.io

#41

Its stuff like this that makes me very cynical about a big portion of the startup world. I admire companies that stick to their vision for the long haul and don't bow out because all of a sudden they don't have enough attention/passion/whatever. You'd think that if a party comes out stating huge ambitions and a big vision for fixing a problem, they'd have the determination to match the cause.

@cynicalmood I'm curious whether you've run a startup? How long would you go without an income (if that's the "whatever" you're referring to) even if you believed in the vision?

I agree with @cynicalmood that if you don't know what it takes to pull this thing through, don't trick the users into believing you're have got solid plans. Experimenting is always fine as long as everybody involved is on the same page.

Re: With great sadness we announce the closing of Fluent.io

#42

Earlier quoted context omitted.

Email is great. But long threads with various forwards and cc's become incredibly painful. Gmail have gone some way to fixing it, but Fluent.io looked like they were doing a great job (Judging by the demo videos)

But isn't that what tools like Basecamp and such are for? Email is great, IMO people just use it for the wrong things.

>IMO people just use it for the wrong things

CC's and Replies aren't what email is for?

Re: With great sadness we announce the closing of Fluent.io

#43
post #8

> Email is quite clearly a thing that needs fixing Honestly, I've never seen it that way. Email continues to work fine. It's platform independent and easy to use/setup. It's probably one of the best things on the internet ever.

Ever tried sending an attachment to someone over 4-5mb? One of the most broken aspects of email right there and something that won't be changing any time soon. Sure you can use a service like Mediafire or Rapidshare, but it's just another step that shouldn't exist in this day and age.

In case you're interested; I've been using GMail + Attchments.me + Dropbox. Works well.

Re: With great sadness we announce the closing of Fluent.io

#44
@dhanji - thanks for all your work on this - you've inspired us all.

This post read a little bit like "This is more expensive to run in time and money than we thought - so we're shelving it for now."

Can I ask - was this move triggered by (a) Google buying Sparrow? (and thus shelving other email acquisition plans) (b) Marissa Mayer moving to Yahoo (and killing a potential purchaser strategy) (c) The release of outlook.com (creating a high speed competitor with lots of resources for distribution and support and marketing).

Re: With great sadness we announce the closing of Fluent.io

#45
post #40

Earlier quoted context omitted.

AOL released Mozilla as an independent project, which morphed into the stripped down version, Phoenix. Anyway, it was already open source by the time it was released, so it's a very different situation to this startup-releasing-open-source wish, but still the closest example I can think of, when considering only successful projects.

Netscape committed to spinning off mozilla prior to the AOL deal. Also, mozilla is an example of how releasing a closed source codebase often doesn't work, because the mozilla project ended up throwing away the old code and rewriting the engine and user interface. A better example is blender, whose source was bought out and open sourced through a community effort.

The Mozilla Foundation choose the rewrite path, it's true. Yet, the Sea Monkey project [1] is still alive. It's not like the code base vanished in thin air.

[1] http://www.seamonkey-project.org/

Re: With great sadness we announce the closing of Fluent.io

#46

Earlier quoted context omitted.

But isn't that what tools like Basecamp and such are for? Email is great, IMO people just use it for the wrong things.

>IMO people just use it for the wrong things CC's and Replies aren't what email is for?

Of course, but there is a limit. Email has attachments, CCs and replies - that doesn't mean it should be used for version control.

Re: With great sadness we announce the closing of Fluent.io

#47
post #20

Earlier quoted context omitted.

It sounds to me like you're unhappy with Thunderbird, not email. You seem to refuse to use other email clients (Outlook, Gmail, Mail.app) for various reasons entirely unrelated to sending or receiving email.

Think about what you are doing! Think about how narrowly you are defining this! You write: "sending or receiving email" And that's it? That is all we can expect of email clients? Are you arguing that no consideration should be given to concerns like storage, security, privacy, interoperability or any of the other concerns that we normally have when we use software? Can you give one good reason why all of those concer…

Tried mutt? Even runs on MacOS

Re: With great sadness we announce the closing of Fluent.io

#48
post #45
post #40

Earlier quoted context omitted.

Netscape committed to spinning off mozilla prior to the AOL deal. Also, mozilla is an example of how releasing a closed source codebase often doesn't work, because the mozilla project ended up throwing away the old code and rewriting the engine and user interface. A better example is blender, whose source was bought out and open sourced through a community effort.

The Mozilla Foundation choose the rewrite path, it's true. Yet, the Sea Monkey project [1] is still alive. It's not like the code base vanished in thin air. [1] http://www.seamonkey-project.org/

IIRC seamonkey is a rewrite of the netscape communicator codebase. The seamonkey code was what firefox grew out of (firefox itself was not a rewrite, just a refactoring).
Post reply on HN