Localhost Will Inevitably Die
lucasfcosta.com
lucasfcosta.com
Definitely yes.
However, experiments, proof of concept, shy little prototypes always start on a sheet of paper and then on localhost. Before going somewhere else.
In 20 years, the only satisfying places for work, in design, software dev and engineering, were where we could run internal experiments from localhost or even from a shared, always on system on which we could deploy and share our own internal pages and blogs.
Because of the fragile, imperfect, shared, impermanent nature of that infrastructure (co-owned within the product team), expectations and care, both in building and in critique, had a profound impact on the teams.
If you can't reliably run production on localhost, it's not because there is something fundamentally wrong with localhost. You're just not running your workload on a beefy enough localhost to remain local.
Think about it. All those cloud hosted workloads? All of them exist in a relative localhost.
I hold that in reality, localhost is the ideal, and any network hosts are the compromise you make because you just can't afford "dat localhost you actually need". The detail orientation and willingness to lay out things sufficiently on localhost by a singular developer simply exhausts.
You have 65535 ports. You can with the right hardware/architecture have truly ridiculous amounts of addressable RAM. Processors? Same deal.
The weak point of course, is your funding, and your willingness to get everything lined up. Which requires attention. Which is finite.
When dealing with teams of developers, there is the additional challenge of handling individual idiosyncracies, which is another issue that network partitioning naturally lends itself to spackling over, but even then, localhost is still theoretically capable of accommodating it.
I don't need to run all of production, just enough of it to get the job done with no shared parts. That's usually very little.
I meant that enabling/promoting localhost (or assumed shared, small, inconsequential dev/demo environments)-based development for sorting/trying/demoing out things, sometimes ludicrous ones, is a must when you want to favour innovation in your org.
It goes totally against IT security and silo'd orgs (especially in large ones), so it does not happen without a clear understanding/enablement of the benefits of this from very high up in the chain of management.
I was basically pressing Ctrl in that one guys workflow with my project at the time. Fun as all hell. Love a thoroughly tasked computer.
On a side note, this last year I had the displeasure of developing on an existing all serverless ETL system with 30+ lambdas all hooked together in confusing ways. Debugging was a nightmare. In the future I will try to avoid any project that requires me to dev in a non-local environment, unless there’s a platform team that’s producing tools to improve the developer experience .
> 30+ lambdas all hooked together in confusing ways.
You can use localstack to run them locally, but tooling definitely sucks either way.
On the other side, loosing deployments to some "cloud solutions" will make things worse for everyone and general PC computing - right now macOS and Windows is only usable for development and general PC computing because of software engineers needed it. The moment it will be fully replaced by cloud - all major OSs will be locked down as much as possible.
Branding "serverless" as a cloud feature was a huge marketing ploy - there were serverless software before cloud existed, it was running on your personal computer, not on someone else's server.
Same for localhost.
Localhost should be alive forever.