> I’m hoping the citizenry realizes who’s to blame here

So... Apple?

My headphones certainly don't have trouble connecting to a device of any manufacturer without loss of functionality, but some of the "citizenry" seems to fall for marketing materials saying only apple can do things securely and in an integrated manner

▲

Aurornis 5 days ago | parent [-]

You can connect airpods to a non-apple device and use them for audio.

This is more of an iPhone / iOS feature which uses the airpods as the microphone and audio output.

▲

digitalPhonix 5 days ago | parent | next [-]

> This is more of an iPhone / iOS feature which uses the airpods as the microphone and audio output.

Right, so why can’t I connect my non-apple Bluetooth mic + audio output and get the same functionality?

Either it’s an airpods thing and it should work airpods + any host device; or it’s an iPhone thing and should work with any iphone + audio device

▲

lucb1e 5 days ago | parent | prev | next [-]

Um, yes I can do that with headphones and earphones too on non-iPhone/iOS. Not understanding the thing that is a special iPhone feature that no other vendor should be allowed to interoperate with

	▲	intrasight 5 days ago \| parent [-]
		>Not understanding the thing that is a special iPhone feature that no other vendor should be allowed to interoperate with Exactly. And Apple intends to keep it that way ;)

▲

concinds 5 days ago | parent | prev [-]

It's a purely software limitation. That is, it's a purely arbitrary limitation.

▲

sroussey 5 days ago | parent [-]

Is it? Apple does weird Bluetooth and WiFi stuff in the H2 chip.

▲

const_cast 5 days ago | parent [-]

They should stop doing that then and use standards like everyone else. If their protocol is really the bees knees, then just open it.

But, they won't, because they rely on that moat to keep competitors out. It's exactly the same at the lightning cable.

▲

jandrewrogers 5 days ago | parent | next [-]

> They should stop doing that then and use standards like everyone else.

Many of those standards are objectively poor. I don’t want to live in the world where what we are allowed to use is defined by the lowest common denominator of mediocre engineers.

Mediocrity über alles is what you are tacitly advocating for. I’ve been part of many standards processes where the majority democratic outcome was low-quality low-effort standards that were extraordinarily wasteful and inefficient because the people making the standards didn’t care, it was all about what was expedient for them. This is the default state of humanity. No one should be forced to comply with that garbage by regulatory fiat if they don’t want to.

	▲	const_cast 4 days ago \| parent [-]
		> Many of those standards are objectively poor. Okay, fine, I already covered for this. If your new protocol is really the bees knees, then open it, problem solved. > No one should be forced to comply with that garbage by regulatory fiat if they don’t want to. They're not.

▲

techpression 5 days ago | parent | prev [-]

The standards are really bad and it’s not just about protocols but hardware. Should they give away every hardware design needed too?

Lighting was an incredible boon in an era of micro usb, people just seem to forget how shit everyone else was. Now we have usb-c where companies are required to supply the port but doesn’t have to follow any actual specification, yay for standards.

▲

const_cast 4 days ago | parent [-]

> The standards are really bad and it’s not just about protocols but hardware.

Okay, if their hardware is esoteric, open the protocols for interacting with hardware.

> Should they give away every hardware design needed too?

Yeah probably. It would be a lot better, more like x86. We would actually get repairable phones instead of landfill fodder. But that's a different issue.

> Lighting was an incredible boon in an era of micro usb, people just seem to forget how shit everyone else was. Now we have usb-c where companies are required to supply the port but doesn’t have to follow any actual specification, yay for standards.

And then it became a cheap scam, whereby Apple made a few dollars off of every single lightning cable produced by anyone on Earth due to licensing.

Also, as for USB-C - doesnt matter, still better. My chargers work across multiple devices. Yes, there's some standards noncompliance, this is still a huge improvement over ZERO cross compatibility.

▲

techpression 4 days ago | parent [-]

Last time I checked x86 is not open, it’s licensed just like the lightning cable, och and USB-C.

▲

const_cast 4 days ago | parent [-]

Its comparatively much more open, with interface and protocols specified and open source firmware implementations widely used in the wild. I'm also including BIOs/UEFI in this.

ARM and phone manufacturing is a hot mess in comparison. We're still trying to reverse engineer M series MacBooks and iPhones are off limits. Android is also not open source, no AOSP does not count.

There would be a lot more competition in the space if the hardware had proper specs, like x86 does.

	▲	techpression 4 days ago \| parent [-]
		What competition has x86 seen? I’m old enough to remember when there was more than Intel and AMD. When did they last license x86 to a competitor, 30+ years ago? It’s great that documentation exists, but it doesn’t make for competition. ARM is at least licensing out to more than two manufacturers.