• 0 Posts
  • 13 Comments
Joined 2 years ago
cake
Cake day: July 18th, 2023

help-circle
  • Depends on the workload, really. 120 users using small services? probably. 120 users sharing large files or bandwidth heavy stuff? Doubt it. Also a lot of enterprise hardware is about reliability. Multiple PSUs, NICs, more robust hardware for constant load/network traffic, etc.

    Sure, a gaming rig can handle it until it can’t. Another question is what happens when the box crashes? Is the business down until a new PC is built and restored from backups?

    A small business can probably afford two PCs, but scaling up and up eventually becomes a lot of trouble and space.




  • No, boycotts are not a corporate death knell. No one is saying that. LITERALLY no one is saying their personal decision or reasoning is the cause of this news.

    EVERYONE ks pkinting at shitty things Ubisoft does, says, it caused them to not bjy it and likely is impacting others’ decisions… then you come along going, “NUHUH NUHUH, Ubisoft isn’t losing money because YOU didn’t buy it!”

    My dude… we FUCKING KNOW THAT!! We’re saying UBISOFT shot themselves in the foot with shitty behavior. This article is literally about the effects of people not buying en masse, and you’re saying that the NEWS WE ARE READING is not possible…

    Just stop. Just stop. Boycotts most often do not work, but THIS IS NOT A BOYCOTT!! This is people explaining why they stopped giving Ubisoft money. Holy fuck, you are good at doubling down on a bad idea.








  • IMO, “One app/library/etc does one thing only” is a rather ignorant form of wisdom about encapsulation, anyways.

    Encapsulation is important regardless of how many disparate tasks a library handles. Doing one thing with one thing is a pretty good rule of thumb to get close to good results, but it is FAR from a golden standard, and serves to drag people away from the finer nuances of encapsulation.

    The ONLY time it is a hard and fast rule is at the individual function level. A single function ideally should have one task to accomplish, even if that task has side effects.

    I’m sure there are cross-dependency issues on an OS level that makes it a bit wiser to do for widely used system tasks, but to make it an absolute rule smacks of wisdom gone awry. Like not eating shellfish in the bible.