News for hackers. Stuff that matters.
Re:Fuchsia Programming Language Policy by Thaxll on Monday February 24, 2020 @08:42PM (#22410269)
They did not have a negative experience, this is not what's written.
Re:Fuchsia Programming Language Policy by jsnell on Monday February 24, 2020 @08:46PM (#22410290)
What do you mean? It's a direct quote from the page.
Re:Fuchsia Programming Language Policy by terminaljunkid on Tuesday February 25, 2020 @12:33AM (#22411146)
Fuchsia is meant to be used in variety of contexts like IoT [sic], and embedded stuff, Many time Go doesn't play well in such areas.

People coming from language like C++ and senior enough to write OSes may be startled how inexpressive Go is.

Re:Fuchsia Programming Language Policy by pjmlp on Tuesday February 25, 2020 @03:34AM (#22411691)
Even Java that started as a blue collar language, or modern Basic dialects that started as introduction to programming, are more expressive than Go will ever be.
Re:Fuchsia Programming Language Policy by Thaxll on Monday February 24, 2020 @08:53PM (#22410315)
On the same line they mention memory / cpu usage, I don't read it as we had bad experience using the language but more than Go doesn't suit well xyz because of memory usage.
Re:Fuchsia Programming Language Policy by pengaru on Monday February 24, 2020 @09:39PM (#22410499)
Hence the word implementation accompanying experience, which was not omitted in the citation you're responding to.
Re:Fuchsia Programming Language Policy by Cyph0n on Monday February 24, 2020 @09:41PM (#22410506)
Why can’t it be both?