Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I decided to stop working on Mighty

twitter.com

Post reply on HN
Print view View original

141–150 of 342 posts

Re: I decided to stop working on Mighty

#141

Post by [deleted] »

ohgodplsno wrote: post #113
nisten wrote: 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…

There was no point paying $30 a month _period_. You could get a cheap, refurbished 2014 laptop and it would still be a better value proposition than Mighty. The only potential buyers of this service are SV tech bros, not anyone living in the real life.

[deleted]

Re: I decided to stop working on Mighty

#142

Post by fragmede »

loloquwowndueo wrote: post #42
aero-glide2 wrote: post #18

Earlier quoted context omitted.

Each tweet can have a separate discussion

And that’s good why exactly?

Because each tweet is (possibly) worthy of separate discussion. you have

Tweet 1: thesis.

t2: supporting evidence A.

t3: supporting evidence B.

Say you agree with the thesis but think evidence A is weak or otherwise want to discuss it, you don't pollute the discussion on the thesis or supporting evidence B.

Re: I decided to stop working on Mighty

#143

Post by robenkleene »

ec109685 wrote: post #109
robenkleene wrote: post #30

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…

All the heavy lifting of figma happens on your local computer. The delta between doing that in a browser in a native app is only shrinking over time.

I think the delta you're talking about is already gone. Figma is generally considered more performant with its WASM rendering approach than its desktop counterparts.

But I don't think the let's say "other deltas" that are now keeping other high-powered apps from becoming web apps are moving at all. You can check my other comments in this thread for more details, but a specific point I'm making with the original comment is that there are other areas the Figma hasn't dented at all that prevent more powerful apps from being adapted to the browser. And that the fact that design no longer needed those features is what paved the way for its success.

Figma as part of an app family, is way way more similar to Google Slides (i.e., office suite) than it is to Photoshop (i.e., "professional" software).

Re: I decided to stop working on Mighty

#144

Post by ec109685 »

hn_throwaway_99 wrote: post #81
obblekk wrote: post #57

Props 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?

Beyond Corp doesn’t mean those protections are worthless. They aren’t sufficient.

To the parent post, there’s already lots of solutions for non performance oriented Remote Desktop environments.

Re: I decided to stop working on Mighty

#145

Post by ly3xqhl8g9 »

modeless wrote: post #41

Looking at tweets like [1] it seems like their original bet was that server single core performance would dramatically outpace client single core performance. Honestly even if that had happened I still don't think their product would have made sense. The hosting cost and bandwidth/latency requirements would still have killed it. The death of this product is a good sign for computing overall. The more of computing tha…

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 laptops, 1÷2 desktops, 1÷2 tablets, each of them $1,000+ which means around $8,000+ and $11,000+, replaced every 2÷4 years. Instead of 8÷11 screens, each with it's own beefy CPU/GPU/RAM, you could have 8÷11 thin clients (at the most $200 each, for fancy cameras and larger batteries) and a powerful machine, somewhere between $5,000 and $10,000, dual CPU, dual GPU, etc., which can last 10+ years (thinking of all those refurbished servers with 2012 Xeon E5-2620s which work great even today, and have no reason not to work perfectly fine even in 2032).

Bandwidth/latency is an issue but as we are advancing in 5G+ technologies it's just a wait game.

Long live thin clients where the user owns the upgradeable fat server rendering the thin client!

Re: I decided to stop working on Mighty

#146

Post by robenkleene »

robenkleene wrote: post #143
ec109685 wrote: post #109

Earlier quoted context omitted.

All the heavy lifting of figma happens on your local computer. The delta between doing that in a browser in a native app is only shrinking over time.

I think the delta you're talking about is already gone. Figma is generally considered more performant with its WASM rendering approach than its desktop counterparts. But I don't think the let's say "other deltas" that are now keeping other high-powered apps from becoming web apps are moving at all. You can check my other comments in this thread for more details, but a specific point I'm making with the original comme…

> Figma as part of an app family, is way way more similar to Google Slides (i.e., office suite) than it is to Photoshop (i.e., "professional" software).

Digging into my own comment here, part of the reason I harp so much on the skeuomorphic to flat design change is it's such a bizarre thing to happen to an industry, for its defining requirements to change in such a way that the technology gets so much simpler.

E.g., can you imagine if realistic light rendering suddenly was no longer desirable in 3D software? Of course that would leave a gigantic opening for new players!

Re: I decided to stop working on Mighty

#147

Post by fuckstick »

oops wrote: post #123
fuckstick wrote: post #111

Earlier quoted context omitted.

> I don’t know. People without pain do take painkillers. And they can have a really hard time stopping. In that sense, I would argue that Facebook is a lot like a painkiller for a lot of people! Nice, you’ve explained by demonstration better than I could why this is a trash analogy and only confuses issues, does not clarify them. Consider stopping using it.

Quoted post unavailable.

No post body was provided.

Re: I decided to stop working on Mighty

#150

Post by bitwize »

dinvlad wrote: post #99
nisten wrote: 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…

Meh, desktop Intel/AMD chips still beat M1, and are more versatile for gaming etc.

When it comes to single core, M1 smokes EVERYTHING. And browser performance is gated by single core performance.
Post reply on HN