Hacker News new | past | comments | ask | show | jobs | submit login

Out of interest, why are people so confident in Google when it comes to Go, yet every other day there's articles about how Google can't be trusted in related to Dart/Flutter which are soon to be abandoned?



I don't really know anything about Dart or Flutter, but they're entirely separate teams within a huge organisation. It's entirely possible that one team does an excellent job, whereas the other doesn't. I keep repeating this: but "Google" is not a monolithic entity. People aren't "confident in Google", they're "confident in the people working on Go" (or not: you can decide that for yourself).


Because Go has massive traction both inside and outside of Google, whereas Dart/Flutter never got big traction.


Dart only found a real good use case fairly recently. Given its explosion in usage since then, I think it may very well be more popular that go in several years.


Curious- what is the use case?


I think they mean Flutter, and Darts truly cross platform abilities.


I don't trust Google.

I trust specs[1], multiple implementations[2], and how easy it is to bootstrap a compiler[3].

[1]: https://go.dev/ref/spec

[2]: https://gcc.gnu.org/onlinedocs/gccgo/ (even if feature parity isn't quite there yet)

[3]: Instead of requiring double-digits compilation steps that each take too long to be reasonable.


I get an early-UNIX / Bell-Labs vibe from the entire Go project. New Jersey all the way. The ecosystem is too sleek and practical to abandon. My 0.02€, ymmv.


>New Jersey all the way

New Jersey vs. what? I read about that phrase sometime earlier but forgot the rest of it. Is it vs. MIT / Stanford / West Coast / other? implying worse is better vs. other?

is it also related to neat vs. scruffy approaches in AI?

too much in tech to keep track of it all.

but asking out of interest.


Well, it's kinda the whole "Worse is Better" thang. Flee from complexity.

As opposed to the "MIT style".

Related: Featuritis vs. YAGNI.


At any point in recent history, I would have been pretty happy sticking with the last release of go for quite some time. Flutter always feels like it's the next release that's going to be the good one.


> Google can't be trusted in related to Dart/Flutter which are soon to be abandoned

source?


I'm not agreeing with that assessment but recently:

https://news.ycombinator.com/item?id=40997745

https://news.ycombinator.com/item?id=40184763

Among others. Again I'm not saying I agree, I'm just saying you don't see the same with Go.


Off the top of your head, name 3 projects/apps that use Dart/Flutter, now do the same for go.


There are probably more Flutter apps about than you’d think, and at least on Android you can look for yourself: https://x.com/kevmoo/status/1819112503722627286


If you cant name 3 projects/app that use Dart/Flutter that just shows your bias.

Can you name 3 apps/projects that use COBOL?

-- This is akin to asking, "Quick, name 3 books written in Persian. Huh, you cant name them? Must be a dead language"


> Can you name 3 apps/projects that use COBOL?

Does this imply that you see COBOL as having a trustworthy future, making it a great choice for a new greenfield application?


the part of your sentence before the comma is not fully related to the part after it.

iow, the first part does not imply the second part.

a lang could have a trustworthy future for maintenance of existing apps, like in terms of support from vendors, while not being a very good choice for greenfield applications, due to not having modern language features and libraries.

but there is so much cobol in critical infrastructure in the world that I don't think it is going away anytime soon. Google for some relevant threads on hn about it.

there is a good chance that some services critically important to you and your family rely on software written in COBOL running on mainframes. just like for everyone else in the developed world and some of the developing world.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: