Adrian pfp
Adrian
@maurerbot
Why do you think Mighty failed?
6 replies
0 recast
0 reaction

mk pfp
mk
@mk
Personally, I want anything in the cloud on my own terms.
1 reply
0 recast
0 reaction

Jonny Mack pfp
Jonny Mack
@nonlinear.eth
m1
0 reply
0 recast
0 reaction

Matthew pfp
Matthew
@matthew
Couple things: 1) It wasn't a "10x better" product. Partly due to M1, partly due to people moving away from browser for apps like Figma + Notion, but it's just not compelling enough to pay ~$30/mo. 2) Low margins. It's not cheap to run their stack— I suspect high price was necessary to offset the cost of running.
1 reply
0 recast
0 reaction

mk pfp
mk
@monishkumar
My computer was faster and it did not cost an additional $30/month. A mighty effort though. Maybe the bandwidth isn't there yet. They seemed to be counting on communication layer developments to be faster than silicon developments.
0 reply
0 recast
0 reaction

andreas pfp
andreas
@andreas
People that care deeply about speed already have good enough solutions For everyone else, there needs to be some other improvement to attract them (UX like Arc, Dapps and ad free like Brave, etc)
1 reply
0 recast
0 reaction

carlosdp.eth pfp
carlosdp.eth
@carlosdp
Never made sense on the technical fundamentals. They launched at a time when the M1 came out and computers were getting faster and more efficient. Plus WebAssembly was already getting traction, further making local browser work more efficient and fast
1 reply
0 recast
0 reaction