3 ms·
> it's hard to get everyone to run a distributed database, identity server, etc without it being some single binary. Then it's a real problem that people keep
by pessimizer 4y ago
> it's hard to get everyone to run a distributed database, identity server, etc without it being some single binary.
Then it's a real problem that people keep doing these projects in Ruby and PHP. It was a problem that was ultimately laughed off when Diaspora chose it, and it's a problem that continues to linger and continues to be laughed off.
Make it a single-binary that uses a couple sqlite files in a ~/.directory, and people won't mind running their own server. They could opt to proxy their traffic through a caching intermediary, and we could still federate those caching intermediaries. Being a mule for social traffic could be a commodity service if social were standardized properly. Ideally, one would be able to flip a switch and adjust a few dials on one's own instance to become a caching intermediary for others.
- asim 4y agoThis is sort of like the ideal and I think after ruby and php moving on to a new language that can compile down to a self executable makes sense. Whether it's rust or Go to whatever else doesn't matter as much as just taking a new shot at writing something that works. I half heartedly look at one of my own projects written in Go and wonder if it would fit the criteria but still some work to do. At the end of the day most people don't want to run anything and those that do end up with pages of documentation and maintenance burden.