Conversation
Notices
-
@p
@TradeMinister
> C++ seems to have somehow developed a reputation for being fast. I blame Java for this.
Java: another language I never really much liked.
It's not that I'm object-averse: actually I quite like them. I liked Javascript, and especially PHP back when I did that sort of thing after my kernel days were done. It was all the other shit c+++ and to a lesser extent Java tacked on, the templates, multiple inheritance, overloading, so one could look at the source and really have no idea wtf is going on without looking at endless other files. Oh sure, in c, one might have to chase things thru header files (emacs + tags was good for this), but at least one wouldn't see some monstrously like two structs being 'added' together. And I saw no monstrosities in ObjC, just convenient shorthand for how I was already writing object-oriented c.
> So, instances/nodes won't be running on phones anytime soon.
Oh, depends: people have run small (unreliable) Pleroma instances on Android tablets and hacked Nintendo Switches, also Raspberry Pis, etc. Revolver should be even easier on hardware like that. There's how much you federate, and with how many servers. I suspect very strongly that Revolver should be able to handle more load. We'll see when it gets into the wild.
> I see no obvious way around this: a network-as-storage-and-server model seems to require a lot of local storage and network chatter.
Well, it's a matter of scale, and there are different failure modes for exceeding capacity, right?
-
@TradeMinister
> Probably because CS majors were taught C++, not ObjC.
C++ seems to have somehow developed a reputation for being fast. I blame Java for this.
> So, instances/nodes won't be running on phones anytime soon.
Oh, depends: people have run small (unreliable) Pleroma instances on Android tablets and hacked Nintendo Switches, also Raspberry Pis, etc. Revolver should be even easier on hardware like that. There's how much you federate, and with how many servers. I suspect very strongly that Revolver should be able to handle more load. We'll see when it gets into the wild.
> I see no obvious way around this: a network-as-storage-and-server model seems to require a lot of local storage and network chatter.
Well, it's a matter of scale, and there are different failure modes for exceeding capacity, right?