| |
| ▲ | rkagerer 2 days ago | parent | next [-] | | <Waves to you> Neat, thanks for sharing this tidbit of history. Hey, what did the team think of the decision to build it on GWT at the time? (From the outside, seemed like an enabling approach but a bit like building an engine and airframe all at once). | | |
| ▲ | pamelafox a day ago | parent [-] | | Hm, I didn't work on the frontend but I don't particularly remember griping..GWT had been around for ~5 years at that point, so it wasn't super new: https://en.wikipedia.org/wiki/Google_Web_Toolkit I always personally found it a bit odd, as I preferred straight JS myself, but large companies have to pick some sort of framework for websites, and Google already used Java a fair bit. |
| |
| ▲ | floren 2 days ago | parent | prev [-] | | Wave was extremely cool and I wish it had stuck around. Hope it was as fun for you to work on as it was for us to use. | | |
| ▲ | pamelafox a day ago | parent [-] | | It was fun! Now we still see Wave-iness in other products: Google Docs uses the Operational Transforms (OT) algorithm for collab editing (or at least it did, last I knew), and non-Google products like Notion, Quip, Slack, Loop from Microsoft, all have some overlap. We struggled with having too many audiences for Wave - were we targeting consumer or enterprise? email or docs replacement? Too much at once. The APIs were so dang fun though. |
|
|
