Earlier quoted context omitted.
Its disingenuous to claim its 4MB when the first thing it does when you run it is download 500MB of data in order to function.
It needs a browser (~50 MB, not 500) to do authentication once, then it works without it. I'm not happy about it, but there's no other way. It's still a native app, you don't have to always have a web browser running any more.
Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)
151–155 of 155 posts
Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)
#152Earlier quoted context omitted.
You mean you could make a YouTube clone in a weekend? It's easy to fall into this way of thinking. But hey, maybe you will build the next Screenhero, or TeamViewer. Or maybe you'll end up as one of the thousands of other versions of this nobody has ever heard of. The idea is usually not the hard part.
I mean that you can make a Screenhero clone in approximately the same amount of time that it took to write it originally. Should be a bit less because straight path (cloning) is shorter than twisty one (things that Screenhero did that did not end up in the final product). Note that by the time of Slack acquisition Screenhero was approaching v2.0, they had product out far longer than that. So it's not unreasonable to…
I understand they're slightly different from one another, and I suppose its possible all the commenters here went through each and every one of these options and found nothing useable but it seems unlikely to me, and similarly unlikely the +1 one would make in this pool would be any sort of revolutionary "game changer" VCs would mob onto. The space seems well-established or dare I say it "saturated".
Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)
#153Earlier quoted context omitted.
Its disingenuous to claim its 4MB when the first thing it does when you run it is download 500MB of data in order to function.
It needs a browser (~50 MB, not 500) to do authentication once, then it works without it. I'm not happy about it, but there's no other way. It's still a native app, you don't have to always have a web browser running any more.
Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)
#154Earlier quoted context omitted.
When they're old enough to work they'll be forced to interact with people who aren't their friends, and then they'll discover a new appreciation for email.
It won't go away all at once, but a scant few years after "they're" old enough to work, their friends will have been as well, and just we don't consider a company without a website to be a "real" company in this modern times, a company without a Signal/Facebook Messenger/Snapchat contact link will be seen as old and antiquated. I will mourn the loss of the federated open system we call email, and perhaps you're right…
The non-email world is fragmented. Signal? Facebook? Snapchat? Whatsapp? None have achieved ubiquity and their audience is constantly churning over to the next fad platform. Facebook has the best shot and there's still a huge part of the population that doesn't want their FB life to intersect with their work life.
Email is the lowest common denominator. The fact that "younger generations" (as if every 3 years is a "new generation"?) choose a different platform only reinforces the value of email as the only thing that everyone can agree on.
Re: Screen sharing in Slack, made interactive via Screenhero acquisition (YC W13)
#155For anyone wanting to roll this themselves, it's actually quite easy with Chrome media capture these days. Just make a Chrome extension with desktopCapture permissions, follow the example codes to do things like chooseDesktopMedia and webkitGetUserMedia and let them choose the desktop (or tab). You can do what you want w/ the media stream after that (like capture to blobs which you can send around, or send over WebRT…
Slack, Hangouts, Appear.in all use it and on Mac in particular it seems to use alot of CPU.