That won’t stop them either. They’ll just use it anyway. These companies never delete anything they might be able to use. At least not willingly.
That won’t stop them either. They’ll just use it anyway. These companies never delete anything they might be able to use. At least not willingly.
You know that’s 100% accurate. It’s EA. If there’s anything that seems good for players, it’s a mistake.
You think that will stop them? They’ll just do it and pay a comparatively small fine to the government in a decade after they get around to investigating it. And that’s the best case scenario. More realistically nothing will ever happen.
Yeah the movie issues really go back to one root cause. They needed to write and maintain a single cohesive storyline for the trilogy. Allowing the directors to also write the movies as they wanted without any apparent oversight AND switching them in the middle and back was where the issues came from.
JJ started a story, Rian came in and threw that out the window to do what he wanted, then they brought JJ back in, who basically finished the story he started, largely ignoring the middle. It wasn’t cohesive in any way and felt disjointed throughout because of it.
It’s interactive media. Why just watch when you can do?
It’s not really surprising. Maybe Hideo Kojima and his massive interactive movies were ahead of their time.
Technically, the color has always indicated the opposite of the expected default.
Passive indicators on switches like this historically have used the color to signify when something is disabled, because normally you expect that thing to be enabled. Look back to old devices with mute and disable switches like the old iPhones, Palm devices, etc. and the color always signified the thing being disabled. The default state is enabled, and the switch is disabling it.
Active indicators like LEDs being used on devices to indicate things like the mic or cam being on are generally newer. But even going back to things like the red recording lights, that’s because the expected default state was off, and the indicator was showing it was in a secondary state.
The color in both cases indicates the thing being controlled is in a secondary state, but the expected default state is different in the two scenarios.
Yes it is.
deleted by creator
With massive decisions like this that fundamentally screw up the company’s perception by clients, the CEO isn’t the only one to look at, they’re just the scapegoat.
Always need to see what happened with the rest of the Board of Directors. Are those the same people? The CEO works for the Board.
For all we know it could have been requested years ago by developers who have apps that get pirated but there was no mechanism in place to implement it at the time, and wasn’t a priority.
Just because it’s beneficial to Google maintaining more direct control now, that doesn’t necessarily mean that’s the origin.
This has almost nothing to do with Google, it’s a feature that has to be enabled by the app developer. Meaning they want to exclude users getting the APK for their app from elsewhere.
Surprised they haven’t implemented the body lottery from Cyberpunk in real life somewhere.
Look up the Kei trucks. There are a lot of them available if you’re willing to figure out transportation/pickup/delivery after import.
Why!?
Because bigger vehicles can simply ignore various regulatory and efficiency requirements.
Just not Boromir.
Eh, no one else is doing anything to provide support apart from Google either. Anyone else could do their own thing, no one is prevented from their own support. But very few companies and carriers even began to develop support for RCS, even after the Universal Profile. That is why Google developed their own support and built that support into the native app.
Verizon had their own RCS support via a proprietary carrier-specific app that never worked with anyone outside Verizon as far as I remember, and they dropped it in favor of Google’s option as soon as that was available. Samsung had their own RCS support in their proprietary Messaging app, also dropped because Google provides the same support on all of their products and Samsung doesn’t have to do anything or support it in any way. Google now provides an option for all Android devices specifically because almost no one was adding support on their own.
Anyone can, no one else will, because they have no reason to. The average user doesn’t care whether it’s Google, their carrier, or the manufacturer providing support for sending high quality photos to their friend’s phone number as long as it works.
Samsung had support before Google and Jibe… but they have abandoned their own RCS support. Simply because Google’s works on all of their devices and they don’t need to do any development to support it going forwards. Why pay for development and support for a system you don’t have to and get nothing from? No one is buying a Samsung phone for the Samsung Messages RCS capability.
This isn’t done out of altruism.
I never said or even got close to claiming that it was.
But there is a distinct difference between Google taking a fragmented RCS implementation across carriers and manufacturers on Android devices, and providing a single universally supported option for Android (the operating system that they control, but don’t prevent others from modifying heavily)… and Apple actively trying to avoid RCS support entirely in favor of their own proprietary system that does not support any products they don’t make and sell directly. Verizon had their own RCS app on Android, and Samsung added RCS support to their Messaging app on their devices, among others prior to the Universal Profile and Google adding support directly in Android Messages. That’s not something anyone can do or offer for iPhones other than Apple
Google worked to add support for essentially all Android customers. Apple decided none of their customers should be able to use RCS, whether they want to or not, simply because they had their own thing that only their customers could use and won’t let anyone else use. You can’t possibly be trying to claim that Apple is in any way a good guy here. Comparing the two directly here, Apple is clearly worse with no good reasoning for it, it is entirely for selfish reasons.
And absolutely zero users care about the reasons. They only know that sending messages back and forth is dogshit.
The source of the lack of support across is Apple not wanting to even try because they want everyone to use their proprietary system on their devices instead. Google at least implemented a system to get RCS support to as many devices as they could, even when carriers didn’t do anything to help. Apple instead had to be threatened by regulators before they even began to consider looking at it.
Tariffs in general aren’t new, but Trump’s tariffs were applied haphazardly and poorly determined because he doesn’t understand what they are. Avoiding that uncertainty entirely is a good idea.