Hi David, I think it is a bit too early to start using Swift in WebKit, especially since the language is still evolving. Eventually, I think we should start using it, but I’d like for it to settle a bit before we do.
- Sam On Jul 28, 2014, at 12:47 PM, David Farler <[email protected]> wrote: > Hello all, > > I have the following bug to help build out support for layout tests in the > iOS Simulator. > > iOS Simulator LayoutTestRelay > https://bugs.webkit.org/show_bug.cgi?id=135269 > > I'd like to include this as a new tool written in Swift. > > Why I think it's fine in this case: > - This tool is specific to the iOS and OS X platforms > - Swift is a fully supported, albeit new, language starting in Xcode 6. > - Swift is probably the best way to get Objective-C bridging "for free" in > the long term > - Swift supports script-like "immediate mode" with good JIT-compiled > performance > - The tool's size and scope is sufficiently small with no complex or > WebKit-specific dependencies > > I understand that its freshness and continual evolution means that we won't > reviewer support relative to our C family languages. I would argue that it > will be difficult to subjectively tell when the time is "right", that a good > way to solve that is to start using the language itself, and take an > incremental approach to crafting the Swift story in WebKit. Using it for some > simple tools is a good place to start. > > The larger discussion of using Swift in larger AOT-compiled contexts but is > probably going to happen in this thread anyway, so let's have it: > > What of future use of Swift in WebKit? > > Regards, > David Farler > _______________________________________________ > webkit-dev mailing list > [email protected] > https://lists.webkit.org/mailman/listinfo/webkit-dev
_______________________________________________ webkit-dev mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-dev
