Y'all are watching Apple knife the web to death, one cut a day for a decade. We're way past a thousand cuts, and they sure had help from FB.
-
Show this thread
-
Replying to @slightlylate
While this Is ABSOLUTELY true, there are VERY few people working on WebKit full time .It’s important that outside companies contribute to WebKit either directly or through a company like
@igalia .Apple consistently treats Safari as its unwanted child Cc@briankardell1 reply 0 retweets 3 likes -
Replying to @eisaksen @slightlylate and
Why would anyone do that when
@Apple has the final say what goes into their browser/device?1 reply 0 retweets 1 like -
So many reasons! First tho, clarification: In practice the owners of each engine's codebase have the final say in what goes into them. Each of them has many contributors who aren't the maintainers company.
@igalia is a top contributor to all (see https://bkardell.com/blog/2019-Wrap.html …)1 reply 0 retweets 3 likes -
Replying to @briankardell @brgrz and
Maintaining browser diversity alone is a very good reason. We can disagree on specific leanings from history but I don't think that anyone disagrees that one engine would be too few - lots of googlers said this, I don't think there is disagreement
1 reply 0 retweets 6 likes -
Replying to @briankardell @brgrz and
Browser engines are so tremendously complicated that we only get them through evolution of their past selves. Every browser can trace its rendering engine lineage back to at least the late 90s, and they take years to adapt
2 replies 0 retweets 7 likes -
Replying to @briankardell @brgrz and
Any thoughts on this apparent newcomer? https://www.quirksmode.org/blog/archives/2020/01/new_browser_on.html …
1 reply 0 retweets 0 likes -
I mean, obviously I do since we are the maintainers of the official embedded WebKit fork on http://webkit.org/downloads but - too complex for twitter :) Expect more from me this year on the topic. "It's not there yet" is in the interview itself.
1 reply 0 retweets 4 likes -
Replying to @briankardell @simonstl and
You can also point to the existing reworks as evidence of the invisible complexity/size of the task. Mozilla servo stuff, Google's LayoutNG... giant, multi-year tasks even for big teams
1 reply 0 retweets 3 likes -
Replying to @briankardell @simonstl and
Webkit maintains potential viability for sure. That's no replacement for competition, tho. The price of a better web is now the price of a new phone. Netscape never managed to charge that much!
2 replies 0 retweets 4 likes
These #s only hint at the world of pain webdevs face on Safari:
https://web-confluence.appspot.com/
-
-
Replying to @slightlylate @briankardell and
The slow, hard, painful remedy that we used to have (switching to a better browser) is now toothless on iOS. FruitCo put sand in the tank; stepping on the gas doesn't work any more. Deadweight losses everywhere.
0 replies 1 retweet 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.