I had expected Mighty to pivot to solving the giant problem of corporate computing security.
Mighty Retrospective
11–20 of 107 posts
Re: Mighty Retrospective
#12> RAM: Mighty allowed users to open hundreds of tabs without being worried that their RAM would be consumed. But my sense is this was not a killer feature. The benefit simply isn’t massive: the alternative is to close tabs and “clean things up”. Many people probably do this anyway because it’s visually hard to have hundreds of tabs open, so users end up closing tabs even with infinite RAM. This is evident in the data: when we gave users 32gb of RAM, 90+% of them didn’t go beyond 16. We did have the opportunity to provide users with a whole new interface of tab management – one in which tabs never have to be closed and hundreds of tabs are visually manageable. Maybe this would have been a smash hit, it’s hard to be sure.
What I want is for the address bar to give me a really quick way to jump to existing tabs, if I start to type in the address of one I already have open. The entire reason my tabs get out of control is that at some point I get enough open that I start to lose track of what's there, and repeat myself. End up with like 5 AWS tabs, only one of which I'm actually using, stuff like that. So finally I just bookmark the whole set ("just in case"—I've not once looked back at these, in almost a decade of working this way, though I bet there's some great shit in there) and start over.
Apple's "tab groups" approach being a solution, but the trouble is I forget to switch to the correct group for a given site and end up using a single jumbled-up session anyway. It needs better (more automatic, probably) UI.
Re: Mighty Retrospective
#13While I never really believed in Mighty as a concept, I think the technology has enormous potential in some industries. A robust, performant and versatile VNC like toolkit to enable traditionally desktop software to be made available in the cloud could be be very successful. There are many CAD, Visualisation, Rendering, Editing, and Simulation tools that are incredible CPU, GPU or Memory intensive that could be made…
Industry has been using Citrix in that problem space for nearly a decade. What does Mighty bring to the table?
parsec, nvidia's thing and a few other companies are already in that specific space as well, mighty just seemed dumb
Re: Mighty Retrospective
#14> RAM: Mighty allowed users to open hundreds of tabs without being worried that their RAM would be consumed. But my sense is this was not a killer feature. The benefit simply isn’t massive: the alternative is to close tabs and “clean things up”. Many people probably do this anyway because it’s visually hard to have hundreds of tabs open, so users end up closing tabs even with infinite RAM. This is evident in the data…
Yes tab groups has helped a lot and is nearly there but not quite.
I try and be disciplined but like you end up having to manually stop myself and drag tabs back to the ‘proper’ group.
Re: Mighty Retrospective
#15While I never really believed in Mighty as a concept, I think the technology has enormous potential in some industries. A robust, performant and versatile VNC like toolkit to enable traditionally desktop software to be made available in the cloud could be be very successful. There are many CAD, Visualisation, Rendering, Editing, and Simulation tools that are incredible CPU, GPU or Memory intensive that could be made…
There are tons of these solutions in production for well over 10 years. Big media customers has run virtualized edit bays in AWS for at least 4 years at this point.
Reasons people don't use these solutions are the same reason Mighty ended up not working. Even in CAD applications, latency matters when trying to move objects in 3D space with precise mouse input or using a 3dconnexion spacemouse. Sure, you can overcome latency by doing what Google essentially invested in with Stadia, run GPU's closer to the edge but at that point the cost of just buying workstations for your employees is not that different from acquiring a stable connection (for 8+ hours a day) with the fee of renting the hardware.
Re: Mighty Retrospective
#16I had expected Mighty to pivot to solving the giant problem of corporate computing security.
https://www.island.io/ (not affiliated in any way)
Re: Mighty Retrospective
#17Streaming Chrome with some value adds must have been a short-term product right? It could only have existed until PCs caught up on processing speed (Apple's M1?). I wonder what vision did Suhail pitch to PG to deserve high praise. Because this can't be it.
The ultimate vision is/was to have everything run in the cloud. Imagine if you could run any app on the most powerful machine in the world. See: https://blog.mightyapp.com/mightys-secret-plan-to-invent-the... In my opinion, this is the right goal, but I don't think this can be done by running existing apps in the cloud (and remoting their UI). Instead, I think we need a new cloud-native platform so that any app can b…
Hmmm. Interesting. Would the UI be local and compute remote in this paradigm? And how is that different from the old thin client model?
just read your site, and I’m thinking of this as more like a super massive global mainframe?
Re: Mighty Retrospective
#18While I never really believed in Mighty as a concept, I think the technology has enormous potential in some industries. A robust, performant and versatile VNC like toolkit to enable traditionally desktop software to be made available in the cloud could be be very successful. There are many CAD, Visualisation, Rendering, Editing, and Simulation tools that are incredible CPU, GPU or Memory intensive that could be made…
Isn’t this just Citrix?
Re: Mighty Retrospective
#19> Mighty’s short term goal was to make people more productive with their browser.
I believe the biggest reason for their failure and lack of traction is because they misidentified their value proposition from day 1.
No, loading web pages marginally faster is not going to make you more productive. It will save you a few minutes per day in the best case scenario, nothing else.
Productivity does not come from loading speed, it comes from how quickly you can identify the information that matters on a page and absorb it.
This HackerNews page took 320ms to load, but I've been on the page for 5 minutes already. They really think saving even 90% of the load time is going to make any difference to my _productivity_?
Re: Mighty Retrospective
#20> RAM: Mighty allowed users to open hundreds of tabs without being worried that their RAM would be consumed. But my sense is this was not a killer feature. The benefit simply isn’t massive: the alternative is to close tabs and “clean things up”. Many people probably do this anyway because it’s visually hard to have hundreds of tabs open, so users end up closing tabs even with infinite RAM. This is evident in the data…
> What I want is for the address bar to give me a really quick way to jump to existing tabs, if I start to type in the address of one I already have open.
Chrome's been doing this recently and I absolutely love it