Re:Capitalism the Apple Way vs. Capitalism the Google Way (2...
by webwielder2 on Monday January 07, 2019 @11:42PM
(#18853205)
Google has indeed been much more successful at shipping vaporware.
[ Parent
| on HN ]
Re:Capitalism the Apple Way vs. Capitalism the Google Way (2...
by dnautics on Tuesday January 08, 2019 @04:07AM
(#18854294)
I wouldn't call google's products vaporware. There are definitely five that I have used. Search, Gmail, Maps, Youtube, and Android. I barely use google search anymore (DDG is my major driver) - I'm not too content with Gmail anymore, and my youtube use has gone down since their ad strategy has changed.
Probably Maps and Android are the two products they do that I would consider 'quality'.
I'm not happy with Tensorflow, Golang, or Kubernetes.
Re:Capitalism the Apple Way vs. Capitalism the Google Way (2...
by samatman on Tuesday January 08, 2019 @06:48AM
(#18854886)
In the last twenty years, Google/Alphabet has killed more products than Apple has launched.
In a very real sense, Alphabet has an r selected corporate strategy, while Apple is K selected[0]
Re:Capitalism the Apple Way vs. Capitalism the Google Way (2...
by baldfat on Tuesday January 08, 2019 @09:32AM
(#18855705)
> my youtube use has gone down since their ad strategy has changed.
I pay for Google Music and YouTube for $16 for 5 family members and me. I haven't seen a YouTube ad for years. Best use of my money every month.
Re:Capitalism the Apple Way vs. Capitalism the Google Way (2...
by avinium on Tuesday January 08, 2019 @05:26AM
(#18854597)
Tensorflow, I can understand - I imagine the rampant popularity of pytorch shows we're not alone.
What's your issue with Golang though?
Re:Capitalism the Apple Way vs. Capitalism the Google Way (2...
by dnautics on Wednesday January 09, 2019 @01:58AM
(#18862859)
There was an article about how golang takes a very classist attitude... There are programmers who use go, that are the peons, and the programmers who write go, who are anointed.. like hashmaps breaking the typesystem.
It feels like a lot of the things that happen like if err != nil are code smell. I wrote a cli in go and wouldn't mind it again but I program in elixir now and the emphasis on developer joy is refreshing (but it makes wise choices, e.g limiting the scope of macros to lexical)