Live data from Hacker News

I decided to stop working on Mighty

twitter.com

31–40 of 342 posts

Re: I decided to stop working on Mighty

#31
post #22

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…

This happens to literally every startup tho

Re: I decided to stop working on Mighty

#32
Mighty as an idea was cool and interesting and I hope the tech survives and continues to be developed. Fat clients have their place in the world but a solution like Mighty allows for a lot of the benefits of a fat client without a lot of the downsides.

I 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

#33
post #22

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…

[deleted]

Re: I decided to stop working on Mighty

#34
post #22

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…

Hmm, I'm not quite sure how to interpret Jonathan Blow's tweet. You seem to be saying that he is saying that the Mighty project itself is embarrassing, while I took it to mean the fact that today's beefy computers, with all their CPU and RAM, struggle to render web pages to the point that someone is considering doing a rube-goldberg-esque solution of rendering on a mainframe-equivalent and then streaming you the results is the part that's embarrassing.

Re: I decided to stop working on Mighty

#36
This idea sounded bad like a lot of ideas initially sound (insert ipod nomad lame meme). There was a case to be made that consumer laptop processing speeds had completely stagnated, chrome wasn't getting any lighter, and fast internet was more readily available.

But, 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

#37

I 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.

Stadia failed too… but was that just google pulling the plug, or the whole concept that doesn’t make sense?

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

#38

The 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…

You say "what really happened" four times with four, to me, unrelated conclusions.

Re: I decided to stop working on Mighty

#39
I don't think it's M1 that killed it.

Probably 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

#40
post #29

I 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…

> use your old laptop

> 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.

Post reply on HN