Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
Software Google Open Source Operating Systems Programming Apple Linux

Google Is Working On Fuchsia OS Support For Apple's Swift Programming Language (androidpolice.com) 54

An anonymous reader shares a report from Android Police: Google's in-development operating system, named "Fuchsia," first appeared over a year ago. It's quite different from Android and Chrome OS, as it runs on top of the real-time "Magenta" kernel instead of Linux. According to recent code commits, Google is working on Fuchsia OS support for the Swift programming language. If you're not familiar with it, Swift is a programming language developed by Apple, which can be used to create iOS/macOS/tvOS/watchOS applications (it can also compile to Linux). Apple calls it "Objective-C without the C," and on the company's own platforms, it can be mixed with existing C/Objective-C/C++ code (similar to how apps on Android can use both Kotlin and Java in the same codebase). We already know that Fuchsia will support apps written in Dart, a C-like language developed by Google, but it looks like Swift could also be supported. On Swift's GitHub repository, a pull request was created by a Google employee that adds Fuchsia OS support to the compiler. At the time of writing, there are discussions about splitting it into several smaller pull requests to make reviewing the code changes easier.
This discussion has been archived. No new comments can be posted.

Google Is Working On Fuchsia OS Support For Apple's Swift Programming Language

Comments Filter:
  • Don't you just need to update a language compiler to support the OS's system call structure for the language to be supported?
    Or are they providing a runtime library to provide the appleOS API's and calling conventions so Apple's compiler/IDE can be used without modification?

    • Re: (Score:3, Informative)

      by Anonymous Coward

      "On Swift's GitHub repository, a pull request was created by a Google employee that adds Fuchsia OS support to the compiler."

      • My guesses are:

        A) He only read the headline, and improperly parsed it as Google working on supporting Swift within Fuchsia OS.

        B) He's not familiar with modern semi-open development fads and he doesn't understand that a "pull request" means Google is requesting that Apple pull Google's changes (supporting Fuchsia OS) into Apple's source code for the Swift compiler.

        C) covfefe

    • Don't you just need to update a language compiler to support the OS's system call structure for the language to be supported?

      If the language is any good, you just replace the library you use for system calls..

      OTOH, If I use any of these newfangled languages, and I need to (say) embed Postgresql, or use existing statistical libraries like TSP, how good is the support for that? (Like the equivalent of PHP-pgsql for PHP? is the support supported? (ie updated to track changes in the underlying target code/sy

      • And for the guy who asked about Smalltalk - the Xerox machine which first used mouse and Icons was a hardware Smalltalk machine.

        No it wasn't. It was a Xerox Alto. The Alto was a microcoded 16-bit system, and each language that was developed for it wrote its own microcode. The Alto processor was designed to execute bytecode, with each one being implemented by running the microcode provided for that index. Smalltalk bytecode was just one of the microcode implementations, the Algol virtual machine (for example) provided a different bytecode. This mechanism went out of fashion when people became interested in running programs writt

  • To those who dont remember, dart was google's attempt to replace javascript.

  • by sconeu ( 64226 ) on Monday November 20, 2017 @07:37PM (#55591553) Homepage Journal

    So, SmallTalk, then?

    • by kwerle ( 39371 ) <kurt@CircleW.org> on Monday November 20, 2017 @08:01PM (#55591675) Homepage Journal

      Absolutely not. Way closer to C++ or maybe C# in that it is all about compile time. Very little about the language feels dynamic. Nearly nothing.

      • And this is why I don't really see the point of Swift. If you want to avoid run-time overhead from Objective-C but want to maintain compatibility with Objective-C libraries, there's already a language that lets you do this: Objective-C++. You can use C++ templates for compile-time specialisation and Objective-C for late binding. Objective-C ARC now makes this combination cleaner, because Objective-C object pointers are non-POD types in C++ and all of the memory management interoperates cleanly. It's als

        • by kwerle ( 39371 )

          Yeah, I'm not a big fan either. I keep hoping they'll add the dynamic part - but it sure doesn't seem like that's gonna happen.

          It makes me a little sad - I wanted to love swift. But I'm coding in ruby - which I think of as the ObjC of scripting languages. And I freakin' love it.

    • Smalltalk would have been a much better choice than Swift, but oh well, you can't have everything.
  • by Anonymous Coward on Monday November 20, 2017 @07:39PM (#55591571)

    I ran a one-line script to print "Hello world" and it uploaded 20Mb of data to Google's servers. It's almost ready for release.

  • by jfdavis668 ( 1414919 ) on Monday November 20, 2017 @07:44PM (#55591591)
    I think mauve has the most RAM.
  • by Anonymous Coward

    Linux became popular because it's a free OS to embed on devices. But with Apple devices running iOS (ie. not Linux) and Google moving away from Linux for its devices and all those that depend on it, the beleaguered operating system is sure to severely decline in popularity.

    Linux, a flash in the pan!

    • by Anonymous Coward

      This is a very real problem. Linux is losing the developer mindshare that it once had. Lots of developers are using macOS these days, and like you point out they aren't targeting Linux. Even if they're working on Android apps, Linux is so deeply hidden that it may as well not even be there. The BSDs are seeing a resurgence for server use, and Linux desktop use has withered with the failures of systemd and Gnome 3. I think that Linux may have plateaued, and now we are seeing the beginning of a decline.

      • by Kjella ( 173770 )

        No idea why this troll is at +3, maybe the /. echo chamber have heard this crap so many times they believe it. Read the headlines for Market Share Analysis: Server Operating Systems, Worldwide, 2016 [gartner.com] with highlights like "Linux (Server) Is the Fastest-Growing OS Segment" and "Red Hat Became the Second-Largest OS Vendor Through Linux (Server) Growth and Geographical Expansion". The major players are Windows, z/OS, HP-UX and Solaris with Canonical getting a honorable mention. BSD is not on anybody's radar exce

        • Linux is great for servers, but it doesn't make a whole lot of sense for consumer devices.

          The kernel is just too bloated to be practical for low power, low memory devices like mobile, and the API changes so much that drivers are always broken in new versions, requiring an update. Updates to drivers are expensive due to all of the certification required, which is a big reason most OEM's don't upgrade older Android phones, Google included. It also contributes to IoT's security problems.

          For desktop, Linux is t

  • by Misagon ( 1135 ) on Tuesday November 21, 2017 @04:04AM (#55593385)

    BTW, the microkernel at the bottom of Fuchsia has changed name from Magenta to Zircon.
    Maybe because there's a Magenta Linux... I dunno.

    Zircon has security based on capabilities (which it calls "handles", rightly so IMHO) for pretty much everything. This could support sandboxing of new sub-processes that you own, but it lacks revocation of rights from running processes that would be used as services -- which I find to be a serious omission.
    IPC is very much like Unix domain sockets: with streams and queued asynchronous message passing... which means that it is never going to be faster than Mach ... and Linux is demonstrably faster than Mach. seL4 would have been a better foundation IMHO.

  • Google is having a problem with Java and Oracle. Replacing it with a language that has a large user base, is mobile-first, easy to develop with and can already have IDE support (https://www.jetbrains.com/objc/features/swift.html) in their current Android Studio seems like a good idea.

    Google is also having a problem with the Linux kernel. It's unwieldy and not mobile-first. Building their own kernel designed specifically for mobile would make the entire system more CPU and battery efficient.

    All around,

All laws are simulations of reality. -- John C. Lilly

Working...