Earlier quoted context omitted.
> The idea isn’t that transport magically disappears. The idea is that users don’t have to deploy, operate, pay for, or even think about transport. It's sharing this advantage with every other free, third party managed communication service I can choose to depend on. It's also sharing the weakness that it puts me at the mercy of whatever third party I am relying on. It introduces a new weakness in that the third part…
I don't think this was meant to be taken as seriously as you seem to be taking it
Macaroni – a single HTML file messenger
61–70 of 93 posts
Re: Macaroni – a single HTML file messenger
#62"Sending a message to your mother should not require infrastructure comparable to a small bank." To that end, requiring the use of GitHub for your application to work is a dead end. "Macaroni Messenger is a distributed messaging system" No. "The backend does not exist." Unless by "backend" you mean the underlying infrastructure and server logic you've made the clients depend on for the exchange of messages to happen.
That’s fair criticism of the current implementation. The idea isn’t that transport magically disappears. The idea is that users don’t have to deploy, operate, pay for, or even think about transport. GitHub happens to provide one out of the box, which makes the proof of concept extremely easy to try. If I need to run databases, message brokers, servers and monitoring just to send my mom “please cook macaroni”, I’ve al…
Re: Macaroni – a single HTML file messenger
#63I wonder why this type of deployment is not more popular - pushing all resources inside a single HTML file, with a script tag, and inline resources as blobs.
I created a couple Single File Web Apps: https://fuzzygraph.com and https://hypervault.github.io/.
Re: Macaroni – a single HTML file messenger
#64Re: Macaroni – a single HTML file messenger
#65Earlier quoted context omitted.
I'm not advocating this development approach, but I also think some of your reasons aren't particularly robust when scrutinized. > can't reuse a stylesheet, script or image on a different page (each has to have their own copy) Isn't the point of a single HTML file that you don't have different pages that would need to reuse those assets? > can't cache commonly used files You can still cache the HTML. > can't make gra…
If you need a build script, your app is probably too big to be a single .html already. > You can still cache the HTML. But then any time you update any part of the app, the user has to re-download the whole thing. It is also a problem with many traditional frontend builds, but if you carefully split it into chunks, you can update parts of the app while most of it stays cached. See e.g. Linear’s approach to vendor dep…
Re: Macaroni – a single HTML file messenger
#66I laughed at the 1000% vibecoded badge
Re: Macaroni – a single HTML file messenger
#67I'm a fan of the license. https://www.wtfpl.net/about/
Re: Macaroni – a single HTML file messenger
#68Re: Macaroni – a single HTML file messenger
#69"Sending a message to your mother should not require infrastructure comparable to a small bank." To that end, requiring the use of GitHub for your application to work is a dead end. "Macaroni Messenger is a distributed messaging system" No. "The backend does not exist." Unless by "backend" you mean the underlying infrastructure and server logic you've made the clients depend on for the exchange of messages to happen.
crypto needs nodes but we still consider them decentralized
direct tcp/ip communication still requires routing but etc
Re: Macaroni – a single HTML file messenger
#70Earlier quoted context omitted.
If you need a build script, your app is probably too big to be a single .html already. > You can still cache the HTML. But then any time you update any part of the app, the user has to re-download the whole thing. It is also a problem with many traditional frontend builds, but if you carefully split it into chunks, you can update parts of the app while most of it stays cached. See e.g. Linear’s approach to vendor dep…
https://fuzzygraph.com is a 1.4Mb Single HTML file that I have a build script for ( https://github.com/calebmadrigal/fuzzygraph ).
Looking again, figure it has to do all the math again with each pan/drag, so minor latency makes sense.