Earlier quoted context omitted.
I'm really REALLY not sure how it makes sense to pay that much for a remote browser unless there's something I'm missing which I have to think is the case. What was the actual hook here? Surely a remote browser cannot have been worth it for 240-360 dollars a year? Wouldn't it have been more worth it to simply buy an M1 Mac or a Surface? How are people suffering from slow browsers that much?
Hence why M1 killed them. Some people do all their work in browsers.
I decided to stop working on Mighty
241–250 of 342 posts
Re: I decided to stop working on Mighty
#242Earlier quoted context omitted.
The obelus, ÷ [1]. [1] https://en.wikipedia.org/wiki/Obelus
I see, this is a novel use you have settled on. Thanks for naming the symbol for me.
Re: I decided to stop working on Mighty
#243Would be great if PG got more humble as a result, but something tells me that's never gonna happen.
Re: I decided to stop working on Mighty
#244Props to Suhail for building in the open (takes a lot of rejection tolerance) and being so honest about the path. That said, I work with lawyers as customers and I suspect there was an adjacent market in data privacy that a hosted browser would have had PM fit for. A lot of industries have strict legal requirements on controlling employee access to data (think healthcare, legal, compliance). In these cases, SaaS beco…
> The standard solution is to limit the webapp to be accessible on VPN, and limit VPN to be accessible on MDM controlled devices, and limit MDM to be accessible on company owned devices. Didn't the "BeyondCorp" zero trust model pretty much kill that, or at least show there was a better way to restricting access to secure apps than a VPN?
Of course a certificate could be stolen/transplanted but you would need to compromise the laptop first, and that’s also true of VPN solutions unless the keys are in TPMs.
Re: I decided to stop working on Mighty
#245I think it really was the M1 Chip that killed Mighty. The product itself looked like it was working great. Before the value proposition was good. You can still use your old laptop and still have a very fast browser experience via remotely running it on a AMD server chip, this way you save on battery life and RAM too. Then M1 speedometer scores started beating AMD Epyc on single core web browsing performance. Not only…
> where you do everything right
everything except for, as Suhail points out, picking the wrong side of a technical trend to bet on. All the technical wizardry in the world can't save you from bad strategy.Re: I decided to stop working on Mighty
#246Re: I decided to stop working on Mighty
#247Earlier quoted context omitted.
> I think it really was the M1 Chip that killed Mighty. The product itself looked like it was working great. Agree with this take. It's amazing he was able to get this funded at a time it was fairly obvious from their product roadmap and language that Apple was going to release ARM Macs. Props to him for the skill it took to get funding in the door.
didn't need funding skill, didnt need to look at apple roadmap, suhail's prior success as a founder was good enough for most pple
In seriousness, going by what Suhail's been documenting through their tweets, they seem to fit the relentlessly resourceful bracket to a tee, which (according to pg, at least) means they have an above average chance at succeeding doing venture-scale startups: http://www.paulgraham.com/relres.html
Re: I decided to stop working on Mighty
#248What is Mighty?
It's basically Google Stadia for web browsers; do the computation and renderning in a far-away data center and stream the result as a video feed to a local thin client program. I suppose this is an idea that could work better for web browsers than video games, but modern web browsers and sites/"applications" require fewer resources than modern AAA video games by at least a tiny margin and the pricing just wasn't competitive.
Re: I decided to stop working on Mighty
#249It made no sense to begin with, had little to no use case and was full of hype by VCs [0] and had absolutely zero path to making any money. Doomed for failure from the start. [0] https://twitter.com/ShaanVP/status/1511477714049388548
The most incredible thing about Mighty, for me, was that VCs bought into it. That... is just, wow. I guess it goes to show that the idea is apparently only a small part of their decision making process - how it's sold to them is the bigger piece by far.
Re: I decided to stop working on Mighty
#250Earlier quoted context omitted.
The product, "compute pixels on powerful machine -> render on thin client", makes much more sense if you don't try to monetize by being a cloud landlord, but you let the users own that powerful machine, make money through hardware, and help them with the software, make money through support, no subscriptions, no rent-seeking. Think at the level of a family: 2 parents, 2 children which means: 4 smartphones, 2÷3 laptop…
I find it deeply unsettling that you'd consider it normal/common to upgrade 4 digit (is that all Apple?) devices every 2 years, or that folks would need so many different form factors in the first place. Just thinking of the literal mountains of ewaste gives me goosebumps.