Many conversations happening on #WhatsApp (WA) groups about new #WhatsAppPrivacyPolicy .
This thread has arguments to help ditch WA & move to https://t.co/En4fe9VxUN
Share," target="_blank">@signalapp:
https://t.co/En4fe9VxUN
Share, use, copy-paste, modify with understanding as you deem fit on any platform in whole or part
1/n

(1) Let’s get one thing straight right now;

I was a mod on r/watchpeopledie.

Ive taken part in uncovering evidence of p3d0’s to reveal to LEO.

I have seen some *dark* sh*t in my day.

Unless you are used to it; you will NOT be able to handle “seeing the truth”. I promise ➡️

Porting vanilla (minimal external API usage, no SIMD, no threading) C++ code to work in the browser with emscripten and WebAssembly is amazingly simple now. The Emscripten docs are excellent, but here are some things that could speed up the process of getting started:

1. Beware of code which does unaligned memory reads/writes (which "may be slow on some CPU architectures")
2. Test with -fsanitize=undefined -fsanitize=address
3. Link with "-s ALLOW_MEMORY_GROWTH=1" and "-s INITIAL_MEMORY=X", X is a multiple of 64k, allows the C++ heap to grow.

(I completely avoid unaligned memory reads/writes because when compiled to asm.js they "can fail silently".)

4. Link with "-s MALLOC=emmalloc" to reduce compiled size.
5. I usually test with -O1 because -O0 can take very long to load/execute.
6. For debugging link with -s DEMANGLE_SUPPORT=1 and -s ASSERTIONS=1

7. C++ printf() outputs to the Developer Console: Chrome Settings->More tools->Developer tools
8. If something crashes, try running in Firefox which may explain the error differently.
9. I use Web Server for Chrome for

~8yrs ago (Dec’12) I got a job @Google. Those were still early days of cloud. I joined GCP @<150M ARR & left @~4B (excld GSuite). Learned from some of the smartest ppl in tech. But we also got a LOT wrong that took yrs to fix. Much of it now public, but here’s my ring-side view👇

By 2008, Google had everything going for it w.r.t. Cloud and we should’ve been the market leaders, but we were either too early to market or too late. What did we do wrong? (1) bad timing (2) worse productization & (3) worst GTM.

We were 1st to “containers” (lxc) & container management (Borg) - since '03/04. But Docker took LXC, added cluster management, & launched 1st. Mesosphere launched DCOS. A lot of chairs were thrown around re: google losing this early battle, though K8 won the war, eventually 👏

We were 1st to “serverless” (AppEngine). GAE was our beachhead -- it was the biggest revenue source early on but the world wasn’t ready for serverless primitives. We also didn’t build auxiliary products fast enough. Clients that outgrew GAE wanted “building block” IaaS offerings.

1st to hadoop (map-reduce ‘04) but our hosted Hadoop launched in ‘15. AWS EMR was ~200M ARR by then. 1st to cloud storage (GFS ’03), but didn’t offer a filestore till ‘18! Customers were asking for it since 2014. Didn’t launch archival storage or direct interconnect till v. late.

Yoga employs more Americans than coal. But compare and contrast 1/2

and 2/2

I think many of us carry in our minds an image of the US economy that looks like this

when the reality is this

and this

Data drop! Some numbers, nuggets and trends for bowl season which I find interesting...

Miami has lost 9 of its last 10 bowl games and is 2-10 ATS in its last 12 bowl games. Oklahoma State has covered each of its last four bowl games, three coming as an underdog.

This is the first time since 2011 Texas is favored in a bowl game...

Wisconsin has won five of their last six bowl games with the only loss in that span a one-point loss to Oregon last year in the Rose Bowl. Each of Wake Forest’s last five bowl games have been one-possession games (6, 3, 3, 8, 6)...

Mike Leach coached teams are 1-9 ATS in their last ten bowl games (4-6 SU). Included in those ten games are four outright losses and a 1-7 ATS mark as a favorite. In the last five years, Leach’s teams have averaged 19.6 PPG in bowl games (28 is the high in that span)...