Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.social/users/lisamelton/statuses/112655046670477252">Lisa Melton (lisamelton@mastodon.social)'s status on Saturday, 22-Jun-2024 04:38:01 JST</a><a href="https://mastodon.social/@lisamelton" title="lisamelton@mastodon.social"><img src="https://gnusocial.jp/avatar/139236-48-20230622184532.webp" width="48" height="48" alt="Lisa Melton" style="position: absolute; left: 0; top: 0;">Lisa Melton</a><div><a href="https://todon.eu/@ljrk/112655013406258270" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/78759" title="kdawson@tldr.nettime.org">Keith Dawson</a></li><li><a href="https://gnusocial.jp/user/105402" title="ljrk@todon.eu">lj·rk</a></li></ul></div></section><article><p><a href="https://todon.eu/@ljrk">@ljrk</a> I certainly agree that moving to Swift would further isolate the development of WebKit.</p><p>And, yes, if there are still Objective-C components in the Safari UI, those could certainly be rewritten in Swift.</p><p>But the existing codebase of WebKit is already using a tight subset of C++. And it has strict memory management and error handling systems. My old gang has been working on this now for over 20 years and they kinda have it tuned by now. 😀</p><p><a href="https://curmudgeon.cafe/@fahrni">@fahrni</a> <a href="https://tldr.nettime.org/@kdawson">@kdawson</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3274798#notice-6456636">In conversation</a><time datetime="2024-06-22T04:38:01+09:00" title="Saturday, 22-Jun-2024 04:38:01 JST">about a year ago</time> <span>from <span><a href="https://mastodon.social/@lisamelton/112655046670477252" rel="external" title="Sent from mastodon.social via ActivityPub">mastodon.social</a></span></span><a href="https://mastodon.social/@lisamelton/112655046670477252">permalink</a></footer></blockquote>

Corresponding Notice

Embed this notice
Lisa Melton (lisamelton@mastodon.social)'s status on Saturday, 22-Jun-2024 04:38:01 JSTLisa Melton
in reply to
@ljrk I certainly agree that moving to Swift would further isolate the development of WebKit.
And, yes, if there are still Objective-C components in the Safari UI, those could certainly be rewritten in Swift.
But the existing codebase of WebKit is already using a tight subset of C++. And it has strict memory management and error handling systems. My old gang has been working on this now for over 20 years and they kinda have it tuned by now. 😀
@fahrni @kdawson
In conversationabout a year ago from mastodon.socialpermalink

Public

Embed Notice

HTML Code

Corresponding Notice