Actually, you should read the whole note -- it's fun. Half of the languages are bad because of memory leaks, the other half are bad because of having GC; half are bad because of difficult asynchronism, the other half are bad because of having a runtime. etc.
It reads like an imperiously-worded tautology about safety/power/convenience coming at a cost. On Tue, Feb 25, 2020 at 9:51 AM Mohamed Yousif <mmbu...@gmail.com> wrote: > It seems they are betting high on Dart/flutter and their front end is > already written with flutter. The assessment seems to be pretty much the > same as for Dart. > > Dart won with the ui side, while go was competing with C. > > On Tue, 25 Feb 2020 at 7:22 PM, Jon Conradt <j...@theconradts.com> wrote: > >> The Fuchsia Programming Language Policy >> <https://fuchsia.googlesource.com/fuchsia/+/refs/heads/master/docs/project/policy/programming_languages.md#Go> >> gives >> some insight into the experience the Fuchsia team has had with Go, and it >> doesn't sound good. >> >> "The Fuchsia Platform Source Tree has had negative implementation >> experience using Go. The system components the Fuchsia project has built in >> Go have used more memory and kernel resources than their counterparts (or >> replacements) the Fuchsia project has built using C++ or Rust." >> >> >> The Fuchsia Platform Source tree is defined as "The *Fuchsia Platform >> Source Tree* is the source code hosted on fuchsia.googlesource.com." >> >> Their conclusion, and each language has some issues is pretty severe. >> >> - Go is not approved, with the following exceptions: >> - *netstack*. Migrating netstack to another language would require >> a significant investment. In the fullness of time, we should migrate >> netstack to an approved language. >> - All other uses of Go in Fuchsia for production software on the >> target device must be migrated to an approved language. >> >> That's a shame. I was hoping that Fuchsia would provide a way for Go to >> have a nice GUI. >> >> Two of the issues listed as cons include the toolchain producing 'large >> binaries' and the related issue of their being a 'substantial runtime.' It >> seems to me that both of these issues can be addressed through some of the >> techniques used to build tiny Docker images from Go, but I suspect they >> would like to have a much simpler route, e.g. a go build flag. >> >> Jon >> >> -- >> You received this message because you are subscribed to the Google Groups >> "golang-nuts" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to golang-nuts+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/golang-nuts/7778a387-f1f5-4ed0-8453-5b811bac4a6d%40googlegroups.com >> <https://groups.google.com/d/msgid/golang-nuts/7778a387-f1f5-4ed0-8453-5b811bac4a6d%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/CAHrL7wHqJnDnEVe4%3D--%3DcSW9oA-eYxcbKagESdZHgSkrdLutpA%40mail.gmail.com > <https://groups.google.com/d/msgid/golang-nuts/CAHrL7wHqJnDnEVe4%3D--%3DcSW9oA-eYxcbKagESdZHgSkrdLutpA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- *Michael T. jonesmichael.jo...@gmail.com <michael.jo...@gmail.com>* -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CALoEmQx0mMnuKQHOrp9ptxM1iN5y9%2B3rXYDZ4TaOYK%3DfXmq4Sg%40mail.gmail.com.
