3 ms·

Full quote: > Con: The Fuchsia Platform Source Tree has had negative implementation experience using Go. The system components the Fuchsia project has built in

by rob74 7y ago

Full quote: > Con: 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. I wonder if they had other negative experiences beside the higher resource usage? Because it's hardly surprising that a garbage-collected language should have higher resource usage than C++/Rust. They could have still supported it for app development however - but it seems they took a "there can only be one" approach and went for Dart instead.

deleted 7y ago
[deleted]
pjmlp 7y ago
Supporting Go for app development would mean having to design a generics free API. Also most likely why Android will never support Go officially.
- terminaljunkid 7y ago
  Generics Free, No exception handling, also hard to support to shared libraries. That's more cost than benefit.
  - jstimpfle 7y ago
    > also hard to support to shared libraries why?
    - deleted 7y ago
      [deleted]
    - thu2111 7y ago
      Go doesn't really have a standard/stable ABI. The way you include one module inside another is by doing what amounts to a big #include on the source code.