Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Epic says Apple will reinstate developer account

9to5mac.com

Post reply on HN
Print view View original

651–653 of 653 posts

Re: Epic says Apple will reinstate developer account

#651

Post by PlutoIsAPlanet »

idle_zealot wrote: post #494
PlutoIsAPlanet wrote: post #279

Earlier quoted context omitted.

I don't really see it as prioritising your own browser. It's a system level feature and uses the system provided web engine. Microsoft doesn't let you swap out EdgeHTML or Trident for applications that use the native OS web frame. But apps shouldn't be forced to use that web frame is the issue the commission had and the DMA attempts to resolve.

Notably, Android does let users swap out the system webview. So clearly such a thing is possible.

Yes, but Google did that so they could update the WebView via the Play Store because OEMs were slow to distribute updates.

But the system still needed a WebView for when Play Services were not available, so they made a way to toggle between them.

Re: Epic says Apple will reinstate developer account

#652

Post by beeboobaa »

evilduck wrote: post #644
beeboobaa wrote: post #628

Earlier quoted context omitted.

Try reading my post again, maybe? The tooling is pretty janky because no one does this yet. No point to torture yourself with janky tooling when you only get to target android anyway...

Again, not answering a thing but a making up a claim you aren't willing or able to support. How is this supposed web development tooling jankiness attributable to Apple today? Feature detection is a solved problem. What tooling are you even referring to? You aren't even trying to support this with a concrete claim. This is nonsense and you know it. PWAs are the perfect scapegoat of infinite nebulous whining. The defi…

> Proper support on all platforms. No point working on PWAs that have janky tooling (reason: see previous sentence) when they're only going to work decently on Android devices anyway.

If you need it spelled out for you:

* WebUSB

* WebBLE

* WebSerial

* WebGL

* Many more standards Apple refuses to implement because it would let developers break free of their walled garden

Without being able to target apple devices why would I, or anyone, bother using these technologies and invest in their tooling? Just make a native android app with quality tooling that's been around for a decade and be done with it.

Re: Epic says Apple will reinstate developer account

#653

Post by evilduck »

beeboobaa wrote: post #652
evilduck wrote: post #644

Earlier quoted context omitted.

Again, not answering a thing but a making up a claim you aren't willing or able to support. How is this supposed web development tooling jankiness attributable to Apple today? Feature detection is a solved problem. What tooling are you even referring to? You aren't even trying to support this with a concrete claim. This is nonsense and you know it. PWAs are the perfect scapegoat of infinite nebulous whining. The defi…

> Proper support on all platforms. No point working on PWAs that have janky tooling (reason: see previous sentence) when they're only going to work decently on Android devices anyway. If you need it spelled out for you: * WebUSB * WebBLE * WebSerial * WebGL * Many more standards Apple refuses to implement because it would let developers break free of their walled garden Without being able to target apple devices why…

Right, I wanted you to spell it out because I was expecting you to write that exact sort of nonsense. Your first three examples aren't even web standards they're experimental features in Chrome that not even Firefox supports. The fourth actually is supported by Safari/iOS. What missing standards are stopping you from writing Progressive WEB Apps? Be exact please.

And.... even if you wanted to build a serial-port enabled "Works only in Chrome" PWA today (lol, we both know you're not) there's no tooling jankiness stopping you from doing so, checking for `if ("serial" in navigator) { ... }` requires no tooling at all it's just plain javascript, you'd just choose to show an error message for browsers like Safari and Firefox that don't support it.

I'm not convinced you're even arguing in good faith here. Well, I never was because PWA whiners never are, but you've proven you're not.

Post reply on HN