Good pivot and a humbling reminder for us all. Jonathan Blow on the day this was announced, "Very hard to describe how embarrassing this is for everyone involved in the Web and, sort of, software more generally." https://twitter.com/Jonathan_Blow/status/1387094702139142145 > Wait, Paul Graham supported this? Jonathan: Very vocally, to the point of insulting world-class programmers who think it’s dumb (he did not know…
I decided to stop working on Mighty
31–40 of 342 posts
Re: I decided to stop working on Mighty
#32I think this is a really interesting decision from Suhail and one not taken lightly. I think this decision is another data point that AI-infused applications are a potential new “tech platform” and we’re at the beginning of a new “mega cycle”. I.e. web2 2002-2010, mobile 2010-2020.
Folks shouldn’t be spending much energy on thinking about how Mighty may have gone wrong (and seriously the negative analysis is so boring and lame), and instead think about the new AI opportunity.
Re: I decided to stop working on Mighty
#33Good pivot and a humbling reminder for us all. Jonathan Blow on the day this was announced, "Very hard to describe how embarrassing this is for everyone involved in the Web and, sort of, software more generally." https://twitter.com/Jonathan_Blow/status/1387094702139142145 > Wait, Paul Graham supported this? Jonathan: Very vocally, to the point of insulting world-class programmers who think it’s dumb (he did not know…
Re: I decided to stop working on Mighty
#34Good pivot and a humbling reminder for us all. Jonathan Blow on the day this was announced, "Very hard to describe how embarrassing this is for everyone involved in the Web and, sort of, software more generally." https://twitter.com/Jonathan_Blow/status/1387094702139142145 > Wait, Paul Graham supported this? Jonathan: Very vocally, to the point of insulting world-class programmers who think it’s dumb (he did not know…
Re: I decided to stop working on Mighty
#35Quoted post unavailable.
Re: I decided to stop working on Mighty
#36But, Apple stepped in with the M1/M2 and totally obviated the need for any product like this.
Re: I decided to stop working on Mighty
#37I was skeptical about Mighty but seeing gaming platforms moving to streaming, PG endorsing this as the future, I thought I was just not getting it. Maybe I should trust myself more.
Personally I’ve tried stadia and ps now, and they both have noticeable artifacting, lower resolution, and input latency, on a 1 gig symmetrical fiber connection. The only streaming that’s remotely acceptable as a gamer is steam in-home streaming over a hardwired connection.
Re: I decided to stop working on Mighty
#38The trick of Figma claims another. I see Mighty as part of the broader trend of folks thinking Figma it the leading edge of a wider transition to web apps across all creative work. But all forms of coding and media editing (the main tasks that are truly CPU/GPU-bound, the area where something like Mighty would help) have remained as local desktop app affairs. I think what really happened is folks misinterpreted the s…
Re: I decided to stop working on Mighty
#39Probably high server costs and being a vitamin and not a painkiller killed it.
Also, people are not too happy about giving away their browser history data to server-side powered browsers.
That being said, it's still sad to see startups fail. Hopefully they'll have better luck with their new direction. Fingers crossed!
Re: I decided to stop working on Mighty
#40I 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…
> M1
To have a M1 chip, you need a new laptop. A new Intel/AMD laptop would bring you plenty performance not to require remote desktop as a service.