Elderos @ Elderos @sh.itjust.works

Posts

0

Comments

90

Joined

2 yr. ago

I don't know about the former, but yes to the later.

The idiots are being manipulated in cults and are pushing twice as hard compared to other demographics to get their guy in. Meanwhile a majority of average people are straight up not bothering with the process at all. We're really not good at governing ourselves past a certain size, because we only care about the stuff that directly affect us. The cults are merely providing fake issues to get the idiots out.

I read the Tweet, it does not "show" that the account had purchased games. This has been Ubisoft's policy for years and there is no record of deleted account, except for a random tweet.

This is misleading and ragebait. They only delete old-ass accounts without purchased games, and this is a compliance thing with European laws.

It certainly adds up, and it makes maintaining the databases more complex and costly as a whole.

Imo this is just lazy, they could at the very least "archive" old accounts and move the bare minimum data out of the main DB, as to make it possible to reactivate the account later on. Why can virtually every platform keep old account arround, but not Ubisoft?

What you seem to be describing is one big class with lots of responsabilities, and not circular dependency. Personally, I don't think it is ideal, and I don't know about your specific case so I could be wrong, but I have never seen a legit case for bloated classes. That being said, making a big class is still much better than splitting it into inter-dependant classes. Classes that know each other are so cohesive that they might as well be the same class anyway.

To add onto the circular dependency problem, it is not just about readability and cognitive load (though there is some of that), but cyclic dependencies actively break things, and make it much harder to manage the lifecycle of a program. No dependency injection, poor memory management, long compile times. It is a huge hack, and I understand that you think it can be the proper solution sometime, but it is really just a bad thing to do, and it will bite you some day. And I am assuming here that you're using a language that is friendly, in some languages you won't even compile past a certain point, and good luck cleaning up that mess.

It does not get more complicated to split your example. What gets more complicated is giving all sort of unrelated responsabilities to a single class, simply because it is the path of least resistance.

In your example, all you need is an extra module listening for configuration changes and reacting to it. This way you leave your context-specific logic out of your data model, no need for cyclic dependency. There are so many downsides to cyclic dependency, to justify it because splitting your logic is "too complicated" really isn't a strong argument.

you're blind af

afaik nothing that has been happening to tfg is related to biden. It is mostly conservatives going after him, or independant in the case of Smith.

Agree with you, but small nitpick, password sharing was encouraged at some point, at least from the PR side of the business.