I’m actually happy that Mighty did not succeed. A more centralized web with dumb terminals is not what we need. I was always a bit disappointed to see Paul Graham hyping it up.
Suhail is super smart though so I’m sure their next chapter is going to be awesome!
I decided to stop working on Mighty
301–310 of 342 posts
Re: I decided to stop working on Mighty
#302Honestly one of the most "But why?" startup ideas I'd ever heard of. I figured pg's hype for it was based in thinking it could someday be targeted for profitable acquisition by Google. But perhaps the current tech industry downturn (plus Stadia's death) made that obviously untenable. At $30/month, this sounded like something that could only be worthwhile for businesses (though I'm at a loss to imagine what size/indus…
I think pg likes slightly naughty ideas. Didn't he famously want to program a server using instructions send over email? And this Mighty idea was quite naughty. Stream like Netflix but it is your whole browser. And also pg really hypes YC companies which, bless his heart, is what we all expect and why YC is such a beast.
PG hypes a very infinitesimal subset of YC companies.
Re: I decided to stop working on Mighty
#303Earlier quoted context omitted.
Wait until adblockers stop working, and see many people start seeing YouTube ads again. Will they agree to stay on Chrome?
My only use for chromium is youtube. I only watch a handful of channels but things are getting ridiculous. Sometimes I get ads every minute. Every minute! Just the other day I got served 5 ads in a row after a simple fast forward. I gave up TV more than 20 years ago and this crap is way worse. What can I do without letting them in my actual browser? These people are crazy.
I watch youtube through firefox with adblock on
Re: I decided to stop working on Mighty
#304Earlier quoted context omitted.
I don't consider it normal at all. Seems like the words of an out-of-touch upper cruster. Most people make a 1k$ purchase last decades. Enthusiasts may be dropping 5-10k$ but not your average joe.
WTF? Mostly you can't even use consumer technology from "decades" ago - it's incompatible. In 2005 the average size of a TV was 30 inches. Two decades ago a TV had no HDMI, and it only received analog NTSC or PAL. A phone was 2G - 3G was the thing about to be but mostly not there yet. One decade ago the iPhone 5 was released. An Apple iBook cost $1200 with 128MB of ram and a PPC processor: https://apple-history.com/i…
My old gaming computer from 2013 still plays 2022 games on medium-high settings just fine. You can make computers run for a long time if you put in the effort.
Re: I decided to stop working on Mighty
#305Earlier quoted context omitted.
I see, this is a novel use you have settled on. Thanks for naming the symbol for me.
With this specific meaning of "range between"/"closed interval" it is often used in Eastern European italo-/franco-phone languages/texts. A short history of obelus on StackExchange [1]. [1] https://hsm.stackexchange.com/a/9530
Ah ha I see. Thank you.
Re: I decided to stop working on Mighty
#306Earlier quoted context omitted.
latency
I've played a 50hrs of Xbox cloud games in the last 2yrs and never had latency issues The people saying this either haven't used it recently or need a modern ISP
>I've played a 50hrs of Xbox cloud games in the last 2yrs and never had latency issues
Gonna be honest , I'm not taking gaming advice off someone who has played only 2 hours per month.
Especially with regards to something like input lag.
Re: I decided to stop working on Mighty
#307Earlier quoted context omitted.
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.
You probably need some post-rendering to speed things up. And send the data as entity state changes. Like hot and sexy X11 done since I was born. The render, compress, send over IP, decompress pipeline will just always feel laggy and slow.
I agree with the idea, but it may depend on how the X11 application was written.
My experience with X11 over a network (across a city, geographically and distance-wise) was very poor. Slow updates, just extreme latency in doing anything. Not impossible to use, but definitely unusable by any reasonable metric. We're talking dozens of seconds for most GUI interactions.
I eventually piped it through RDP (mRDP, iirc), which itself was piped through a VPN. This vastly improved performance and made it so that I didn't have to be physically present at my workstation. Just as well, since it was during the early covid timeframe.
Re: I decided to stop working on Mighty
#308I agree with Casey Muratori's take on this one:
Running a browser to connect to the cloud to run a browser to connect to the cloud to retrieve the contents of a single 2D page to recompress and send back to the original browser is now "the future of computing".
Re: I decided to stop working on Mighty
#309Earlier 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 think something like this could make sense as a place to run large machine learning models locally. I don't need a server to run my browser or my apps, they run just fine locally. But a server to run large language models, Stable Diffusion, Whisper voice recognition, etc would be useful, as these types of models can run much faster at higher quality on a beefy GPU than they ever will on a phone. The endgame of thes…
Precisely, data will become the ultimate material, from chemputers [1] to neural laces, it's all data, and having the user be the true absolute owner of it, as in actually owning the database, is paramount for any sane future use and development of technology. More thoughts and some code on this [2].
After the user owns a server capable of storing the databases and the function execution contexts (see deserve functions) for all their services, having also pixels rendered there and sent to thin clients it's just a matter of convenience and security: no more worries that the device you carry all day can be broken or stolen, it's just a low-cost piece of glass with an uplink to your server.
[1] http://www.chem.gla.ac.uk/cronin/news/cronin-group-builds-ch...
Re: I decided to stop working on Mighty
#310Earlier quoted context omitted.
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.
And even among households that do have so many devices, aren't the kids' devices typically "replaced" with hand-me-downs from the grownups rather than with totally brand-new devices?
It was just a bit of napkin mathematics seasoned with some quickly searched statistics of averages. The greater point is that thin clients become truly relevant when the user also owns the rendering machine, think of self-cloud.