Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Retiring Wave

git-wip-us.apache.org

Post reply on HN
Print view View original

81–90 of 98 posts

Re: Retiring Wave

#81

Post by mseebach »

bambax wrote: post #68
jacobolus wrote: post #63

Earlier quoted context omitted.

The “key mistake” was that all of the technical parts were poorly architected and horribly buggy, and then they tried to scale up the user base using a massive amount of marketing hype before their product or infrastructure could handle the load. As a result all the hyped-up customers were confronted by a terrible user experience, felt burned, and left. Without a completely different technical implementation from top…

Maybe the tech was bad, but the marketing was worse. I never even tried Wave, so didn’t experience the bugs and bad UI, because I could never understand what it was or what family of problems it was trying to address.

Even worse, I was super excited about Wave and wanted to use it for a project - but I couldn't secure enough invites for the project team, so my trial never happened.

Re: Retiring Wave

#82

Post by mseebach »

derefr wrote: post #51
dvt wrote: post #23

Google Wave was really the spark that inspired me to "build a startup." With that said, it was a mess. It was a schizophrenic product that couldn't decide whether it was a developer platform or replacement for email. It had "everything" in the worst of ways. It really was a Frankenstein; I distinctly remember threaded conversations that wouldn't collapse, weird and inconsistent results when contributing to the same "…

> It was a schizophrenic product that couldn't decide whether it was a developer platform or replacement for email. In other words, it was Lotus Notes 2.0. One of these days, someone's gotta make a Lotus Notes 3.0 that actually makes good on the original premise, without screwing it up by adding too much other stuff (like Lotus+IBM did) or by forgetting what the problem being solved is (like Google did.) The original…

Isn't your (1) the AMP for email that Google just announced?

Re: Retiring Wave

#83

Post by neals »

I've got different kind of annecdote that I need to share now that the thing got retired.

I missed the entire wave thing. Don't know how or why. But I just missed it. And I never ever miss these kind of things. My job at the time was consulting and advising startups and I just looked silly when "wave" came up in a meeting and I had no idea what it was.

I remember the CEO saying "You didn't see the video of the developers cheering with their laptops above their head?" ... which I did not.

It's one of those things that comes back to haunt me when I can't sleep. You know, one of those awkward social interactions that nobody but yourself remembers.

So good bye Wave. Bane of my existence.

Re: Retiring Wave

#85

Post by edo »

Analemma_ wrote: post #42

I've said this before, but while I know for a lot of people Reader is the axed Google product they miss most, for me it will always be Wave. I know a lot of people didn't get it, and I can't blame them, but I was part of a six-person software team using Wave for a brief project and, despite its faults, it was the greatest communication tool any of us had ever used, and remains so to this day. Slack/Discord/Teams/Trel…

What made Google wave so great to you? (Even better than slack/Discord/Trello)?

Re: Retiring Wave

#86

Post by liveoneggs »

tedmiston wrote: post #60
liveoneggs wrote: post #43

Earlier quoted context omitted.

I like airflow the dag/re-run/cron stuff but have a project running in py2.7 and one in 3.6, what do I do?

That's definitely a good question, and one that I don't think is clearly addressed in the docs (so I might take the opportunity to turn this into a little blog post later). tl;dr - Airflow can support running multiple Python versions. Here's a three-pronged answer: 1. PythonOperator - Assuming you're running Airflow on 3.6, you can run your 3.6 functions with the normal PythonOperator. 2. PythonVirtualenvOperator - T…

I will check out the docker operator. I didn't want to drop down into the bash executor to run docker containers because it felt a little dirty.

My dev team is excited to use airflow but, in my estimation, keeping them all in lockstep with a single requirements.txt seems a little far fetched. ;)

Re: Retiring Wave

#87

Post by hnarn »

mseebach wrote: post #80
hnarn wrote: post #79

Earlier quoted context omitted.

>Google Wave could have been a killer product, but for a key mistake that is a bat light for failure — it was positioned as a replacement for email. So, the same reason Slack is now failing miserably I guess?

Positioned is the operative word here. Slack isn't positioned as a replacement for email. It might become that, it might even already be that to some, but nobody is buying a Slack subscription as part of a plan to turn off the Exchange server.

- How E-Mail Killer Slack Will Change the Future of Work [1]

- Slack is killing email [2]

- Beyond email: could startup Slack change the way you work? [3]

There are a lot more examples of this if you look.

[1]: http://time.com/4092354/how-e-mail-killer-slack-will-change-...

[2]: https://www.theverge.com/2014/8/12/5991005/slack-is-killing-...

[3]: https://www.theguardian.com/technology/2016/mar/25/slack-but...

Re: Retiring Wave

#88

Post by bitL »

Spooky23 wrote: post #58
dvt wrote: post #23

Google Wave was really the spark that inspired me to "build a startup." With that said, it was a mess. It was a schizophrenic product that couldn't decide whether it was a developer platform or replacement for email. It had "everything" in the worst of ways. It really was a Frankenstein; I distinctly remember threaded conversations that wouldn't collapse, weird and inconsistent results when contributing to the same "…

Google Wave could have been a killer product, but for a key mistake that is a bat light for failure — it was positioned as a replacement for email. Email is the ultimate killer app and ultimate whipping boy.

Ahh, that was the time I was eager to try anything coming out of Google. These days I try to stay away.

Re: Retiring Wave

#89

Post by fosco »

I used Wave along with a group of friends when it first came out often. I also setup WIAB which was almost usable but never was as 'smooth' as the google hosted Wave.

what was smooth you ask? I never had issues, I even played people in some of the games they had to great enjoyment (was never able to get this on my WIAB)

I joined Apache Wave with great excitement when it first was accepted and yet disappointed in my inability to contribute. I am not a software engineer but I tried multiple times with different IDs and the response was (paraphrasing) go check this site and pick something to work on.

as the years went on multiple attempts were made to retire Apache Wave with last minute efforts by multiple people trying to keep it going. I knew this day would come and it is still sad to see.

I am not sure if there was a better 'onboarding' for noobs available if I would have done much but I think many open source projects may fair better if their barrier to entry for them were clearer

Re: Retiring Wave

#90

Post by thunderplot »

hnarn wrote: post #87
mseebach wrote: post #80

Earlier quoted context omitted.

Positioned is the operative word here. Slack isn't positioned as a replacement for email. It might become that, it might even already be that to some, but nobody is buying a Slack subscription as part of a plan to turn off the Exchange server.

- How E-Mail Killer Slack Will Change the Future of Work [1] - Slack is killing email [2] - Beyond email: could startup Slack change the way you work? [3] There are a lot more examples of this if you look. [1]: http://time.com/4092354/how-e-mail-killer-slack-will-change-... [2]: https://www.theverge.com/2014/8/12/5991005/slack-is-killing-... [3]: https://www.theguardian.com/technology/2016/mar/25/slack-but...

These are just Time's, The Verge's and The Guardian's opinions and/or hidden ads.
Post reply on HN