The long-awaited day is here: Apple has announced that its Messages app will support RCS in iOS 18. The move comes after years of taunting, cajoling, and finally, some regulatory scrutiny from the EU.

Right now, when people on iOS and Android message each other, the service falls back to SMS — photos and videos are sent at a lower quality, messages are shortened, and importantly, conversations are not end-to-end encrypted like they are in iMessage. Messages from Android phones show up as green bubbles in iMessage chats and chaos ensues.

Apple’s announcement was likely an effort to appease EU regulators.

  • noisefree@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    17 days ago

    ding ding ding The microwave analogy they were going after makes no sense. I mean, there are semantics at play and I could have explicitly mentioned I wasn’t talking about firmware in order to exclude things that are essentially calculators and clocks but I didn’t anticipate someone going the direction of absurdist bespoke microwave OSes given that firmware alone is enough. Even at that level, you have examples like Seiko Epson inventing precision timed ticket printers for the 1964 Olympics - they’re still dominant in the arena of commercial printers to this day, yet they have allowed other manufacturers to adopt their ESC/POS language as a standard that’s still widely used across brands today, allowing for feature parity on the software functionality side from competing brands while Epson competes on the hardware reliability side. (This isn’t an endorsement of Epson, their consumer printers are trash because they’re not Brother laser printers lol.) Spoiler alert, the price tag of a commercial printer doesn’t have much to do with it being compatible with network standards (???! - standards being the key word here) and has more to do with reliability and general feature sets (in that order once competition exists for a device, see Epson vs feature identical Beiyang (insert other generic clone brand here)) and the same would hold true even if we decided to network our microwaves in some scenario where we’re also automating food going in and out of the microwave.

    All of that said, if I were to modify what I was saying while keeping the sentiment the same, I would just simplify it by saying “no hardware vendor is allowed to lock their hardware to running specific software” (doesn’t mean they have to provide technical support for errors in another vendor’s software) since that gets at the root of the issue. But, going back to the original sentiment, open standards that have nothing to do with specific hardware are clearly better. Look at Apple vs x86 vs ARM, specifically Apple during the period between PowerPC (at least there were partners here, so the chips had lives outside of Apple hardware) and their M-Series - they wouldn’t have had an excuse not to offer something like BootCamp during the x86 era given that their OS clearly was able to run on off the shelf PC components and the inverse with Windows and Linux being able to run on their hardware was also clearly true. Is it a good thing that Apple hardware is once again locked in to running only their software?