• 0 Posts
  • 30 Comments
Joined 1 year ago
cake
Cake day: July 4th, 2023

help-circle










  • Ram@lemmy.ramram.inktoAsklemmy@lemmy.mlWhy are folks so anti-capitalist?
    link
    fedilink
    English
    arrow-up
    59
    arrow-down
    18
    ·
    1 year ago

    a lot of hate for capitalism here

    The fediverse is largely populated by 2SLGBTQIA+ people and people of colour who are oppressed by capitalist regimes. The other big contingent is marxists and people who like FOSS. FOSS, at its core, is anti-capitalist.

    You’re in a place founded by anti-capitalism, that exists in spite of capitalism, asking “why is there so much anti-capitalism here?”





  • The only time Sony’s ever had stronger hardware was PS3, which was a dumpsterfire that never even ended in a profit. PS1 < NS4. PS2 < GCN. PS4 < Xbox One (by a small margin). PS5 < Xbox Series X.

    The only thing they have to their name is a bit of code made for their platform and not others, and the opportunity to buy a $700 headset that’s outclassed by a standalone $400 headset.

    The best thing that ever happened to Sony was a) Nintendo using cartridges to solidify FF as a PS franchise, and b) Sega marketing Nintendo as “for kids” back in the 90s, a stereotype they’ve never been able to get away from.






  • Ram from ReZero Peaking from a Corner

    I think this is going outside the realm of self-hosting and moreso into actually creating a server architecture. All servers would need to use the same database, so you’d want likely as its own server a database server, caches on the front-end servers so popular things aren’t queried for the same info again and again.

    I’ve never set up anything like this, so this is just me trying to think of how I’d throw it together, I’m sure there’s a bunch of async problems I’ve not even considered how to tackle, and even having the DB be offsite from either of the front-end servers would be less than ideal.

    I suppose you could have the DB in one of the servers, but then that one now has the same frontend-load as the other while it also is the only one doing DB queries, so the load’s not really being distributed properly. 🫠