“the sudden announcement of Boeing CEO Dave Calhoun’s resignation by the end of 2024 was interpreted as a response to the company’s persistent safety issues.”
I hope Boeing has serious bonus claw-backs in their contracts, because this idiot’s “cost-savings” have actually cost Boeing a fortune, and destroyed their reputation. The entire board should go.
How about wearing a wedding ring on the left hand 3rd finger? Since the 9th century, that’s primarily been a strongly Christian tradition, therefore arguably a symbol of Christianity?
The moon phase cycle is 29.5 days. The reported bug cycle is 49 days. Yet somehow, “Not strictly the cycle of the moon but close”.
With that sort of logical analysis ability, no wonder this guy struggles with stupid bugs.
Although rug-pulls like this are dubious to say the least, neither should FOSS contributors be hauled over the coals simply because, to justify continuing to commit more and more time to a project. they need to generate some kind of revenue. If more FOSS advocates donated reasonable amounts of money to the projects they use, this kind of bollocks would be much less frequent, and the long term stability of projects would increase dramatically. Sadly, way to many people donate nothing. And way too many companies, as well.
Of course, it is not always possible to avoid over-committing as sometimes the business calls for it.
Well that sounds like lazy acceptance of a bad situation for your team.
No mention of fighting for better terms for the team. If the business calls for over-committing you team, you or someone else in management have failed. Such a commitment may be indeed be unavoidable in that situation, but your job as a manager is to fight for your team to be additionally compensated for such an over-commitment.
even if it’s a blatant copy paste they can’t do anything.
They can sack you.
Not pro-corporate in any way, I don’t see how you could possibly read that into what I posted. But if you choose to sup with the devil, best use a long spoon.
Unity have already established market dominance, if not effective monopoly, as the mobile gaming development platform. They are in a position of power, they have invested large sums of money to get there, and there is really very little game developers with a product 1 or 2 years in development can do about it.
While this is going to be difficult for Indy developers, they really only have themselves to blame. Part of the task when you are making a major software platform decision as a company is to research your vendor’s financial strategy - that’s basic due diligence. Unity has been loss making for years, which either means they are not financially viable (and not a safe bet), or they are engaging in a strategy of establishing an effective monopoly position to later squeeze dependant customers until the pips squeak.
This is likely just the start, whether it’s through runtime charges, Unity control of in-game advertising, or huge hikes in seat license fees. Possibly all three.
If you want to go down that path, a password is only security by obscurity.
Port knocking is an extra layer of security, and one that can stop attackers from ever knowing your private server even exists. A random scanner won’t even see any open ports.
Always bear in mind that any random guy advising people not to use port knocking may be doing it with malicious intent. I’m sure there’s someone out there advising that random passwords are a waste of time, and everyone should just use monkey123.
An early 16 bit home computer based on the 68000 microprocessor. Versions released from the late 80s to the early 90s. It earned a cult following because it was the first home computer to have arcade quality graphics and sound (80s and 90s arcade games, obs).
It had a decent OS and business software, but at heart it was a gaming computer. It lost out to the home consoles, partly because as a fully fledged computer, piracy was rife, so big games developers moved to the very locked-down games consoles instead.