提供幾個數字做為參考，首先是文章提到的：
Ultimately, Slack was ripe for the taking. Entering 2020 it had lost around 40% of its value since it went public. Consider that after its most recent earnings report, the company lost 16% of its value, and before the Salesforce deal leaked, the company was worth only a few dollars per share more than its direct listing reference price. Toss in net losses of $147.6 million during the two quarters ending July 31, 2020, Slack’s uninspiring public valuation and its winding path to profitability and it was a sitting target for a takeover like this one. The only surprise here is the price.
Slack’s current valuation, according to both Yahoo and Google Finance, is just over $25 billion, which, given its very modest price change after-hours means that the market priced the company somewhat effectively. Slack is up around 48% from its valuation that preceded the deal becoming known.
而 2016 年有新聞說微軟將 Slack 視為價值高達 80 億美元的潛在收購目標。1
AWS 的思維一值是 scalability > consistency。
先前是 us region 維持最初的 eventually consistent，其他新的 region 支援 read-after-write consistent。
這次 upgrade 應該是除了 read-after-write，其他操作, e.g., list, ACL 也變成 strong consistent
還沒細看條文，感覺應該還有但書，要不然 "Amazon S3 delivers strong read-after-write consistency" 中間就不會有 "read-after-write"
聽到這個嚇一跳，S3 不是一直都是 strong 嗎？
看回應是說 us region 的一直都是 eventually consistent，其他比較新的 region 很早就是 strong 了。
我都用新加坡或日本所以一直都無感…
kotlin 1.3.x ~ 1.4.10 IDE plugin 有很嚴重的效能問題，遇到的快升級吧！
公司開發用的 mac 很慢，會放大這個 bug，compile 一個大檔要卡 30 秒，超級崩潰。
還好 1.4.20RC 之後就修好了。
The problem is that ARM architecture doesn't clock very high and has high leakage at high power levels (this is also conversely true, x86 is not very good at low power scenarios)
是這樣？ARM 頻率沒辦法撐高嗎？那之後的 M2, M3... 不就...