(no title)
ayberk
|
1 year ago
As a Google engineer, it's really saddening to see the Welchism completely taking over Google. There are more than enough examples showing focusing on bottomline to increase shareholder value doesn't work in the long run, but it's obvious the current leadership doesn't care.
_the_inflator|1 year ago
I re-read How Google Works, Engineering at Google, etc. Kind of ironically, YT delivered these fantastic talks from 2011:
Google I/O 2011: HTML5 versus Android: Apps or Web for Mobile Development? https://youtu.be/4f2Zky_YyyQ?si=rbKgYi7Rck-6y3qE
Or HTML5, CSS3, and DOM Performance, Breaking News at 1000ms with Patrick Hamann
This was and still is fantastic stuff.
The next step would be to drop the unofficial requirement that every manager be able to code. MBAs at Google: regression to the mean.
Old Google was inspirational; new Google seems to evolve into yet another drawing board MBA construct.
Narhem|1 year ago
Sure you could use a react based app with some of the compilers but it’s like opening another bag of worms.
fngjdflmdflg|1 year ago
ein0p|1 year ago
paxys|1 year ago
hnburnsy|1 year ago
ddalex|1 year ago
burtonator|1 year ago
dspillett|1 year ago
----
[1] this takes time: after _years_ of saying I'm going to I've finally started experimenting with using Kagi for search instead. It also takes _good_ alternatives, a paid option won't be seen as good by many.
fennecfoxy|1 year ago
At least Google's M.O. has mostly been to make stuff and then just throw it out into the open (with no support). Apple has been the opposite, ingesting the ideas and features of whole other companies without buying them, because they control their own little ecosystem.
Yes, developers can use basic/locked down UWB functionality in their apps, but no they cannot run it in the background constantly like Apple does for their airtags, essentially making it useless.
ranger_danger|1 year ago