2 ms·
The web is also rather complicated to set up and run. A simple binary that one builds or downloads and runs is often far simpler than setting up VPSes, SSL, an
by berkes 3y ago
The web is also rather complicated to set up and run.
A simple binary that one builds or downloads and runs is often far simpler than setting up VPSes, SSL, and so forth. And typically "web" projects are ran on complex setups where one needs the right runtime, a database, some weird bundling/dependecies step (that breaks after a few months).
Shoes has the same problems of a fickle runtime and flakey bundling step as Rails, Django, Laravel,Express and whatnot have. So it's a bad example.
But a single statically built go or rust binary is just so much easierto runthan hosting any web-app.
- bbor 3y agoAll very fair! I guess I was thinking of the small CLI-related usecases that this is a more natural fit for. Writing a little monitoring gui for your program, making a few graphs from local files, etc. In that context I see web only requiring one-command startup (ie `npm start`), maybe two if you want a database. And then you have the entirety of the internet to steal from, rather than just the other Shoes/Textual devs. Long story short, I think your answer is a great consideration of typical modern web servers, but I was suggesting the use of the protocols in a more unusual way. Namely, writing web programs that you don’t intend on ever publically hosting