this post was submitted on 26 Jan 2024
250 points (97.0% liked)

Europe

8324 readers
1 users here now

News/Interesting Stories/Beautiful Pictures from Europe ๐Ÿ‡ช๐Ÿ‡บ

(Current banner: Thunder mountain, Germany, ๐Ÿ‡ฉ๐Ÿ‡ช ) Feel free to post submissions for banner pictures

Rules

(This list is obviously incomplete, but it will get expanded when necessary)

  1. Be nice to each other (e.g. No direct insults against each other);
  2. No racism, antisemitism, dehumanisation of minorities or glorification of National Socialism allowed;
  3. No posts linking to mis-information funded by foreign states or billionaires.

Also check out [email protected]

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 8 points 9 months ago* (last edited 9 months ago) (1 children)

only WebKit is truly optimized and safe for iPhone users

So that's why it interprets certain standards differently than all other engines. Must be the security. The amount of rendering errors I have to debug just for iOS is annoying. Especially, since you need a MacBook AND an iPhone to debug this bad engine properly, so either me or my employer needs to buy into their ecosystem.

[โ€“] [email protected] 4 points 9 months ago (1 children)

Especially, since you need a MacBook AND an iPhone to debug this bad engine properly

Do you? WebKit is open-source and other browsers use it too, GNOME Web (Epiphany) for example.

[โ€“] [email protected] 4 points 9 months ago* (last edited 9 months ago)

For some reason I thought the Safari engine was proprietary, but you're right, you totally can.

However, you need to have the specific Webkit version on your system that's also used on the iOS release where the bug is present. Which can be a real pain to manage and I imagine compiling this engine will take quite a while.

Still better than buying unnecessary, overpriced hardware, though! I will for sure check this out soon.