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 laptop…
I decided to stop working on Mighty
201–210 of 342 posts
Re: I decided to stop working on Mighty
#202Earlier quoted context omitted.
That character is what I'd use for"x divided by y". Is it common use somewhere to use it for "between x and y inclusive"
The obelus, ÷ [1]. [1] https://en.wikipedia.org/wiki/Obelus
Re: I decided to stop working on Mighty
#203Suhail’s Twitter is definitely worth a follow as he is regularly tweeting about the everyday problems and challenges of running a startup. If you’re interested in the space it’s a good mix of technical and startup challenges and is one of the few Twitter accounts that provides great content all the time (in my opinion)
Re: I decided to stop working on Mighty
#204Earlier quoted context omitted.
yes! this is the same reason I’m glad Stadia died. “cool demo” does not equal “practical business”, and local compute will always be superior to cloud compute.
Stadia was amazing and worked great even for games that required semi-high latency. The problem was the business model.
It might have been OK for mobile games, but then they were just competing with themselves, with an arguably inferior product (if I can't play my mobile game anywhere, only in the vicinity of my house where I already have my high powered rig, what's the point?)
I do think it was an attempt to defeat a very legit, widespread use case to try tk justify pushing thin clients on everyone, glad it failed.
Re: I decided to stop working on Mighty
#205Earlier quoted context omitted.
The obelus, ÷ [1]. [1] https://en.wikipedia.org/wiki/Obelus
Your own link states that this is primarily a division symbol, hard to take this seriously...
[1] https://en.wikipedia.org/wiki/Obelus#:~:text=It%20also%20has....
Re: I decided to stop working on Mighty
#206Earlier quoted context omitted.
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.
Re: I decided to stop working on Mighty
#207I 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…
> I think it really was the M1 Chip that killed Mighty. The product itself looked like it was working great. Agree with this take. It's amazing he was able to get this funded at a time it was fairly obvious from their product roadmap and language that Apple was going to release ARM Macs. Props to him for the skill it took to get funding in the door.
Re: I decided to stop working on Mighty
#208Earlier quoted context omitted.
To a degree yes but acting like anything that uses <500MB of RAM is a disaster goes beyond what is a reasonable concern in my opinion.
I think you got your greater than sign the wrong way around? Consider a lot of non-tech people don't constantly upgrade, and still rock 4GB systems, at least an eighth of that resource is a big ask for a sloppy app (unless it is the only app they use on the device).
For games etc yes 32GB+ is fine but we went the wrong way thinking what we have is acceptable.
Re: I decided to stop working on Mighty
#209Earlier quoted context omitted.
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 laptop…
I find it deeply unsettling that you'd consider it normal/common to upgrade 4 digit (is that all Apple?) devices every 2 years, or that folks would need so many different form factors in the first place. Just thinking of the literal mountains of ewaste gives me goosebumps.
Re: I decided to stop working on Mighty
#210Earlier quoted context omitted.
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 laptop…
That character is what I'd use for"x divided by y". Is it common use somewhere to use it for "between x and y inclusive"