Live data from Hacker News

Google Ending Support for Jamboard

workspaceupdates.googleblog.com

81–90 of 289 posts

Re: Google Ending Support for Jamboard

#81
I wonder in these situations: why don't they spin it off / sell it to some other smaller company that doesn't need a Billion Users to succeed?

Never used it myself, but it looks like a useful product. Shame to have it disappear if there are still enough people who would buy it.

Re: Google Ending Support for Jamboard

#82
post #63

Earlier quoted context omitted.

> What if there was a corporation that bought out every entrant involving new technology (not necessarily monopolizing their already dominant verticals, but other new inventions/ideas)? They either have a winner, or they stifle innovation in corresponding area for the lifetime of any associated patents. There are companies like this: patent trolls. That's why the big tech companies all have patent sharing agreements…

It sounds like a corporation could impede the humanity/progress of countries that respect these patents by patent_lifetime * number_of_patents so long as they have the money to do so.

You do realize you are describing the exact thing that's currently plaguing the software industry, among others?

Re: Google Ending Support for Jamboard

#83

I wonder in these situations: why don't they spin it off / sell it to some other smaller company that doesn't need a Billion Users to succeed? Never used it myself, but it looks like a useful product. Shame to have it disappear if there are still enough people who would buy it.

Probably it is too tightly integrated with other google internal services to be able to give the code to a third party and have them operate the business.

Re: Google Ending Support for Jamboard

#84
post #10

This is a bummer, I use Jamboard (the software not the hardware) to draw diagrams during Zoom calls and send the link to participants after. I mostly use a Wacom tablet to do the actual drawing. Any good free alternatives out there ? Edit: The proposed alternatives they mention in the update (FigJam, Lucidspark, and Miro) really don't fit that workflow.

https://mural.co/

Mural has a free tier. I did not used it much but was nice.

Re: Google Ending Support for Jamboard

#86
post #28
post #10

This is a bummer, I use Jamboard (the software not the hardware) to draw diagrams during Zoom calls and send the link to participants after. I mostly use a Wacom tablet to do the actual drawing. Any good free alternatives out there ? Edit: The proposed alternatives they mention in the update (FigJam, Lucidspark, and Miro) really don't fit that workflow.

I've been enjoying Excalidraw a lot[^1]. It lets you share diagrams without accounts and you can even collaborate in real-time. [^1]: https://excalidraw.com/

Seconding Excalidraw! A feature I really like: you can export diagrams in PNG with the scene data embedded in the image metadata. This lets you modify the diagram by opening the PNG image directly.

Re: Google Ending Support for Jamboard

#87

I wonder in these situations: why don't they spin it off / sell it to some other smaller company that doesn't need a Billion Users to succeed? Never used it myself, but it looks like a useful product. Shame to have it disappear if there are still enough people who would buy it.

Probably it is too tightly integrated with other google internal services to be able to give the code to a third party and have them operate the business.

In some senses it is a bit of an indictment on Google's cloud offering that their teams don't build it on those.

Re: Google Ending Support for Jamboard

#88

I wonder in these situations: why don't they spin it off / sell it to some other smaller company that doesn't need a Billion Users to succeed? Never used it myself, but it looks like a useful product. Shame to have it disappear if there are still enough people who would buy it.

Probably it is too tightly integrated with other google internal services to be able to give the code to a third party and have them operate the business.

And that also would be why they are shutting it down.

Google internal services are always being rewritten, and code migrated from the old version of the service to the new one. If nobody is willing to migrate an externally visible product, it has to sunset at the same time that the internal service does.

This philosophy does wonders for internal code quality and consistency. It also makes people outside the company wonder whether they should trust Google's public offerings.

Re: Google Ending Support for Jamboard

#89
post #87

Earlier quoted context omitted.

Probably it is too tightly integrated with other google internal services to be able to give the code to a third party and have them operate the business.

In some senses it is a bit of an indictment on Google's cloud offering that their teams don't build it on those.

The issue though would be the source code. Most projects at Google are developed in the monorepo and this makes it very difficult to split things out (to sell, or in some cases to open source) because the code likely links to all kinds of internal things.

Re: Google Ending Support for Jamboard

#90
post #87

Earlier quoted context omitted.

Probably it is too tightly integrated with other google internal services to be able to give the code to a third party and have them operate the business.

In some senses it is a bit of an indictment on Google's cloud offering that their teams don't build it on those.

Steve Yegge had a great rant around a dozen years ago that explains why their teams don't.

https://gist.github.com/chitchcock/1281611

Post reply on HN