Podcasts about L2

9月15日UTC时间06:46:46，在以太坊区块高度15,537,393处，最后一个POW区块被挖出，POS信标链接管了链上共识，一次空中换发动机式的升级后，以太坊今年最重要的升级完成。虽然GAS费，出快速度基本不变，但在以太坊64层分片后，我们或将迎来远超现有体系的支付技术。 更近的未来，聚光灯的焦点照耀在了以太坊L2层，OP Rollup VS ZK Rollup的竞争还未全面展开，L3的概念却再次被Vitalik提出，让协议和应用之间的界限，变得更加模糊。 主播｜阿伟 Awaei ，Twitter：@web3awaei (https://twitter.com/web3awaei) 嘉宾｜周载南Victor，以太坊核心开发者 Twitter：@ZainanZhou (https://twitter.com/ZainanZhou) 【你将听到】 The Merge 01:04 超预期，The Merge异常顺利 02:28 什么是难度炸弹？ 03:29 后续扩容计划：Surge, Verge, Purge和Splurge 05:09 误区一：The Merge后，出快速度和GAS费变化不大 06:24 以太坊社区最新关注点：分片方案和提前释放质押ETH 08:38 64层分片后或超越Visa形成全新支付方式 11:08 EIP-1559产生了以ETH为单位的价值回流 L2，L3 13:44 分片+Rollup方案的合理性 17:04 L2解决的是什么问题？ 20:55 OP Rollup VS ZK Rollup 25:30 误区二：L2的可用性和POS转换无关 28:17 L3不是新概念，能否实现待验证 29:59 应用和协议的界限变得模糊 【相关阅读】 * 一文了解以太坊的 Merge、Surge、Verge、Purge 和 Splurge (https://www.techflowpost.com/article/1154) * Vitalik：什么样的 Layer3 才有意义？ (https://www.chaincatcher.com/article/2079734) 【术语解释】 Rollup：打包L2层交易，集中记录在L1层的以太坊扩容方案 Evm：Ethereum Virtual Machine 以太坊虚拟机 难度炸弹 Terminal Total Difficulty （TTD） 分片 Sharding Consensus Layer 共识层 Execution Layer 执行层 OP Rollup 代表项目：Arbitrum (https://arbitrum.io/) 和 Optimism (https://www.optimism.io) ZK Rollup 代表项目：Starkware (https://starkware.co) 和 zkSync (https://zksync.io) Validator Committee：验证者委员会 Block Producer：区块创建者 Bid：出价 Balance：余额 Settle：设定好 Diff：差额 Proofer：证明者 Pending：等待处理 【BGM】 Mumbai — Ooyy Aquafine — Lupus Nocte 【后期】 刘媚 【在这里找到我们】 中国用户：苹果播客｜小宇宙 海外用户：Apple Podcast｜Google Podcast｜Amazon Music｜Spotify Twitter：@Web3_101 (https://twitter.com/Web3_101) 【嘉宾言论仅代表个人，本期节目不构成任何投资建议哦】

※ 投稿邮箱：418150505@qq.com※ 本文章发布于订阅号：百车全说，订阅号阅读更加方便，欢迎关注前30分钟聊全新领克03，后半部分聊一位专车司机的故事。说起十多万的A级轿车，首先你会想起谁？朗逸、轩逸？还是卡罗拉、雷凌和速腾、宝来？这几台车常年都是霸榜，尤其是轩逸，新老加在一块一年能卖近50万台（2021年销量493868台）。不过其实这也不算什么，因为隔壁的的丰田卡罗拉和雷凌加一块也有45万台，更别说大众了，速腾+宝来+朗逸这三款加一起，一年直奔80万台去了。除了这一波水桶车型之外，还有几款运动型轿车，虽然销量数据没有那么夸张，但是粉丝的忠诚度非常的夸张。你不让他买，他就茶不思饭不想，食之无味，夜不能寐，整天魂不守舍，就跟失恋了一般。比如马自达昂克赛拉、本田思域和型格。这三台日系车在和对手比，空间差不多的情况下，增加了运动型设计，以及所谓的操控性，就让准车主们神魂颠倒。尤其是昂克赛拉这款车，不买的人觉得它动力很一般，光吼不走，价格不仅贵，还没什么优惠。但是买它的人觉得，这就是品位，恨不得马路上就自己一个人开才好，小众就意味着脱离群众，小众就意味着与众不同，花小钱装大x，这种感觉别提多爽。而且，马自达的AT变速箱反应真的快，转向也很精准，确实是在平民车型中玩出了小跑的感觉，人马合一的说法真不是空穴来风，的确有两把刷子。思域和型格也是同样的道理，本田的L15系列发动机从中大型suv，用到紧凑级轿车，稳定性好，性能和油耗平衡的也很好，CVT变速箱虽然有些拖后腿，但是比起同级其他车型的CVT，这已经算是CVT SPORT版本了，再加上JDM的传说，本田标就可以叠加BUFF加成，所以思域一直是同级运动家轿的标杆之一。在10-15万级轿车领域，有这么多座大山压在前头，换做是你，你还愿意继续挑战他们吗？还是放弃这块市场，赶紧造几台国人喜欢的SUV，多赚些钱？实际上，大部分厂家选择的是后者，但今天我们要聊的品牌领克，选择的是前者。管你几座大山压在前头，改炸掉的炸掉，炸不掉的挖隧道，你50万一年的销量，还是80万一年都与我无关。老子就玩自己的文化，打造自己的调性，拥有自己的粉丝。从一开始领克打造03车型的时候，我就感觉这股劲头是挺足的。后来跑WTCR拿了几次年度总冠军，我感觉这个品牌，或者说领克03这款车基本算是成了。要知道，现如今绝大部分国产轿车，还在用性价比抢市场，领克现在已经不谈性价比的问题了，我就卖得比你贵，怎么滴？动力比你好，内饰比你好，设计比你新颖，空间也不差，怎么就不能比合资车贵？当然领克有这个底气，一方面背后靠的是沃尔沃，另一方面也是因为有吉利兜底。比如吉利星瑞，A+级的尺寸，A级车的价格，全系都是2.0T，卖的比思域，速腾便宜，能接受吧？还有比亚迪秦PLUS，混动和纯电卖的都挺不错，主要原因也是咱们自己掌握核心科技，比亚迪在新能源领域算是成了，合资的纯电和插混都是短板，目前这个市场还是牢牢地掌握在国产品牌手里，特别是紧凑级新能源车市场，比亚迪赚的是盘满钵满。其实我们今天要聊的是领克03系列。其实03和03+车型一定程度上抢走了很多思域和昂克赛拉的用户。思域也就是最近2年才开始降价，昂克赛拉也是最近两年下调了官方售价。我不是推荐大家一定要买领克03，但是我们要知道，至少它的存在让合资不再那么嚣张。前几天，新款领克03上市，其实争议也挺大。有人说4年了，应该是换代车型吧，外观、内饰、动力、配置都有变化。也有人说，这最多算是中期改款车型，平台根本没变，轴距还是老样子。其实在我看来，这次的变化，有点像是高尔夫GTI，从MK7换代到MK8，外观深度整容，内饰脱胎换骨，车机全面升级。唯一跟GTI不太一样的地方，就是03这次的动力整体拔高很多。那么，领克03新款和老款究竟差别有多大？新款定价算不算贵？哪个配置更值得推荐？三缸真的退市了吗？这期节目，咱们一起来好好聊聊。领克03新老款有什么差别？新款03整体变化还是比较明显地，尤其是外观和内饰。在外观上，新款03的进气格栅变大了很多，而且呈梯形。旁边还有黑色的条纹做点缀，有点像动物的獠牙，所以03车头显然是变得更凶了。上代03很多车友反馈有个小问题，那就是车灯不是很亮。虽然是LED前大灯，但是没有透镜，属于灯碗反射的结构，所以远光灯跟没有一样，尤其是在下雨天的夜晚，整体照明亮度达不到车友们的预期，毕竟买03的车主大部分还是比较懂车的，对细枝末节的要求都比较高。当然，也可能是花了合资的钱买个国产车，要求自然更高了一些。所以新款在前大灯上提升了不少，全新的LED矩阵大灯，整体亮度升了三级，中心亮度进一步提升超30%，照明距离可以到170米以上。它拥有48矩阵光照分区，能够实现来车避让、跟随避让、转向随动等多种功能。车侧部分新款03基本没变，除了轮圈的样式。有245/35/R19锻造式轮圈可选，造型也是领克03+同款，轮胎配的也是偏性能的马牌MC6。从这一点上看，算是把性能车外形下放了，有点类似奔驰C加了AMG运动套件的感觉。车尾部分变化也很大，新款虽然是贯穿式尾灯，但是每颗灯珠都是竖条状的，点亮还有动态效果，应该能吸引不少年轻用户，毕竟合资车上没有。不过尾部造型跟老款比，实际上就相当于把尾灯拉长，然后把牌照框放在了保险杠上。再加上一个造型夸张的尾部扩散器，即便是普通版的03看起来也确实要比老款运动很多。内饰部分的变化也是非常大的，换装全新样式的平底方向盘，更大尺寸的全液晶仪表盘，12.8英寸智能随动滑移屏取代了老款03的内嵌式屏幕，支持上下角度调节，这样带来的好处就是，调节到最高位置方便乘客观看，调节到最低位置，不遮挡视线。还有中控的空调出风口位置和样式都进行了改动，副驾驶处出风口采用贯穿式设计。电子档把也更新了造型，前方设计有两个手机卡槽，其中一个带有无线充电功能；中控台下方位置做了掏空处理。当然，大部分等待新款03的车主，关注可能并不是这些变化，而是车机换“芯”没有？新款03和极氪001一样，都用上了高通骁龙8155芯片。之前我们在试驾体验的时候不管是导航还是语音控制，比老款确实好用太多了，我看有些媒体说的还比较含蓄，可能是要照顾老车主的情绪，怕老款车主哭晕在厕所里。新车搭载的12.3英寸的液晶仪表，分辨率和清晰度也提高了不少。总结来讲，新款领克03的外观和内饰变化，有点让我感觉开始“极氪化”，我在想，今后的燃油车与电动车的边界也许会越来越模糊，我们可能很难再从外观判断出哪款是燃油，哪款是电动了。新款领克03还配备了Lynk Co-Pilot智能辅助驾驶系统，该系统中使用了12颗超声波雷达+5颗毫米波雷达+4颗高清环视摄像头+1个前视高精摄像头，并可实现多达25项智能驾驶辅助功能。从我们小谢同学的试驾体验上来看，领克的这台智能驾驶辅助系统，算法还是比较严谨的，跟车距离最小的时候，距离前车还是比较远，主动刹车介入的比较柔和，没有太突兀的感觉。开启智能驾驶之后，明显能够感觉到自动修正方向的力矩还是挺大的，如果你不打转向灯强行变道的话，会感觉有股劲跟你对着干。不像日系的智能驾驶辅助，你只要稍微动一下方向盘，智能驾驶辅助就解除了，生怕多干一秒的活。在外观尺寸上，长宽高分别增加了27mm，3mm，12mm，轴距没变。所以理论上，新款领克03的内部空间并没有什么变化。而在动力上，新款领克03有了很大的变化。首先是普通版本取消了之前的三缸1.5T，除混动以外，燃油版车型全系都是2.0T的T5发动机总成。普通版的提升最为明显，以前2.0T的领克03是190马力，300牛米，现在升级成了254马力，350牛米，搭配7速湿式双离合，百公里加速也从之前的7.4秒变成了6.9秒。账面数据上新款03已经可以跟高尔夫GTI打个平手了。所以很显然，领克是把上一代03+的发动机用在了普通版本的03上面了，那么问题来了，新款03+用什么？答案是新款03+和03+ CYAN用的是T5 EVO发动机，最大马力比T5多了11匹，变成了265匹，最大扭矩380牛米。再加上博格华纳的第六代四驱系统，百公里加速5.7秒。不出意外，价格也会调整不少。熟悉领克03+的朋友都知道，03+的变速箱和普通的03有所不同，不是双离合，而是8AT。但是在实际在动态加速上，新款03普通版本一点都不比它的大哥03+和03+CYAN慢。昨天我们的编辑小谢同学刚参加完新款03试驾会，试驾会上既有03也有03+和03+ CYAN。在红绿灯路口，小谢开着03，隔壁的媒体开着03+CYAN，都是地板油出去，03甚至没有丝毫落后的趋势。也就是说，普通的新款03和03+CYAN在动态加速上，普通用户甚至不会感觉到明显区别。所以要我看，新款2.0T的普通版03在动力上的提升真的很大，而且还可以花5000元选装19英寸的轮圈和运动排气，选装完后开起来的感受基本就和03+差不多了。很明显，厂家这是要放大领克03普通版的优势，想吸引更多年轻客户，这是要放量占有市场的节奏。而在底盘方面，新款03基本没变。还是前麦弗逊，后E型多连杆悬架，前后桥都配有防倾杆。底盘硬朗，路感清晰，变速箱响应直接。所以从运动角度看，新款03普通版2.0T的性价比，或者说动力和操控比老款，显然是提高了很多。甚至让我觉得新款03+的价格还真不好定，定高了肯定没人买，定低了又失去了03+的意义。很多人说新款03的三缸取消了吗？其实准确地说不是取消了，而是放到混动版本上去用了。新款03除了03/03+和03+ CYAN外，还推出了03EM-F车型，也就是吉利星越L雷神混动上的那套动力总成，三缸1.5T发动机再加3挡DHT Pro，确实比较省油。不过它和星越L雷神一样，上的是蓝牌。目前吉利的三缸机，基本都用在混动车型上，之前我在节目里也提到过，这款三缸机实际上技术含量不低，而且是针对混动系统优化过的，所以大家可以看看易车网的国产混动车型大横评。虽然听起来三缸混动让很多人望而却步，但实际用起来，你只会说真香。我和两名摄影师开着星越L雷神混动，自驾从呼和浩特到响沙湾，开了几天下来，摄影师一直纳闷，这确定是三缸吗？不会给错车了吧？新款03的定价贵不贵？新款03目前售价15.48-17.68万，混动版15.78-16.98万。要说这个定价贵不贵，还得从两个角度分析。首先，燃油版这个价格对比之前的2.0T的领克03，其实真的一点都不贵，不仅外观内饰有了很大的变化，动力也从之前的T4升级到了T5，车机芯片还做了升级，但是价格只贵了4000元。而如果你对比新老03的入门价格，你肯定会觉得贵了好多。毕竟新款入门版的03定价15.48万，对比之前三缸03的入门价格只有13.48万，足足贵了两万。加上保险和购置税，新款最低配的03落地也要17万。要知道，15-6万的裸车价已经能买到顶配的本田思域和型格了，而国产2.0T的UNI-V顶配也不过才14万。别忘了之前三缸的03一直都有优惠，现如今新款领克03刚上市，如果没有优惠，实际新老款入门版的差价要去到3万上下了。所以，对于原本准备买老款2.0T版本03的客户，他们可能觉得新款值得入手。但是对于准备买老款1.5T版本，还期待有更大优惠的客户，这次新款03的售价，肯定是会让他们失望了。总结来讲，不能说贵了，只能说是入门门槛变高了。其实最近很火的奔驰全新AMG C63也是同样的道理，在有些人眼里，AMG C63是100万以内，能买到的最便宜的V8性能车。但也有人觉得，100万买一台奔驰C，是不是疯了？而现如今，AMG C63新款变成了2.0T+电机。难道说为了环保，AMG车型今后不搭载V8发动机了吗？其实不是，而是奔驰把V8的门槛提高了。100万以内买V8发动机的性能车已经成为了历史，2-3百万其实还是可以买到的。就比如AMG G63，你看他们敢不敢把300万的AMG G63变成2.0T+电机？敢不敢把200万的GT63和AMG GT变成2.0T四缸？打死他们也不敢，真要这么做，AMG就彻底没有了信仰，没有了灵魂，以后谁还买？所以并不是C63没有了灵魂，还是奔驰让你玩V8性能车的门槛变高了。十年前，只要100万就能买到V8 AMG，但是十年后，你得花200万甚至300万，你说是不是这么个道理？不过大家并不用太操心，我猜测03大概率后期还会推出更便宜的1.5T版本。为什么不一开始就推出呢？因为领克这里不止一台车在等着换四缸机，比如06，既然吉利用上了1.5T四缸，那么在领克这里也没什么理由会缺席，估计也用不了多久就会相继推出。如果你真的想要便宜，可能之后的1.5T四缸的03更适合你。领克03有哪些竞争对手？其实领克03的定位属于A级运动型家轿，所以最直接的对手应该是本田思域和昂克赛拉。但是新款领克03定价15.48万起，没有L2级驾驶辅助，也没有18英寸轮圈和360全景，连性能套装都不能选装。真正要买的话应该从16.68万的中配看起。但是这个售价已经能买到顶配的思域了，思域虽然只有1.5T，但他是本田。而且思域的名气大，口碑好，保值率也高。关键是思域还有JDM的信仰加成，不管是家用还是改装买思域都不会错。所以领克03在它面前即使动力好，配置高，内饰装潢也更有味道，但是入手价格还是偏高，钱包受不了。以现在03的价格去竞争思域，肯定有客户会纠结很久，迟迟不敢下手。而对比昂克赛拉，领克03虽然空间更大，配置更高，动力甚至强的不是一星半点，但是依然面临价格偏高的问题。昂克赛拉2.0自动质雅版，指导价14.29万，优惠完12万出点头，落地才13万出头，跟领克03入门15.48万比，还是便宜2-3万。即使看昂克赛拉的车主想要回头买领克03，还是会因为价格够不到而困扰。所以，我强烈建议领克03开放零首付，零利息贷款。明面上价格就是比合资贵，实际上贷款使劲的补贴客户，让他们买起来没压力，这才是取胜的法宝。要知道，17-18万的落地价，都可以买到很多合资的B级轿车了，为什么要选一个国产A级车呢？这个道理，我相信很多人都懂。不能因为领克品牌拿下了几次WTCR年度总冠军，就得让所有年轻人都有信仰，都支持国产吧？我们也知道领克03上市4年，销量超过了23万辆，但是还记得我们开头说的数据吗？轩逸一年50万辆，卡罗拉+雷凌45万辆，速腾+宝来+朗逸一年80万辆，领克03任重而道远。可以添加微信46415254加入我们的社群音频图文更新在订阅号： 百车全说每期抽三条留言，每人赠168元的“芥末绿”燃油添加剂一瓶点击订阅，每周三，周六更新会有提醒新听友可以搜索：百车全说2014，百车全说2015，百车全说2016，往期300多个小时的节目可供收听

"In this article, I'll talk about L2s on Ethereum, the state of the current scaling ecosystem, and why I believe running L2s on top of Ethereum is the most economically and technically sustainable scaling solution long term." ------------------------------------------------------------------------------------

Robinhood Wallet releases to public beta with initial support for Polygon, Superfluid integrates bridging via LI.FI, EPNS rebrands to Push Protocol, and OpenSea adds support for Optimism. Newsletter: https://ethdaily.link/signup Twitter: https://ethdaily.link/twitter Lens: https://ethdaily.link/lens

Design of the on-board data compression for the bolometer data of LiteBIRD by Mayu Tominaga et al. on Monday 26 September LiteBIRD is a space-borne experiment dedicated to detecting large-scale $B$-mode anisotropies in the linear polarization of the Cosmic Microwave Background (CMB) predicted by the theory of inflation. It is planned to be launched in the late 2020s to the second Lagrange point (L2) of the Sun-Earth system. LiteBIRD will map the sky in 15 frequency bands. In comparison to $it{Planck}$ HFI, the previous low-temperature bolometer-based satellite for CMB observations, the number of detector has increased by two orders of magnitude, up to $sim$5000 detectors in total. The data rate is 19 Hz from each detector. The bandpass to the ground is limited to 10 Mbps using the X-band for a few hours per day. These require the data to be compressed by more than 50 %. The exact value depends on how much information entropy is contained in the real data. We have thus evaluated the compression by simulating the time-ordered data of polarization sensitive bolometers. The foreground emission, detector noise, cosmic ray glitches, leakage from the CMB intensity to polarization, etc. are simulated. We investigated several algorithms and demonstrated that the required compression ratio can be achieved by some of them. We describe the details of this evaluation and propose algorithms that can be employed in the on-board digital electronics of LiteBIRD. arXiv: http://arxiv.org/abs/http://arxiv.org/abs/2209.12492v1

Text Hawk to 66866 to become part of Mindful Monday. Receive a carefully curated email from me each Monday morning to help you start your week off right...  Full show notes at www.LearningLeader.com Twitter/IG: @RyanHawk12    https://twitter.com/RyanHawk12 Scott Galloway is a professor at New York University's Stern School of Business, where he teaches brand strategy and digital marketing to second-year MBA students. A serial entrepreneur, he has founded nine firms, including L2, Red Envelope, Prophet, and Section4. In 2012, he was named one of the “World's 50 Best Business School Professors” by Poets & Quants. He's the author of multiple best-selling books including The Algebra of Happiness, The Four, and Adrift. Notes: Leaders who sustain excellence: Demonstrate excellence in what they do. "People want to follow people who are excellent at their job." They hold people accountable "Excellent leaders are generally kind to others and establish goodwill with many people." "Your job is to find something you're good at, and after ten thousand hours of practice, get great at it. The emotional and economic rewards that accompany being great at something will make you passionate about whatever “it” is." “I tell my students that nothing wonderful, I'm talking really fantastic, will happen without taking a risk and subjecting yourself to rejection. Serendipity is a function of courage.” "If you don't get criticism it means you aren't saying anything." What does it mean to be a man? “Being a responsible head of household that provides for your family and is a real partner with someone and raising kids and checking that instinctive box — being a good father, being a good husband … raising responsible, civic-minded kids. It's also realizing that if your partner is better at being the head of household and being the provider you get out of the way and support them to do it." "The most dangerous person in the world is a broke and alone male, and we are producing too many of them." Greatness is in the agency of others… When I asked Scott about how he's built his career, his first thought was about the others who he's surrounded himself with. Greatness is in the agency of others. Your ability to attract and retain talented people will be the difference between a good career and a great one… We should spread kindness. Have security in yourself and give people compliments they deserve. "The most interesting 5 minutes I've had in a long time" - Anderson Cooper describing Scott Galloway "This guy is a walking applause break" - Bill Maher describing Scott Galloway Scott has sat on the boards of Gateway Computer, Urban Outfitters, Eddie Bauer, The New York Times Company, University of California Berkeley, Panera Bread, and Ledger, a crypto wallet. He hosted the CNN+ host of a business and technology show, No Mercy No Malice.

※ 投稿邮箱：418150505@qq.com※ 本文章发布于订阅号：百车全说，订阅号阅读更加方便，欢迎关注前30分钟聊红旗HQ9，后半部分聊差点损失5万多的惊悚经历。今天咱们要聊的车型是红旗HQ9，当我看到它的售价35.88-53.88万的时候，既有些意料之外，又感觉是情理之中。因为红旗车型的定价，从来都不是按照常规国产车定价规则来的。我说的规则，就是对标合资车配置更高，空间更大，价格更低。红旗有自己的定价规则，它也许是对标合资，也许是对标豪华，反正绝对不可能跟同级国产车型一个价。而买红旗的客户，似乎对价格也不是那么敏感。那么买MPV的客户群体，他们对价格敏感吗？我觉得30万上下是目前MPV购车用户的主流，而这部分客户家里已经有了一台甚至更多的台私家车，买MPV纯粹是为了改善出行质量。因此，家用MPV的客户预算上下浮动可以有个小几万。而商用MPV客户，一般目标都比较清晰，什么样规模的企业，做多大的生意，日常接待什么样身份的客户都比较明确。所购买的MPV车型，不能太便宜，太便宜显得公司没有实力，也会让客户感觉不重视自己。当然也不能太贵，否则显得太浮夸，太高调。因此，30-50万区间是商务SUV的主流价位。那么红旗HQ9定价35.88-53.88万，官方又宣称主打商用车市场，这个逻辑就说的通了。回看市面上的主流MPV车型，丰田赛那、本田奥德赛 、艾力绅这些车型，还是偏家用多一些，家用MPV不仅需要考虑驾驶感受，得轻松一些，舒服一些，要有混动技术，省心省油。同时也需要照顾二三排的乘客，需要功能丰富、空间够用，客户看中的是面面俱到，经济适用的工具车，保值率高，稳定性好，不出错，这就是台好车。而GL8和广汽传祺M8，我觉得更偏向商用多一些，商用MPV更多的是牺牲一些操控性，让空间更大一些，二排三排的乘员照顾的更周到一些，驾驶员开起来舒不舒服这并不是重点。其实真要说起来，别克GL8应该算是中国MPV市场里的元老了。自2004年进入中国市场以来，路面上能见度最高的MPV就应该是这款车型。你想想，上到领导干部，下到企业老总，在过去的很多年里，只要稍微讲究点排场的商务场合，肯定会首选GL8来接待贵宾，因为它是大家公认的七座商务车。如果你只需要接待3-5个人，大众也好，奥迪也罢都可以随意挑，但是6-7人，在当年好像除了GL8也每没太多可选。当年别克在MPV市场上可谓是把红利吃的满嘴流油。在2010年之前，国内市场上就没几台MPV可选，除了GL8，大家还能想到什么车型？稍微懂点车的估计能想到丰田的普瑞维亚，日产贵士，但是06年的时候，它们定价都是接近50万。那时候买这两台车的人，都是非富即贵。还有奔驰Viano唯雅诺，在埃尔法还没登陆中国市场的时候，这就是有钱人的保姆车。还有本田奥德赛，熟悉这款车的人应该知道，在2014年之前，奥德赛还只是轿车模样，后门也是正常的往外拉的开门方式，2015款之后才改成了侧滑门。所以这车一直给人感觉也就是加长、加座、加了屁股的轿车而已。但是后来随着国内市场上MPV车型的不断增加，MPV车型才开始慢慢成为了普通家庭关注的车型。从2011年开始，明星的保姆车丰田埃尔法引入国内，当时售价就高达56.88-68.88万，没想到还是被加价疯抢，一直持续至今。再比如2012年东本艾力绅开始国产，再到2014年奥德赛大换代，换成推拉门。渐渐地，国内的消费者也慢慢开始意识到，原来MPV并不是商务车，商务车只是MPV里的一种分支而已。如果说二胎政策的放开加快了SUV的市场化，那三胎的放开绝对加速了MPV车型的推陈出新。大家看看最近一年，国内市场上涌现了多少MPV车型？国产丰田赛那、现代库斯途、起亚嘉华、大众威然、岚图梦想家，腾势D9，极氪009等等。现在，又来了一款红旗HQ9。前面说了那么多我对MPV的看法，接下来我们就来聊聊红旗HQ9这款车怎么样，定价贵不贵，哪些人适合入手，哪个配置适合入手？红旗HQ9怎么样？红旗最近步伐很快，继H5之后又发布了两款全新产品。一是HQ9这款中大型MPV，另一个就是大型SUV LS7。不过我觉得红旗最近两年步子走得很急，感觉像是在有限的时间内要完成任务一般，火急火燎的想要把轿车、SUV、MPV车型全部补齐，甚至燃油、混动和纯电也全部都得到位。而关于红旗的定价，其实你只要看一款车就行了，那就是LS7。这款大型SUV长宽高分别是：5695/2095/1985毫米，轴距3309毫米。如果不是有规定超过6米就要悬挂黄牌，我甚至感觉他很可能直接按6米来造。当然，红旗想让6米的车上蓝牌，也不是没有这种可能性，改一下规则而已。红旗LS7的尺寸放在大型SUV也是吊打同级，宝马X7的长宽高：5163/2000/1835毫米,轴距3105毫米，奔驰GLS迈巴赫尺寸和X7差不多。所以，红旗LS7比宝马X7和GLS迈巴赫还长了半米多。我找了一圈，目前国内在售的SUV中，尺寸能达到这个程度的只有林肯的领航员壹号。看清楚，是领航员壹号，加长版的领航员，不是普通的领航员。所以真要说起来，红旗LS7是国产尺寸最大的SUV车型，一点也不夸张。同时它应也是国产最贵的SUV，没有之一，售价136.58-146.58万。这就是红旗品牌的调性，你可以看看而已，但我必须价格封顶。我们回头再看今天聊的主角，红旗HQ9。这款车定位中大型MPV，售价35.88-53.88万。这是红旗的第一款MPV，看它的数字，HQ9应该是红旗家族里最大的MPV，也不排除今后可能还会推出HQ7、HQ5小一号的MPV。所以，这款车的定价肯定得先标高一些。和以往红旗车型差不多，当你看到HQ9的第一眼就知道这是台红旗，而且是台大红旗。这个“大”不仅是指车身尺寸，HQ9长宽高分别为5222/2005/1935mm，轴距为3200mm，车内座椅布局为2+2+3式。隔壁的GL8陆尊也不过长宽高5219/1878/1799，轴距3088毫米。比GL8宽了127mm，高了136mm，轴距长了112mm。除了车身尺寸大，HQ9车头的大嘴也非常大，这个巨大的进气格栅我估摸着占了车头一大半的面积，我严重怀疑这是五年后宝马鼻孔的大小。其次，进气格栅中间的红色线条也是红旗的专属。所以HQ9的车头看起来就神似加高加宽的H9。车侧部分，HQ9和普通的中大型MPV基本没有区别，重点就是D柱的位置会稍显不同，百叶窗状的镀铬装饰条确实有点独特。车尾造型基本也很沉稳，贯穿式的尾灯+镀铬条。不过有点不一样的是红旗竟然给HQ9配了一个尾翼，一个外观很商务的MPV竟然给配了一个车尾的顶翼，难道是红旗觉得它太商务了，像价格尾翼让它更运动亲民一些？另外，目前媒体拍摄的HQ9的轮毂被无数人吐槽，这种五朵花瓣似的轮毂造型，放在运动型车上可以，放在商务车型上，感觉是很奇怪。内饰方面，说实话设计感还行，16.2英寸中控屏也不算小，但是没有H9上的那套更有豪华感。HQ9按理说直接把H9的那套内饰放上去岂不是更好？也许红旗内部要求是创新，所以设计师领了任务，就不敢按照套娃的方式来设计，可以理解。不过MPV最核心的不是内饰，还是配置，特别是第二排和第三排座椅的配置。我觉得大家要相信红旗，造车行不行我不敢说，但是怎么让领导舒服，它一定行。在配置上，全系标配6气囊、电子驻车、胎压监测、驻车雷达、倒车影像、定速巡航、全景天幕、电动遮阳帘、无钥匙启动、7英寸液晶仪表、第二/三排座椅靠背电动调节、16.2寸触控中控屏、LED大灯、第二、三排+后风挡隐私玻璃、三温区自动空调等。在中高配上，HQ9的第二排是宽大且舒适的头等舱。同时，HQ9配备有“迎宾台”功能。常规状态下，该迎宾台位于前排座椅之间。在需要使用时，第二排乘客可以通过扶手屏将迎宾台电动后移，并成为第二排乘客的多功能控制台，具体功能包括杯架、手机无线充电板、可电动升降香氛系统和储物格。这种玩法，之前在iMAX8上应该很多人都看过。而且HQ9的二三排座椅是共轨设计，在第三排没有乘客的情况下，第二排座椅能一直滑到第三排，腿部会腾出非常大的空间。同时，因为是二三排共轨，也就意味着它的第三排地台和第二排地台是处于同一水平高度，并不会出现很多MPV第三排类似于“阶梯教室”的高坐姿，而且第三排如果空间不够，还可以往后备箱位置移动。反过来，也可以把第三排往第二排移动。你别说，这个设计真的不错。当年广汽传祺M8，三排无法移动，就被无数网友吐槽，这个设计值得竞品学习。当然，像赛那那种把三排座椅折叠放在后备箱下方，也可以腾出很大的空间，不过成本显然更高一些。但无论怎么看，红旗HQ9在车内的空间和舒适性上，确实做的不错，估计这个设计能圈粉不少人。动力上，HQ9全系搭载2.0T发动机+48伏轻混系统，发动机最大功率185千瓦，峰值扭矩380牛·米，匹配8速手自一体变速箱。同时，HQ9的前悬架为麦弗逊式，后悬架为多连杆式独立悬架。有网友吐槽，这都什么年代了，不是混动谁买啊？这话我就不爱听了，岚图梦想家和腾势D9都是插混，我看买的人也不多。GL8就是2.0T，销量一直排第一，所以这根本不是发动机的问题。HQ9定价贵不贵？至于HQ9的定价贵不贵，我觉得这得看两方面。不知道大家有没有感觉，其实红旗的商务车和普通的民用车区别还是比较大的，比如红旗L5和红旗H5，虽然都是5字结尾的轿车，但是定位完全是两个概念。那么，红旗HQ9如果定位是商用车，那我觉得这个定价，算是自降身价了。而你如果真的拿它跟常见的合资或者国产MPV比，那么定价35.88-53.88万肯定是贵的。其实根本不用太复杂的比较，咱们就拿别克GL8最畅销的ES陆尊版来比较，ES陆尊销量最好的配置是31.79万的舒适和34.39万的尊享。而红旗HQ9起售价就是得35.88万，按道理对标的是34.39万的ES陆尊的尊享版。可是，GL8到了这个配置，L2级智能驾驶辅助已经配齐，其他配置也与红旗HQ9不相上下。但HQ9的最入门的35.88万版本，不仅没有L2级智能辅助驾驶，连车主最关注的侧滑门还是手动的，主副驾驶还是手动调节，座椅加热更不可能有了，氛围灯这些想都别想，还有双层夹胶玻璃、车内空气净化等等都没有。配置给不到位，难道就因为比GL8大一圈，再加上红旗品牌加持，就可以比GL8贵1万多吗？大家可以谈谈自己的看法。个人推测，红旗HQ9的主售车型，应该是43.88万以上的版本，因为L2级驾驶辅助、双侧电滑门、电尾门、后排小桌板、16色氛围灯都是从这个版本才开始配齐的，我不信一个买红旗HQ9的客户，顶着这么大个红旗标，这个气派的造型，却只花低配的钱买到这么丐版的配置？无论家用，还是企业接待，这都让人感觉很奇怪。性价比高不高，和对手比怎么选？其实看到红旗HQ9的那一刻起，我就感觉这台MPV会更偏商务一点。如果真的想要定位偏家用的话，要么低配配置不变，价格下调。要么价格不变，配置上调，不然HQ9作为家用MPV来说，性价比真的一点也不高。买红旗HQ9低配的预算，其实都可以轻松拿下赛那的中配了，甚至可以买到顶配的奥德赛。我们刚刚对比的中配GL8陆尊都能买到了。相比HQ9，作为家用MPV，赛那它名气更大，GL8销量也是碾压同级的存在。奥德赛、艾力绅这些车型口碑和知名度都很高，还有国产广汽传祺M8也一直很受欢迎。这些车有的省油、有的保值、有的省心，个个都很能打。所以，不是说红旗HQ9做的不好，而是别人已经是水桶车型了，让我用什么理由选择你呢？所以如果你买来只是为了家用的话，我不会推荐你买HQ9，除非你非常喜欢红旗，而且非MPV不买，要不然我宁愿推荐你买红旗HS7都不会推荐你买HQ9。除非你说，我非红旗不买，非MPV不买，那我就不劝你了。所以如果花40万买车，SUV和MPV你会怎么选呢？可以添加微信46415254加入我们的社群音频图文更新在订阅号： 百车全说每期抽三条留言，每人赠168元的“芥末绿”燃油添加剂一瓶点击订阅，每周三，周六更新会有提醒新听友可以搜索：百车全说2014，百车全说2015，百车全说2016，往期300多个小时的节目可供收听

Even though the vocal tract is the same regardless of a child's sex before puberty, researchers have found time and again that adults can perceive gender differences in speech as early as four years of age. In this episode, we talk to Priscilla Fung, lead author of “The development of gendered speech in children: Insights from adult L1 and L2 perceptions,” which appeared in the January 2021 issue of JASA Express Letters. We talk about how her team's research about gendered speech shows that gender differences may be apparent even earlier than previously studied, how acoustic measures play into those differences, and the role the first language of the child and the listener will affect those perceptions.Associated paper:Priscilla Fung, Jessamyn Schertz, and Elizabeth K. Johnson. “The development of gendered speech in children: Insights from adult L1 and L2 perceptions.” JASA Express Letters 1, 014407 (2021); https://doi.org/10.1121/10.0003322.Read more from JASA Express Letters. Learn more about Acoustical Society of America Publications  Music: Min 2019 by minwbu from Pixabay. https://pixabay.com/?utm_source=link-attribution&utm_medium=referral&utm_campaign=music&utm_content=1022

Link to bioRxiv paper: http://biorxiv.org/cgi/content/short/2022.09.20.508739v1?rss=1 Authors: Oldenburg, I. A., Hendricks, W. D., Handy, G., Shamardani, K., Bounds, H. A., Doiron, B., Adesnik, H. Abstract: Recurrent cortical activity sculpts visual perception by refining, amplifying, or suppressing incoming visual signals. Despite the importance of recurrent circuits for cortical processing, the basic rules that govern how nearby cortical neurons influence each other remains enigmatic. We used two-photon holographic optogenetics to activate ensembles of neurons in Layer 2/3 of the primary visual cortex (V1) in the absence of external stimuli to isolate the impact of local recurrence from external inputs. We find that the spatial arrangement and the stimulus feature preference of both the stimulated and the target ensemble jointly determine the net effect of recurrent activity, defining the cortical activity patterns that drive competition versus facilitation in L2/3 circuits. Computational modeling suggests that a combination of highly local recurrent excitatory connectivity and selective convergence onto inhibitory neurons give rise to these principles of recurrent activity. Our data and modeling reveal that recurrent activity can have varied impact, but a logic emerges through an understanding of the precise spatial distribution and feature preference of the multicellular pattern of activity. Copy rights belong to original authors. Visit the link for more info Podcast created by PaperPlayer

Development of the Low Frequency Telescope Focal Plane Detector Modules for LiteBIRD by Benjamin Westbrook et al. on Wednesday 21 September LiteBIRD is a JAXA-led strategic large-class satellite mission designed to measure the polarization of the cosmic microwave background and Galactic foregrounds from 34 to 448 GHz across the entire sky from L2 in the late 2020s. The scientific payload includes three telescopes which are called the low-, mid-, and high-frequency telescopes each with their own receiver that covers a portion of the mission's frequency range. The low frequency telescope will map synchrotron radiation from the Galactic foreground and the cosmic microwave background. We discuss the design, fabrication, and characterization of the low-frequency focal plane modules for low-frequency telescope, which has a total bandwidth ranging from 34 to 161 GHz. There will be a total of 4 different pixel types with 8 overlapping bands to cover the full frequency range. These modules are housed in a single low-frequency focal plane unit which provides thermal isolation, mechanical support, and radiative baffling for the detectors. The module design implements multi-chroic lenslet-coupled sinuous antenna arrays coupled to transition edge sensor bolometers read out with frequency-domain mulitplexing. While this technology has strong heritage in ground-based cosmic microwave background experiments, the broad frequency coverage, low optical loading conditions, and the high cosmic ray background of the space environment require further development of this technology to be suitable for LiteBIRD. In these proceedings, we discuss the optical and bolometeric characterization of a triplexing prototype pixel with bands centered on 78, 100, and 140 GHz. arXiv: http://arxiv.org/abs/http://arxiv.org/abs/2209.09864v1

Development of the Low Frequency Telescope Focal Plane Detector Modules for LiteBIRD by Benjamin Westbrook et al. on Wednesday 21 September LiteBIRD is a JAXA-led strategic large-class satellite mission designed to measure the polarization of the cosmic microwave background and Galactic foregrounds from 34 to 448 GHz across the entire sky from L2 in the late 2020s. The scientific payload includes three telescopes which are called the low-, mid-, and high-frequency telescopes each with their own receiver that covers a portion of the mission's frequency range. The low frequency telescope will map synchrotron radiation from the Galactic foreground and the cosmic microwave background. We discuss the design, fabrication, and characterization of the low-frequency focal plane modules for low-frequency telescope, which has a total bandwidth ranging from 34 to 161 GHz. There will be a total of 4 different pixel types with 8 overlapping bands to cover the full frequency range. These modules are housed in a single low-frequency focal plane unit which provides thermal isolation, mechanical support, and radiative baffling for the detectors. The module design implements multi-chroic lenslet-coupled sinuous antenna arrays coupled to transition edge sensor bolometers read out with frequency-domain mulitplexing. While this technology has strong heritage in ground-based cosmic microwave background experiments, the broad frequency coverage, low optical loading conditions, and the high cosmic ray background of the space environment require further development of this technology to be suitable for LiteBIRD. In these proceedings, we discuss the optical and bolometeric characterization of a triplexing prototype pixel with bands centered on 78, 100, and 140 GHz. arXiv: http://arxiv.org/abs/http://arxiv.org/abs/2209.09864v1

※ 投稿邮箱：418150505@qq.com※ 本文章发布于订阅号：百车全说，订阅号阅读更加方便，欢迎关注前40分钟聊宝骏kIWI EV，后半部分聊我面试的经历。先问大家一个问题，10万左右的预算，你们会买什么车？我相信我的粉丝们大概会分成三波群体，一种是只看合资车。相比几年前，现在的入门合资车的价格便宜了不少，价格已经被众多国产车和电动车给打下来了。比如卡罗拉、朗逸都有两万甚至更高的优惠，十二三万就能落地。虽然配置不高，但是买它的人就是认合资车的品牌力，再加上省心、不坏就够了。第二种是看完合资车，觉得除了品牌力之外毫无性价比，转身选择了空间更大、动力更强、配置更高的国产车，尤其是国产SUV，花着和合资A级轿车车不多的钱，用起来却舒服太多，觉得这才是真正的刚需用车。像哈弗H6，长安CS75PLUS，现在的混动比亚迪宋PLUS DM-i这些。第三种就是看电动车的，比如比亚迪海豚、秦PLUS，还有上期说到了MG MULAN，还包括广汽埃安Y、欧拉好猫等，选择电动车的又是另一部分人群，同样价位买到的电动车动力肯定比同价位燃油车更好，电费又便宜，出行成本大大降低，而且电动车要比油车更安静，开起来质感也会更好一些。今天我们要聊的车，选它的人可能是第四种，甚至第N种人群，宝骏KIWIEV，定位微型电动车。这车外形十分另类，长的像个行走的火柴盒。但是熟悉K-CAR的朋友一定知道，这种设计更多的是为了得到更大的内部空间。不过，宝骏的品牌力在厂家眼里肯定是高于五菱，但是消费者的接受程度明显正好相反。大家看看五菱宏光MINIEV的销量就知道，每个月几万台，而宝骏KIWI每个月只有小几千台。我相信，粉丝应该知道宝骏KIWI的估计很少。如果正巧你就是宝骏KIWI的车主，或者你是KIWI前身宝骏E300车主，也欢迎在节目下方留言，聊聊自己的用车感受。前不久，2023款宝骏 KIWI EV正式上市，售价8.78-10.28万元。估计很多人一听就要纳闷了，一个微型电动车竟然定价10万块，不过回想五菱宏光MINI EV的GAMEBOY版都要卖到7万，敞篷版定价要超过10万。那么宝骏KIWI EV为什么敢卖10万？原来它也有一个别人没有的卖点，就是跟大疆合作，多了一套智能驾驶辅助，那么消费者会为这个买单吗 ？今天我们就来好好研究一下宝骏KIWI这款车？聊聊它到底有哪些优缺点？10万级电动车还有哪些可选？特别是，这次大力宣传的顶配大疆版，是否值得入手？宝骏KIWI究竟怎么样？和宏光MINIEV有什么区别？宝骏KIWI EV其实早在2020年就推出了，只不过当时它还并不叫KIWI，而是叫宝骏E300。但是如果你仔细看过价格就会发现，当时的五菱宏光MINIEV售价2.88-3.88万，而隔壁的宝骏E100在2020年售价4.98-5.48(两门两座，长的像smart，续航305km）。同时E200 5.48-6.48万（E100升级版），E300 6.48-8.48万（两门三座/四座，续航305km），这四台车组成了一个2.88-8.48万的产品线。所以，大家不要以为宏光MINI EV是一战成名的，实际上是宝骏E系列在为它负重前行。当时的E300还分为双门三座和双门四座两种车身结构，后来到了2021年，没想到宏光MINIEV爆火，所幸宝骏也给五菱让路，直接停产了E100和E200，不过E100和E200目前被五菱NANO EV所以取代。而E300也改名换姓，换个很洋气的名字KIWI，并且也取消了短轴的双门三座，只保留一种长轴的双门4座的车身结构，所以起售价也从之前的6.48变成了8.68万，一下贵了2.2万。这也是为什么很多人觉得宝骏KIWI EV这款车定价贵的原因。说回到KIWIEV上，定位微型电动车，车身长宽高分别为2894/1655/1595mm，轴距为2020mm。长度和宏光MINIEV差不多，但是KIWI的宽度更宽，轴距也长一点。所以外观上看，它就是台很小的车，不过2020mm的轴距几乎跟车长差不多，内部空间非常夸张，如果比作房子，应该算是得房率超高的户型，几乎没什么公摊面积。不过要说这款车最大的亮点那一定是它的外观造型。其实很多主机厂在夸自己的产品外观时，用词都非常夸张，所以大家看看就好了。但是KIWI说的是用了星际几何的设计语言，我觉得它的这个描述确实没有太夸张，相反，我甚至感觉还挺贴切的。因为你看到这台车后，你在市面上绝对找不出第二台和它一样的车了。如果说你喜欢宏光MINIEV的造型，但不喜欢五菱的标，其实你还可以看看奇瑞QQ冰淇淋、北京汽车的元宝可以选，但是如果你喜欢KIWI，那市面上还真没什么替代品。整车设计分为上下两层，就像拼接起来的一样，你可以说看上去很突兀，但看久了也挺顺眼，就像我们刷短视频，第一次刷到某个奇葩主播，这是什么玩意？第二次再刷到，脑子是不是有病？第三次再刷到，可能你就学会了“一给我滴GIAO”“你看扎不扎你就完了”，还有那些洗脑歌曲也是一样的道理，虽然想吐，但是久久不能忘去。而且KIWI也用上了双色车身的设计，加上23款KiWi EV新增摩卡、暮光、抹茶这三种小清新的配色，一定会吸引更多的女性消费者。所以在外观设计上，宝骏KIWI EV我觉得是成功的，哪怕你说它丑，它也是丑到竞争对手不敢模仿的地步，KIWI EV如果和五菱宏光MINIEV相比，它更像是个玩具。内饰上，新款KIWI EV相比老款也有了很大的变化，相比之前只有一块的小屏幕，新款直接给你配上了双联屏的设计，10.25寸液晶屏+10.25寸中控屏，并且这两块屏是全系标配。同时，KIWI的车机系统支持语音交互、多媒体影音、导航、车控设置等功能。其实，你如果体验过五菱或者宝骏的车机，其实做得挺不错，也许是我们上车之前就对它没有太多期望，就像我们拿到一台红米手机，肯定觉得它只要刷微博不卡就行了，结果打王者荣耀，吃鸡都不卡，心里肯定惊讶无比。再加上几乎所有宝骏4s店都在五菱4s店隔壁，看宝骏的客户大概率也会去看看五菱，那么宝骏KIWI EV的内饰跟宏光MINIEV比，真的算是豪装了。动力上，2023款宝骏KiWi EV是单电机驱动，和宏光MINIEV一样是后置后驱。不过智潮版、智奢版最大功率40千瓦，大疆版最大功率50千瓦，但最大扭矩都是150牛·米。续航里程智潮版、智奢版为305公里，大疆版为301公里，支持快充和慢充补电模式，快充模式下官方宣传电量30%-80%用时1小时（不过有老车主反映，40%之后快充速度会变的非常慢），使用交流充电桩满电时间为5小时。并且和宏光MINIEV一样，KIWI的三款配置都有磷酸铁锂和三元锂电池可选。在底盘悬挂上，其实KIWI和宏光MINIEV也有着很大的不同。宏光MINIEV为了节省成本，后悬挂用的肯定是非独立悬挂，但是KIWI是双横臂独立悬挂，所以在舒适性上肯定也要比宏光MINIEV好得多。至于KIWI为什么敢定位10万元，一是大疆的自动驾驶辅助作背书。另一点，也是最重要的，因为宏光MINIEV的的成功，所以五菱自己也越来越清楚，这种小车如果真想要卖的多，而且还想要持续卖的多，光靠性价比是远远不够的，关键是要有特色，要有别人无法取代的卖点。就像之前的长安奔奔E-STAR，售价和宏光MINIEV差不多，而长安奔奔E-STAR还是四门五座车，配置也更高一点，但它的销量相比宏光MINIEV，连零头的零头都没有，你可以说它是油改电，但是这个级别的客户，真的有多少人关心油改电的问题？E-STAR可是实实在在可以得到实惠。所以厂家总结出一个到道理：微型电动车，得把车造得有趣，再结合后期的宣传，把它打造成一个大玩具，这样就可以掩盖微型车的廉价感，成为一种时尚。不管男女老少，普通百姓还是大富豪，都想买一台回来玩玩，这才是长久之计。而KIWI看起来比宏光MINIEV更像一台玩具，而且内饰也更豪华，也更智能。况且宏光MINIEV GAMEBOY都卖7.28万了，我KIWI卖个十万出头又怎么了。你说是不是这个理？KIWI EV的对手有哪些？单看8.78-10.28万这个价格，其实KIWI的对手有很多，其中还包括很多燃油车，比如空间尺寸比它大好几个等级的A级轿车吉利帝豪，别克英朗，日产轩逸经典，这些车的落地价也就在9万多，和KIWI的落地价差不多。但是刚才我说了，买KIWI的车主都是把它当玩具来买的，或者就是图它的外形和设计，亦或是与大疆合作的智能驾驶这个卖点。像英朗轩逸这类车，他们绝对不会再看第二眼。所以真要从消费者的角度出发，那英朗，帝豪这类车和KIWI虽然价格差不多，但是买他的完全是两类不同的人群。从KIWI的人设来看，奇瑞小蚂蚁算是它的竞争对手之一，因为都是双门四座微型电动车，而且小蚂蚁的外形也不错。但是小蚂蚁有一个很大的弱点，很多共享汽车就是小蚂蚁，所以开它出去不知道的以为开的是共享汽车，所以它的定位更像工具，而不是玩具。其实我觉得还有一款车在外形、尺寸、设计上和KIWI非常接近，那就是长安糯玉米。和KIWI一样，糯玉米最大的特点也是在于外观，只不过和KIWI的风格不同，一个是几何风，一个是Q萌可爱风。不过相比KIWI，糯玉米的优势在于长度更长，价格也更便宜，顶配才6.39万，这个价格对比KIWI，确实便宜多了。但是真要说起来，宏光MINIEV才是KIWI最大的对手。为什么这么说？因为宏光MINI EV实在太出名了，而且价格也很便宜，最低配只要3.28万，虽然不及之前2.88万低，但是相比KIWI，便宜了整整一半。更关键的是，五菱的4s店大多紧挨着宝骏，有的4s店两家都是连通在一起。所以，宏光MINIEV的销量每个月三四万台，直接导致KIWI活在它的阴影之下。或者说，正是有了宏光MINI EV的存在，会让客户觉得KIWI太贵了，没有性价比。虽然KIWI和宏光MINIEV都是玩具，但是贵的玩具一样很少有人会买。其实说到底，预算不足才会理想，预算充足，买什么都感性。不信你也可以看看销量，KIWI最近半年的销量1.3万台，而宏光MINIEV呢？21.3万多台，20分之一。配置该怎么选，大疆版真的有必要吗？KIWI目前有智潮87800元、智奢93800元和大疆版102800元三款配置，其中智潮和智奢差价只有6000元，但是智奢多出了：360全景影像、无钥匙进入、隐藏电动门把手、4喇叭、语音控制车窗、LED大灯、车窗一键升降、外后视镜电动调节、车内化妆镜等等。所以毫无疑问，只要不差这6000块钱，9.38万的智奢肯定是最推荐的配置。那再往上的大疆版有没有必要选？在我看来，这种微型车一旦超过10万的售价就已经失去了它原本存在的意义，虽然它很智能，有全套的L2级驾驶辅助系统，硬件上配备了：6个摄像头、12个超声波雷达和1个毫米波雷达，但是它的NEDC续航只有301公里，如果上了高速还得打折，估计最后也就只能高速跑个200多公里。并且这套智能驾驶辅助只能在80km/h以下使用，这就很尴尬了，这种微型电动车也开不快，跑个100公里每小时的速度都费劲，再加上L2级驾驶辅助的上限就80km/h，感觉就很鸡肋。在城市里走走停停，各种路口插队，变道,我是不敢在市区随意开启L2级辅助驾驶功能的。所以L2级驾驶辅助放在这种只有300公里续航的微型车上，除了噱头还是噱头。我个人不是很看好大疆版的销量，不过据说这台L2级智能驾驶的方案，成本可以控制在1万元以内，这算是一个不小的突破。我们知道大疆无人机在智能避障方面还是很有心得的，不仅是无人机企业，像是扫地机器人企业，也是有非常好的一套方案可以智能避障。但是他们的方案更偏向于近距离，短暂的规避障碍。与专业的车企无人驾驶专业方案，还是有不少区别。所以在微型车领域低成本试水，是他们的首选。那么如果是你，你会花10万多买这台宝骏KIWI EV大疆版微型电动车吗？可以添加微信46415254加入我们的社群音频图文更新在订阅号： 百车全说每期抽三条留言，每人赠168元的“芥末绿”燃油添加剂一瓶点击订阅，每周三，周六更新会有提醒新听友可以搜索：百车全说2014，百车全说2015，百车全说2016，往期300多个小时的节目可供收听

Wintermute sufferers a $160 million hack, Coinbase Cloud launches Node APIs, MakerDAO greenlights GNO as collateral, and Optimism launches Optimism Quests. Newsletter: https://ethdaily.link/signup

 We have an episode for you! We chat with special guest Owner and Head Coach at Harvest Coaching, Jenna Altman. Jenna is certified as a fitness coach through ACE, L1 and L2 certified Precision Nutrition, Health Mindset Certified through Dr. Kasey Jo Orvidas and holds a specialisation in Functional Nutrition and Metabolism.We deep dive into the all-or-nothing mindset, how we lack purpose and meaning to life and also how self comparison affects our day to day. We hope this episode helps to navigate you into a better head space!

Vitalik Buterin publishes his three visions for Layer 3s, LI.FI releases an Arbitrary Messaging Bridge framework, ENS secures the eth.link domain, and stMATIC is now live on Aave V3. Newsletter: https://ethdaily.link/signup

Steven Goldfeder is Co-Founder and Chief Executive Officer at Offchain Labs, the team building Arbitrum. In this episode we discuss:  Steven's academic background, and his work at Princeton University.  BlockSci, an early blockchain forensics/search product that Steven co-founded.  The evolution of MPC custody and the exciting developments in that category.  The Flash Boys 2.0 paper and the current state of MEV.  Steven's views on the evolution of L1 smart contract platforms and how L2 scaling is shaping up.  The design choices and considerations that went into the choice of optimistic vs. zero-knowledge rollups on Arbitrum.  The future of ZK systems on blockchains.    To learn more about Arbitrum and follow Steven visit www.offchainlabs.com

It's back to school season! C'est la rentrée des classes! In this episode, Kelly and Ingrid discuss what is top of mind for them as they set up routines and expectations for the second language classroom in September. Bonne rentrée! #caslt #frimm #fsl #frenchimmersion #corefrench #L2

※ 投稿邮箱：418150505@qq.com※ 本文章发布于订阅号：百车全说，订阅号阅读更加方便，欢迎关注前40分钟聊MG MULAN，后半部分聊特斯拉和理想客户维权。上期节目说到了哪吒汽车，我在节目里还调侃会不会有车叫李靖、托塔天王？我觉得这个应该不远了，因为上期节目是古代神话人物，这期要聊的车名叫MULAN，谐音木兰。你看看，了解汽车知识的同时，我们不但能学习古代传说，还能了解中华历史文化。木兰是古代巾帼英雄木兰，全名花木兰。所以现在的国产车，在取名字这方面玩得越来越溜，就像国内公认最会取名字的品牌长城，像狗、猫、兔、神兽、初恋、咖啡、坦克等等，只有你想不到的，没有长城不敢取的。所以很多国产品牌深受长城的感染，也慢慢开始不再以字母+数字的形式命名了。在比如比亚迪，既有王朝系列又有海洋系列，海豹海豚，估计下一个不是海狗就是海狮。说回正题，MG名爵最近推出了它的首款纯电车型木兰，定位紧凑级轿车，售价12.98-18.68万。在它价格出来以前，很多人以为它能比比亚迪海豚售价低，所以抱着捡漏的心态准备买MG MULAN。结果价格一出，网上骂声一片，说这车价格太贵，该买比亚迪的买比亚迪，哪怕买五菱宏光MINEV也行。所以今天这期节目我们就来聊聊名爵木兰这款电动小车到底怎么样，定价贵不贵？它和比亚迪海豚、元PLUS，还有广汽埃安Y该怎么选？MG MULAN这车怎么样？MG MULAN这车定位紧凑级纯电轿车，是基于上汽星云纯电平台打造的紧凑型纯电车。和早前按区域定制化出海的产品不同，据说MG MULAN将在全球80余个国家和地区销售。根据规划，将于2022年第四季度抢滩欧洲市场，并计划2023年进军澳新、中东、墨西哥、南美等国家和地区。其实在别的地方，MULAN还有一个别名，MG4。在中国叫MULAN估计也是为了顺应文化潮流吧。不过我觉得木兰确实要比MG4更能让人记住。MULAN整车长宽高分别为4287/1836/1516毫米，轴距为2705毫米。新车车头的造型和以往名爵的车型完全不一样，名爵5、6都是中网再加大嘴，看起来很凶的样子，但是MULAN看起来就没有那么凶。而且它整体造型也不像很多纯电车，设计感那么超前。总之第一眼看上去，既不像电车，也比燃油车更有设计感。车身侧面比较正常，但是车尾那块感觉就很紧凑。现在的车设计的都是越来越大，但是MULAN感觉并不想设计的很大。到了车尾，这个造型确实比较运动，Y字型的尾灯再加分段式尾翼，但是感觉这个造型又很熟悉，尾翼像长安UNI-T，尾灯又像CS75PLUS，合着设计师是从长安身上找到了灵感？其实不光MULAN，自从长安CS75PLUS推出以后，Y字型尾灯就开始流行起来，从哈弗神兽到红旗H5，再到上汽大通G90和MG MULAN，都是这种Y字型尾灯。你们觉得是普通的尾灯好看，还是这种Y字型的尾灯好看呢？来到车内，名爵木兰作为一款国产车，这个设计就显得台简单了点。同样是极简风格，而且木兰还比特斯拉MODEL 3 的中控多了一块液晶仪表，但是就是没有那种高级感。我觉得这大概率还是因为出风口，因为特斯拉虽然只有一款屏幕，但是它的出风口是隐藏式的，是有一定的整体感，而且中控屏的尺寸大、边框小，没有实体按键。木兰的出风口既不是隐藏式，而且屏幕也不够大，底下还有一排塑料的实体按键。这里也不是吹特斯拉，只要你们去对比就能看得出谁更高级一点。即便是竞争对手比亚迪海豚的设计，也是吊打MULAN的存在。而且这个液晶仪表看上去也并没有隔壁的五菱宏光MINIEV的大多少。动力上，木兰有单电机后驱和双电机四驱两种动力布局，并且都搭载了上汽的魔方电池。其中单电机低功率版售价12.98和13.98万，最大马力170匹，最大扭矩250牛米，搭载51度磷酸铁锂电池，CLTC续航425公里。高功率版最大马力204匹，最大扭矩也是250牛米，搭载64度三元锂电池，CLTC续航520公里。不过顶配的四驱双电动机版本更值得说一下，最大马力428匹，最大扭矩600牛米，官方0-100公里/小时加速仅需3.8秒。如果这个加速成绩是实的那这个顶配反而会更有性价比。虽然当今的电动车加速都非常快，但是能进4秒的还是不多的，尤其是它的价格只要18.68万，落地20万不到。要知道同样加速水平的电车售价基本都在25万以上。比如比亚迪海豹四驱高性能和汉EV四驱版都是28万多，极氪001双电机也是落地30多万，特斯拉Model 3 性能版就更不用说了，落地接近40万了。即便是零跑C01高性能版，也都是要25万+。所以这么一对比，反而顶配的MULAN好像更有性价比。只不过因为它的电池和后驱高功率版一样，都是64度，所以它的CLTC续航只有460公里。因此，虽然MULAN双电机四驱版动力很强，但是不能长时间地板电，不够持久。而且有一点也得吐槽一下，就是卡钳罩。估计厂家为了突出顶配的MULAN的性能，专为四驱双电机配备了橙色卡钳罩，没错，只是个卡钳罩而已。卡钳罩这个东西只是外表好看而已，除此之外别无用处，甚至还会影响刹车的散热，导致热衰减，所以这个东西真的是个智商税。要我说，还不如直接把卡钳喷成红色来得更安全，毕竟比起好看，安全更重要。MULAN的定价贵不贵？竞争对手都有哪些？老规矩，这得从两方面说起。如果对比国外的售价，那MULAN的价格绝对算便宜的，而且是很便宜。MG MULAN的国内售价是12.98-18.68万元，德国售价分别为31990欧元、35990欧元和37990欧元。如果按现在的汇率算，即便是最低配也要22万多人民币，顶配要26万多，比国内的价格贵了一倍。所以这么看，在国内买MULAN是要划算得多。但是你要是拿MULAN对比同样价格的竞品，MULAN普通版好像又没那么有竞争力了。比如比亚迪海豚，售价只有10.28-13.08万。虽然尺寸上比木兰小了一圈，动力上也差了一些，而且等车时间都很长，但是它便宜，顶配才13万多，木兰最低配都13万了。虽然续航上数据上看少了20多公里，但是真正跑下来估计也就差个最多10公里，几乎可以忽略不计。并且从配置上看，最低配的12.98万版本，仅仅是拿来拉低入门门槛的。后视镜是手动的，全车只有2个安全气囊，塑料方向盘，织物座椅，还是手动调节，不过两块大屏没有砍掉，而且车联网系统也还在，看来互联网这块上汽还是比较有信心的。因此木兰这款车，主售版本肯定是从13.98万起，而13.98万和12.98万都是用的磷酸铁锂电池，续航都在425km。如果你再多掏3万，就可以买到16.38万的三元锂电池版本，续航增加到520km，并且还多了一整套L2级智能驾驶辅助，电机也从125kw，增加到了150kw，还多了侧气囊，运动外观套件，前排手机无线充电，喇叭也多了2个，还有自适应远近光。可是你都愿意掏16.38万买木兰了， 为何不直接奔顶配18.68万的四驱版本呢？前后双电机，315kw，600N·m，官方宣传的百公里加速3.8秒，非常夸张。如果仅仅配个泰然者的新能源节能胎都能开出这个成绩，那整台车拿到手再强化一下，岂不是各种秒天秒地？关键是买了保险，上了牌，都不到20万。无非续航稍微少一点，才460km，但对于这种小车来说，普通家庭日常代步肯定够了。剩下的问题，就是你对于MG的这种小车，卖18万多，到底信得过信不过？而且木兰是MG名爵的第一款纯电车，后续的品控和口碑消费者都还信不过。比亚迪虽然最有名的是混动，但是纯电车型也跟着一起沾了光。所以即便是纯电，很多人也是首选比亚迪的。首先是比亚迪海豚，木兰总体来说比海豚略贵一些，但配置和性能要比海豚强一些。海豚电机是95kw，木兰起步是125kw，强得不是一星半点。其次，海豚胎宽195，木兰胎宽215，理论上稳定性更好。第三，海豚后悬架是非独立悬架，木兰是独立悬架。第四，车长木兰较海豚更长一些，但车高要低一些，外观个人主观判断，木兰更好一看。第五，海豚方向盘是二向调节，木兰是上下前后，四向调节，对于一些身材瘦小的人更友好。木兰其它的优点不多讲，大家可以自行上网查看，下面说说劣势。第一，海豚自重1.4吨，木兰1.6吨，重了约200公斤。第二，海豚带全景影像车型不到12万，而木兰接近14万，价格高了约2万，当然你也可以后期改。第三，两车虽都是磷酸铁锂电池，但海豚是比亚迪自己的刀片电池，木兰低配磷酸铁锂，高配宁德伊控的电芯。第四，海豚电池容量约45度，木兰是51度，木兰虽然高了几度，但自重大了200公斤，续航应该不及海豚。总的来说，两车各有优劣，海豚我已经试驾过，内饰的廉价感实再是让人喜欢不来。至于木兰，我在成都车展已经静态体验过了，如果内饰用料和做工好一些的话，我会更喜欢木兰一些。除了海豚，木兰的这个售价还可以买到比亚迪的另一款纯电车，元PLUS。元PLUS售价13.78-16.58万，目前卖的最火的是14.78万的510尊荣型，不仅尺寸上比木兰打了好几圈，而且配置也更高，空间也更大，最重要它是SUV。买这个价位的消费者最看重的就是性价比，所以像元PLUS这种紧凑型纯电SUV买这个价格，之前看是有点贵，但是对比木兰，瞬间变香了有没有？而且即便是现在买车，木兰的等车时间也不一样会比比亚迪快多少。如果想要空间，尤其是后排空间的话，那有一款车的后排空间更大，广汽埃安Y。虽然它的车产只有4410毫米，但是轴距有2750毫米，再加上纯平的地台，所以真要图空间大，广汽埃安Y更适合你。而且它的价格13.76万起，并没有比木兰的最低配贵上多少。不过如果拿木兰对比大众的ID3，那性价比会高一些。ID3售价14.9888万起，比木兰贵了两万。不过很多人买大众ID3的理由非常简单，就是好看。虽然木兰的价格比ID3便宜2万，但是买ID3的消费者并不会看木兰第二眼，因为木兰的外观确实没有ID3好看。所以相对来说，木兰的中低配版本，不太推荐购买，如果可能直接冲顶配四驱版本。如果你又觉得18万多买名爵这么一台小电动车，有些不甘心，或者说拿不出这么多预算，只能在15万以内考虑，那么除非你特别喜欢木兰的外观，或者特别喜欢MG这个品牌，否则的话该买比亚迪海豚、广汽埃安AION Y，欧拉好猫的还是去买吧。可以添加微信46415254加入我们的社群音频图文更新在订阅号： 百车全说每期抽三条留言，每人赠168元的“芥末绿”燃油添加剂一瓶点击订阅，每周三，周六更新会有提醒新听友可以搜索：百车全说2014，百车全说2015，百车全说2016，往期300多个小时的节目可供收听

Join JudgeCast in welcoming new host, L2 from New Jersey, Charles Featherer! In this episode we talk about things new L1s should know but might not. Things like “Where do the judges hang out online?”, “Where do I get shirts?”, … Continue reading →

In our Friday edition of the Sloika Darkroom, co-founder Ev Tchebotarev takes the mic to recap highlights from the week plus talk about strategies NFT photographers can implement to accelerate their sales. The ETH merge was completed successfully on September 15 reducing the blockchain's energy consumption by ~99.95%. Looking ahead, we'll see the Ethereum roadmap that will include the use of L2 chains to store more data, compression algorithms, and sharding. We unpack the details shared in the latest issue of Sloika's newsletter about ways to accelerate photo NFT sales. We cover the 3 tiers of collectors: whales, mid-tier (often, tech entrepreneurs), and creator/collectors, and discuss how a useful strategy might be to release work that is appropriately presented and priced to each tier that includes both 1/1 art and editions. Recorded on September 16, 2022. “Retweets are free, so let's use them to support other artists.” Speakers included Ev Tchebotarev, Dylan Wade, and host, Pam Voth. ------------------------------------------ Website: https://sloika.xyz Twitter: https://twitter.com/sloikaxyz Telegram: https://t.me/sloikaxyz Discord: https://discord.gg/FJpYyVPBY2 Instagram: https://instagram.com/sloika.xyz Newsletter: https://sloika.xyz/subscribe

Starbucks announces Polygon-based NFT rewards, StarkWare releases Cairo 1.0, Optimism releases a Bedrock Alpha testnet, and Synthetix plans to suspend its contracts during The Merge. Newsletter: https://ethdaily.link/signup

Week two of the last ever playoffs is done. Some are happy, others sad, by the end of this episode you will know who is who. This week did have the longest recorded penalty kick session ever, like, don't bother fact checking that.  LONG LIVE INDY CUP!    What to listen for: L2 1:54 - Bell Brief - Evan from Inter Monon - Tattoo bets - Derailing Tangents - L1 25:30 - Julie and Ross from Riverside City - Professional Responsibilities - Rental Boots - Capris - Post League Talk 57:30 - Twitch Streams    Listen to new INDY CITY FOOTBALL LIVE! episodes every Tuesday (around 6pm) wherever you get your favorite pods. Don't forget to like this episode, ring the bell, turn the knob, and smash that follow button! 

Tu & Lei start off the podcast with a review of August sales numbers,  the pleasant surprises along with the disappointments. Tu and Lei then take a step back and talk about the global EV market, how the Inflation Reduction Act (IRA) should help the US EV sector and how some Volkswagen customers in Europe have gotten so frustrated with their ID Series vehicles they're returning them.Tu then moves the discussion to the recent restrictions placed on Nvidia and AMD that limits the chips they can export to China and Russia which leads to a broader discussion about the restrictions by both countries that have given them advantages historically that have manifested into companies that are leaders in the space currently.Tu and Lei then move to unpack Baidu's Robin Li who said that most companies would likely skip L3 and go straight from L2 to L4 autonomy with their vehicles and systems. They close the pod with a brief discussion about some of the challenges ahead for the foreign automakers that they'll need to overcome in China vs. their domestic counterparts if they are to ultimately succeed there.  

※ 投稿邮箱：418150505@qq.com※ 本文章发布于订阅号：百车全说，订阅号阅读更加方便，欢迎关注前40分钟聊全新福特探险者，后半段推荐书籍《身份的焦虑》。我们说到了花30多万可以买到的新宝马3系。但花同样的钱，还是有很多消费者不追求BBA这些豪华品牌，他们需要更务实，空间更大的六七座SUV，比如丰田汉兰达、理想ONE、大众途昂等。我们今天要说的就是30多万的SUV里，比较好开的一款6/7座SUV福特探险者。昨天，新款福特探险者正式上市了，售价30.98-37.98万。相比老款的30.98-39.98万，新款售价起售价与老款一样，但是顶配去掉了原有的铂金版。新款上市没有官降，看来这款车还是挺有自信的，那么福特探险者到底产品力如何，市场销售情况怎样，哪款配置最畅销，新老款探险者有哪些区别，竞争对手又有哪些？我们一一展开来聊聊。新款探险者有哪些改进？新款福特探险者是之前在售车型的中期改款，都属于第六代产品。也就是说，新款与现款的发动机、变速箱和底盘都没有变化。不过说到探险者，很多人心中最经典的不是现在的第六代，而是上一代（第五代），甚至就在前几个月，还有人拖我找找有没有第五代的探险者新车，我说这怎么可能有呢，六代都要中期改款了。其实很多人喜欢第五代的原因有两方面。首先是因为很多漂亮国的电影里，警察开的就是第五代探险者，本身就很粗犷的外观再经过特殊的改装和警车涂装，显得更加霸气。它在人们心中的印象仅次于雪佛兰的Suburban萨博班。而且，也是从第五代开始，探险者从非承载式车身变成了承载式车身，所以开起来会更舒服，没有硬核，这样的好处就是会有越来越多的人去买它，就像新宝马3系，虽然没有之前那么运动，变得更舒服了，但是就是卖得更好了。并且五代探险者的设计师，是原路虎的设计师吉姆·霍兰德，因此这一点探险者外形非常像路虎。这一代从2010年一直卖到2020年六代国产，整整10年时间。而第五代探险者首次进入到国内，最早于2010年7月进入到的国内，几乎与国外是同步的。所以真要论辈分，除了汉兰达，探险者绝对排第二，上市比途昂等早多了。不过第五代探险者因为是原装进口车型，一开始的定价特别高，只有3.5L V6+6AT一种动力搭配，78.8-83.8万。这个定价可以说是相当自信了，根本没把奔驰、宝马、路虎放在眼里，但最终还是被销量狠狠地打了一耳光。因此，在2013年进口探险者售价下调了将近一半，那也要卖到45-50万，这个预算的客户妥妥的可以买到宝马5系、奔驰E了，但是仍然有人钟情于探险者车型。回看第一批花七八十万买探险者的车主，其实挺冤的，现如今二手车置换，可能真的是会欲哭无泪。因为第五代探险者，到了后期推出了2.3T的版本，最低售价41.28万，我表弟就是最后一批购入第五代进口探险者的车主，那时候国产六代即将上市的消息已经出来，因此还有不小的优惠，应该说入手价格已经非常划算了，基本相当于宝马3系和奔驰C级。并且，五代探险者还有3.5T的版本，配的是与F150猛禽和福特GT同款引擎，最大马力356匹，最后一批的行情，落地才50万上下。你想想，宝马X3和X4的M40i版本， 333匹马力3.0T都要接近70万。可想而知，还是有懂行的会无脑入手3.5T的福特探险者的，用着也挺香。而现如今的国产六代探险者，已经没有3.5T版本了。说回正题，新款探险者和宝马新3系一样，外观小改，内饰大改。外观上车头改动比较大，进气格栅的面积减小了，采用了最新家族式3D鳞甲设计，虽然很时髦，但是看起来就是没有老款的霸气。前大灯组之间多了一条贯穿式的LED日间行车灯带相，同时取消了雾灯。因为国内法规对前雾灯没有强制要求，再加上现在的车基本都是LED大灯，亮度也够，所以节省成本去掉雾灯这个也能理解。新探险者的尾部造型变化不大，主要集中在后尾灯上，加大了后尾灯的面积。其次，新探险者竟然也抛弃了原有的露出式真排气，改为了隐藏式排气。新款探险者的车身长、宽、高尺寸分别为5063mm/2004mm/1778mm，轴距为3025mm，除了比老款长了12毫米外，其余的宽度和高度还有轴距和老款都保持一致。这样的块头已经全面超越同级别选手了，就连一向以“大”著称的途昂也比不过。车漆方面，新车提供格陵兰白、白令海灰、佩托湖蓝、塞舌尔黑和性能蓝五种颜色供选择，其中性能蓝色是顶配车型ST LINE的专属。对比老款，等于是把勃艮第红去掉，换上了白令海灰。所以，理论上想让人一眼看出，这是最新款探险者，买新增配色是最靠谱的。不过，新车毕竟不同于新手机，懂行的人并没有那么多。并不像你用上最新款iphone，无论是背面的配色，还是小留海变成感叹号，大家都知道。探险者的颜色还是根据自己喜欢来选，这是最靠谱的。车辆的外形无论怎么改，肯定有人说喜欢新款，有人说喜欢老款。但是内饰的变化，我相信大部分人还是会喜欢新款。新探险者全系标配了和EVOS、蒙迪欧同款的12.3英寸液晶仪表+27英寸的中控带鱼屏，分辨率4032x756，可以展现4K视频。不过和蒙迪欧、EVOS不同的是，新款探险者的内饰并不是与EVOS和蒙迪欧完全一样的设计风格，所以这个27英寸的中控屏和液晶仪表是分开来的，不是一体的。这点有点像我们之前说的宝马3系，内饰基本没怎么改，只是加了一套大屏。不过探险者的这套大屏相比老款，内饰的高级感提升了好几个档次，不像之前的那个竖屏，虽然尺寸有12.8寸，也不小，但就是不显档次，甚至有些突兀。此外，新款内饰配色除了全黑以外，还多了一套极光紫的配色。这个内饰配色不得不说要比全黑的好太多，不仅好看，色彩搭配得也恰到好处，很有高级感，而且也不易脏，不显旧。我也很好奇，为什么福特车的内饰颜色基本都是清一色的黑色，十台车里有9个是全黑的，难得见到一个白色+红色缝线，所以这个极光紫内饰也是福特车里面为数不多的彩色内饰。另外值得一提的是，新探险者的主驾驶和副驾驶的车窗玻璃都用了双层加胶设计，提升了一定的NVH表现。除了外观和内饰中控台的变化，其他部分新款探险者改动不大，仍然还是6座或7座车型可选，且除了最低配是后驱之外，其余均位四驱。7座车型标配第二排手动可翻转滑动座椅，6座车型电动翻转头等舱座椅，而且新车和林肯飞行家一样，全系标配第二排可语音复位6向电动调节加大尺寸机长座椅（按键进入+语音复位）。新款顶配ST Line版本增加了HUD抬头显示，四驱风尚就标配了前排加热通风座椅，二排加热座椅。动力方面，新款探险者和老款一样，用的依然是野马同款2.3T引擎+10AT，最大功率276马力，峰值扭矩425牛·米，百公里加速后驱车型7.6秒，四驱车型7.8秒，只要加92号汽油就行。所以从动力上看，挑不出什么毛病，但是油耗可能略高一些，想必买这车的人，应该早有心理预期。竞争对手有哪些，探险者值不值得买？这一代的探险者不再是之前的横置前驱平台，采用的是和林肯飞行家同样的纵置引擎后驱平台，所以真要说起来，探险者和林肯飞行家是亲兄弟，不像它的竞争对手大众途昂，和高尔夫奥迪A3是同平台，横置前驱。纵置后驱布局造价高，用料足，所以一般只有豪华车才会用上，就比如很多BBA车型。很多人不明白为什么BBA的X3 Q5 GLC卖得要比二线豪华的XT5 XC60贵得多。抛开品牌因素不谈，很多人心里也很清楚X3 Q5 GLC都是纵置后驱布局，而XT5和XC60都是横置前驱布局，虽然外观上看不出来，但是底子里还就是没有BBA的平台高级，毕竟凯迪拉克自己广告里都说“无后驱，不豪华”，当然这个广告是用在自家轿车上的，SUV车型直接躺枪。有人可能好奇，探险者这种纵置后驱到底哪里好呢？因为纵置后驱布局的车型前后重量分配得很均匀，重量不会都集中在车头，所以这种车型天生就要比横置前驱的车子好开。就像当你开过探险者再试驾汉兰达或者途昂的时候，很明显能感觉到途昂和汉兰达的车头要比探险者更笨重，指向也没有那么的精准，再回头开探险者，虽然车身也很重，但是明显能感觉到探险者是更好开的。所以从底盘和驾驶性角度分析，福特探险者相比同级很值得购买。但是如果从价格上来说，探险者的性价比就没有特别高了，尤其是福特的品牌力目前还不足以支撑30万以上的价格，当然，特色鲜明的F150猛禽和野马除外，因为那两个都输于玩具，不属于家用车的范畴。尽管探险者的底盘用料很扎实，但是以现在的售价，落地都要35-40万，想要打动消费者，还是需要消费者多做功课才行。而且即便是老款，优惠力度也很小，最高也只有2万。为什么这么说？我们一一来分析一下。新款探险者落地要35-40万，这个价格如果只是想买台SUV，一线豪华品牌的奥迪Q5L 40TFSI完全可以拿下。如果想要台豪华品牌的六七座SUV，也完全可以去买品牌力更高的凯迪拉克XT6了，虽然是横置引擎，但是凯迪拉克就算是二线豪华品牌，那也是豪华品牌，肯定要比福特有面子的多。如果要追求性价比，30万落地都能买别克昂科旗了，和凯迪拉克XT6一样，全系2.0T LSY高功率引擎+9AT，差不多的空间和动力，裸车价格还便宜好几万，跟探险者一样也能享受到购置税减半政策，不香吗？要是还觉得贵，隔壁还有雪佛兰的开拓者，别克昂科旗的亲兄弟，全系2.0T+9AT，裸车20万出头的7座中大型合资SUV，除了内饰老一点基本没缺点，还要啥自行车？其次，这个价位里，口碑和知名度比较高的肯定属汉兰达了，探险者的价格完全可以买到高配的汉兰达。现在汉兰达除了混动，又出了2.0T的纯燃油版，31.48-34.48万，最大马力248匹，动力还算不错，口碑、保值率和故障率都很均衡，再加上丰田的牛头标，在很多人心中买丰田就等于买银行理财，开几年也亏不了多少钱，同样的落地价怎么看都是汉兰达更稳妥。除了汉兰达还有大众途昂和揽境，尤其是途昂，外观很硬朗，很有硬派SUV的感觉，再加上大众标，也有不少人觉得它要比福特更高级。此外，都到了30多万这个价位了，还有沃尔沃XC90的亲兄弟领克09，底盘用料和安全性绝对排同级头头，深得沃尔沃的精髓。一开始领克09刚上市人人都说贵，结果到现在才发现，真正买的人都是奔着高配插混去的，是不是匪夷所思？别忘了30万出头还有理想ONE这个匹黑马，虽然是增程式，但是凭借着绿牌、大空间和丰富的配置也是深得大城市消费者的偏爱。要知道它最近一年买了12.2万多台，平均一个月一万多台，排在中大型SUV的第一名，要知道汉兰达才卖了11万台都不到。前两天的新闻，还爆出老车主去店里维权，因为最近官方降价2万，在尾款里直接抵扣。而且可靠消息是，理想ONE近期已经停产，很快就要被新车型理想L8垂直换代。所以对于探险者来说，前有汉兰达和大众途昂，口碑好，销量不错，老百姓认，后有凯迪拉克XT6追着打，左边还有昂科旗和开拓者，右边还有理想ONE、领克09等一众特斯鲜明的国产SUV夹击，留给探险者的市场空间真的少之又少。车的确是好车，但是得想方法让客户知道，认可，并且真正愿意掏出钱包，还是有很多功课要做，福特品牌力的提升应该才是解决这一问题的良药。新款配置该怎么选最后聊聊新款探险者的配置该怎么选。首先，我们要知道老款探险者卖得最好的配置有两个，一是入门版售价30.98万的后驱风尚，另一个是售价35.98万的四驱钛金版。而新款目前来看，也是这两个配置最为推荐。首先，入门版标配就已经相当丰富，12.3+27英寸屏幕全系都有，L2级智能驾驶辅助也没有缺席，全景天窗，电动后备箱，无钥匙进入，无钥匙启动，前排隔音玻璃，后排隐私玻璃，后排独立空调，车在空气净化器，一个都不少。只要对四驱没有强烈需求的客户，入门版即可。而如果选择四驱，预算又比较充足。那么钛金版35.98万可以得到12个扬声器的B&O音响，7色氛围灯，皮+翻毛皮混搭座椅，感应后备箱，手机无线充电，自动泊车等等功能。基本上算是一步到位了。再晚上多花2万也就是多了个ST-Line套件，21寸大轮圈，换挡拨片，hud抬头显示，前排座椅按摩，喇叭多两个。当然ST-Line的内饰风格也有所区别。不过我身边特别迷恋ST-Line风格的人并不多，所以，常理推断，还是次顶配会更畅销。可以添加微信46415254加入我们的社群音频图文更新在订阅号： 百车全说每期抽三条留言，每人赠168元的“芥末绿”燃油添加剂一瓶点击订阅，每周三，周六更新会有提醒新听友可以搜索：百车全说2014，百车全说2015，百车全说2016，往期300多个小时的节目可供收听

Binance converges stablecoins on its exchange, StarkNet releases Alpha v0.10.0, BarnBridge V2 is now live, and Curve Finance publishes a crvUSD repository on Github. Newsletter: https://ethdaily.link/signup

Jenna Altman is the Owner and Head Coach at Harvest Coaching. She has been in the health & fitness industry for 6 years. Jenna is certified as a fitness coach through ACE, L1 and L2 certified Precision Nutrition, Health Mindset Certified through Dr. Kasey Jo Orvidas and holds a specialization in Functional Nutrition and Metabolism via Sam Miller. She is also a pre and post natal training & nutrition certified coach through Girls Gone Strong. We talk all about how to live a healthy + full life in a sustainable way.  Check her out on instagram @jennaraealtman Menstrual Misfits-- my 8 week course to happier, healthier menstrual cycles + a TON of education is live for sign ups + the fun starts 9/19/22!!   I have a few spots available!  Learn more HERE

On today's episode we talk about how taking a short time away from "momming" can help optimize your emotional and mental health.

Curve Finance may launch a native stablecoin in September, Arbitrum One successfully migrates to Nitro, OpenZeppelin releases an audit report for cbETH, and RSS3 adds support for Lens Protocol content. Newsletter: ethdaily.substack.com

Clarity is kindness. Whether it's bringing a new person into your community, taking charge and leading your class, or helping to develop your Coaches and team...being clear will set you up for success. Denise Thomas is the creator of the Coaches Development Program, CrossFit Seminar Staff Manager, and part of a small team that works on developing the CrossFit Seminar Staff, the "red shirts" who teach the L1 and L2 courses globally. _________ SPONSORS This season of the Best Hour of Their Day Podcast is brought to you by our Official Sponsor, O2. O2 | Best Hour Affiliate Exclusive: Buy 4 Cases, Get a FREE Mini-Fridge, 4 FREE Cases, and a FREE YETI Water Bottle Visit here to learn more: https://wholesale.drinko2.com/pages/best-hour-offer _________ OUR “BEST” FRIENDS DocSpartan - Use code BESTHOUR at checkout for 15% - www.docspartan.com RXSmartGear - Use code BESTHOUR at checkout for 10% off - www.rxsmartgear.com WheelPay - An official best friend of our podcast. Check it out here - www.wheelpay.com LMNT - An official best friend of our podcast. Check it out here - www.drinklmnt.com InsideTracker - Use code BESTHOUR20 at checkout for 20% off - www.insidetracker.com --- Support this podcast: https://anchor.fm/jason-ackerman/support

Carm here from the Aftermarket Radio Network and my guest is Lauren Fix is a nationally recognized and trusted automotive expert, media guest, journalist, author, keynote speaker and radio and television host. Lauren is also from my hometown, Buffalo, NY. I caught up with Lauren, and we discussed her take on electric and autonomous vehicles, supply chain issues, and her passion for cars that are propelled by an Internal Combustion Engine. Lauren Fix, https://carcoachreports.com/ (Car Coach Reports),  https://carcoachreports.com/total-car-score-podcast/ (Total Car Score Podcast), is an automotive expert and analyst based in Buffalo, NY. She has written three books on automobiles. She has appeared on CNN, Fox News, Newsmax TV, CNBC, and USA Radio's Daybreak USA show. Key Talking Points Electric Vehicle- limited charging stations, L2 costs 1M for a charging station, alternating current can have dangers when charging Anti Inflation Act- tax credit, only 18 cars will qualify, Ford and GM raised prices   Shortage of rare earth minerals that cant get mined in the USA  Supply chain issues- oil filters, diesel oil Everything is processed with some form of oil Autonomous vehicles- unpredictable weather, insurance  Car family- a daughter, named Shelby Great cars for the average consumer- Kia Telluride and Hyundai Palisade Lauren owns 26 cars Connect with the Podcast: https://aftermarketradionetwork.com/ (Aftermarket Radio Network) http://youtube.com/carmcapriotto (Subscribe on YouTube) https://remarkableresults.biz/episodes (Visit us on the Web) https://www.facebook.com/RemarkableResultsPodcast (Follow on Facebook) https://remarkableresults.biz/insider/ (Become an Insider) https://www.buymeacoffee.com/carm (Buy me a coffee) https://remarkableresults.biz/books/ (Important Books) Check out today's partner: Learn more about NAPA AutoCare and the benefits of being part of the NAPA family by visiting http://www.NAPAAutoCare.com (www.NAPAAutoCare.com) https://aftermarketradionetwork.com () https://remarkableresultsradio.captivate.fm/listen ()

cETH on Compound is temporarily frozen due to an oracle error, DeFi Saver implements trailing stops, Myria launches a STARK-based zk-Rollup, and Voltz launches fixed rate borrowing Newsletter: https://ethdaily.substack.com

Listeners - before you start your journey through this episode, make sure you have a good two hours of distraction free time ahead of you. May your journey be safe and informative, we will see you on Thursday.   What to listen for: L2 4:32 - The Break - Poo - RetroActive Math - Big Brothers, Big Sisters - L1 39:32 - The Freak Kick (39:56) - Return of the #ICFLTPPBTSL1GOTW Trophy - Patrick Hall - Injury Report - Commish - Playoffs - Whew - Afterparty - The truest words ever spoken (1:42:38)   Listen to new INDY CITY FUTBOL LIVE! episodes every Tuesday (around 6pm) wherever you get your favorite pods. Don't forget to like this episode and smash that follow button! 

1 - End of an Era " leaving #crossfit " 2 - What is next for the #fitness industry - current "near death experience"/push versus a connected awareness of your nervous system https://amzn.to/3AaQsL2 3 - / #BTWNtheEars - what it is, how it will help Words we brought up that I love: #intention #awareness #forQuality #movementpractice #psychologicaltolerance #mentaltoughness #belief #faith #injury #identity #ego #rhabdo #redshirt #unknown #unknowable #performance #authenticity #virtuosity #nasalbreathing "Belief is TRUTH without PROOF" 3 camps of #fitnesslifestyle exercise - training - competing Karianne has been in the fitness industry for over 20 years. Her quest has been to learn and discover everything as much as possible about the body, the mind, and human movement. She discovered CrossFit as part of her journey in the fitness industry back in 2008. She went on to open and operate her two gyms (CrossFit Bernardsville and CrossFit Morristown) for 15 years. During her CrossFit tenure she worked as a L1 and L2 seminar staff member, was Dave Castro's assistant, was part of the CrossFit for Hope initiative team and was a regional level athlete. Currently she has embraced a non-dogmatic approach to health and fitness - her pursuit is how to best serve individuals mental and physical health through hers and her husbands business Between the Ears, an in person gym as well as an online event company.

Meta expands support for NFTs on Instagram and Facebook, Art Blocks launches Art Blocks Engine, Rocket Pool upgrades to Redstone, and Specular reveals its EVM-native Optimistic Rollup. Newsletter: https://ethdaily.link/substack

Today on the Ether we have the Cosmos Pot Luck Sunday space with UniverseDAO, hosted by Cosmos HOSS. You'll hear from Jacob Gadikian, Kuhroog of the Cosmos, Iffy.L2, Sean Ames, Jimmy the Otter, and more! Recorded on August 28th 2022. If you enjoy the music at the end of the episodes, you can find the albums streaming on Spotify, and the rest of your favorite streaming platforms. Check out Project Survival, Virus Diaries, and Plan B wherever you get your music. Thank you to everyone in the community who supports TerraSpaces.

Are you wondering: 1. how to seamlessly integrate Matterport + Shopify or Matterport + WooCommerce? 2. how to enhance brand identity, with customized menus, MatterTags and billboards? 3. how to add interactive design elements for marketing events that include gamification, virtual staging or live streaming? Watch WGAN-TV Live at 5 on Thursday, 25 August 2022 when my guests will be: 1. L2VR.co Business Development Kelly Zhang (@l2iot) and 2. L2VR.co General Administration Danny Ng Kelly and Danny will demo and discuss how L2VR.co can help you with their official Matterport Partner eCommerce integrations. If you need custom integration (development) of Matterport + eCommerce, L2vc.co can help you with that as well (and demonstrate a couple of high-end eCommerce integrations showing that! You can sign-up for a 14-day free trial at: www.L2vr.co and/or email: support@L2vr.co Best, Dan --- About L2 (Info Provided by L2) Value-added Service for your Matterport Spaces L2 is a virtual tour solutions provider, dedicated to 3D reality creation and virtual experience application development. L2 provides online and offline solutions, including: ✓ service robot customization ✓ VR/AR applications ✓ tailor-made brand experience ✓ And more! L2 serves users in more than 30 countries. The services provided by L2 include: ✓ 3D panoramic scanning ✓ interactive game experience design ✓ 3D navigation ✓ online location-based services in virtual space ✓ 3D furniture display ✓ service robot integration ✓ user browsing data analysis L2's unique 3D navigation service is applicable for: ✓ large shopping malls ✓ hotels ✓ museums ✓ other large complexes Features of virtual tour also include: ✓ virtual staging ✓ gamification ✓ synchronized guided tour ✓ multi-language audio tour ✓ e-commerce shop integration ✓ 3D space web design customization Please visit L2VR.co for more information and sign up for 14-day Free Trial. L2 is an official Matterport Partner.

Welcome to The Nonlinear Library, where we use Text-to-Speech software to convert the best writing from the Rationalist and EA communities into audio. This is: Basin broadness depends on the size and number of orthogonal features, published by TheMcDouglas on August 27, 2022 on The AI Alignment Forum. TL;DR For neural networks trained to perfect loss, the broadness of optima in parameter space is given by the number and norm of independent orthogonal features the neural network has. The inner product that defines this "feature norm" and independence/orthogonality is the L2 product of Hilbert space. Introduction - why do we care about broadness? Recently, there's been some discussion of what determines the broadness of optima of neural networks in parameter space. People care about this because the size of the optimum basin may influence how easy it is for gradient descent (or other local optimisation algorithms which you might use to train a neural network) to find the corresponding solution, since it's probably easier to stumble across a broader optimum's attractor. People also care about this because there's some hypotheses floating around saying that the broadness of optima is correlated with their generality somehow. The broader the basin of your solution is in parameter space, the more likely it seems to be that the network will successfully generalise to new data in deployment. So understanding what kinds of circuit configurations are broad seems like it might help us grasp better how AIs learn things, and how an AGI might really work internally. Meaning, understanding what kind of solutions are broad is probably relevant to start developing general predictive theories of AI and AI training dynamics, which we'd like to have so we can answer questions like "What goals is my AGI going to develop, given that it has architecture A, and I'm training it with loss function L on data set D?" Measuring broadness Warning: calculus and linear algebra incoming! Say we have a loss function L(f,x,y) for a neural network f(x,Θ), with some data points x and labels y(x), and we've trained the network to perfect loss, setting the parameters to some set ^Θ. L=∑xl(f(x,Θ),y(x))dL(^Θ)dΘ=0 Now, lets try to look at how much the loss changes when we make small changes to the parameters ^Θ. To do this, we're going to perform a polynomial expansion of L up to quadratic order. This isn't going to describe the function behaviour perfectly, but within a small neighbourhood of ^Θ, it'll be mostly accurate. L(Θ)−L(^Θ)=dL(^Θ)dΘ(Θ−^Θ)+(Θ−^Θ)Td2L(^Θ)d2Θ(Θ−^Θ)+O((Θ−^Θ)3)=(Θ−^Θ)Td2L(^Θ)d2Θ(Θ−^Θ)+O((Θ−^Θ)3)=:δΘTd2L^Θ)d2ΘδΘ+O(δΘ3) The first order term vanished because dL(^Θ)dΘ=0 (since we're at an optimum). δΘ:=(Θ−^Θ) is a vector with #params entries, specifying how much we're perturbing each parameter in the network from its value at the optimum ^Θ. d2L(^Θ)d2Θ is going to be a matrix with (#params,#params) entries. So far so good. Now, if we wanted to work out how broad the basin is by looking at this matrix, how would we do it? The matrix is filled with second derivatives. Or in other words, curvatures. If you only had one parameter, this matrix would be a single number (the second derivative), telling you the curvature of the parabola you can fit to the optimum. And the curvature of a parabola determines its broadness, the closer the curvature is to zero, the broader the parabola, and with it the optimum, is. If you have two parameters, you can imagine the optimum as a little valley in the loss function landscape. The valley has two curvatures that characterise it now, but those don't need to line up with our coordinate axes x and y. You could, for example, have one "principal direction" of curvature lie in the (1,1) direction of parameter space, and one in the (1,−1) direction. To find these principal directions and their curvatures, you perform an eigendecomposition of the matrix. The two eigenvalues of the matrix will be the curvatures, and the two e...

Ciao Italiani Veri, rieccoci in compagnia di Davide. Vi è piaciuto il primo episodio? Il secondo è altrettanto affascinante. Davide ci invita ad affrontare il cammino con il giusto allenamento fisico, ma anche con la giusta predisposizione mentale, che non può prescindere dalla consapevolezza della necessaria fatica. Meglio quindi viaggiare leggeri, portando solo l'essenziale. Pronti a partire, amici?

In today's episode we finish our talk about back to school season, and some tips for getting your health journey a fall refresh.

Offchain Labs releases the Arbitrum Nitro white paper, Hetzner prohibits node operators, SpruceID releases TreeLDR, and the EF announces the Merge Data Challenge. Newsletter: https://ethdaily.link/substack

Matteo Giovanetti from Micro-Air joins the HVAC School podcast to talk about the differences between a hard start and an EasyStart. Micro-Air's “EasyStart” provides a soft start rather than a hard start. A hard start abruptly ramps up the voltage and current to the motor start; a soft start is a much gentler start that results from a gradual voltage and current increase on the start AND run windings.  The EasyStart marks a paradigm shift in how we think about “saving” compressors. It attempts to avoid drawing unnecessary inrush current, which is very common with hard starts. Hard starts may even lead to premature failure if the potential relay fails and can't take the start capacitor out of the circuit.  EasyStart has a different wiring configuration compared to hard start kits. A hard start kit consists of a start capacitor wired in series with a potential relay, which increases the torque on the compressor and removes the start capacitor from the circuit. The EasyStart has four wires; the black and white wires (L1 and L2) connect directly to the contactor, a brown wire that splices directly to the run winding, and an orange wire to the HERM terminal of the run capacitor.  EasyStart also records information about the compressor during the first few startups to optimize its performance. It also monitors overcurrent and fault conditions with phase detection; when it detects a stall, it shuts off the compressor and doesn't attempt to restart it until a few minutes have passed. Matteo and Bryan also discuss: EasyStart models Solar, generator, and RV use Impedance Positive temperature coefficient resistors (PTCRs) Compressors running backward EasyStart's Bluetooth capabilities Tech support and product education Offering useful upgrades to customers Running and starting watt specifications for generators   Learn more about EasyStart or purchase it directly from https://www.microair.net/. You can also contact the manufacturer by email at sales@microair.net.  You can view the EasyStart home installation video at https://www.youtube.com/watch?v=bp4U-husy1o&ab_channel=MicroAir.  If you have an iPhone, subscribe to the podcast HERE, and if you have an Android phone, subscribe HERE. Check out our handy calculators HERE.

About MattMatt is a Sr. Architect in Belfast, an AWS DevTools Hero, Serverless Architect, Author and conference speaker. He is focused on creating the right environment for empowered teams to rapidly deliver business value in a well-architected, sustainable and serverless-first way.You can usually find him sharing reusable, well architected, serverless patterns over at cdkpatterns.com or behind the scenes bringing CDK Day to life.Links Referenced: Previous guest appearance: https://www.lastweekinaws.com/podcast/screaming-in-the-cloud/slinging-cdk-knowledge-with-matt-coulter/ The CDK Book: https://thecdkbook.com/ Twitter: https://twitter.com/NIDeveloper TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. One of the best parts about, well I guess being me, is that I can hold opinions that are… well, I'm going to be polite and call them incendiary, and that's great because I usually like to back them in data. But what happens when things change? What happens when I learn new things?Well, do I hold on to that original opinion with two hands at a death grip or do I admit that I was wrong in my initial opinion about something? Let's find out. My guest today returns from earlier this year. Matt Coulter is a senior architect since he has been promoted at Liberty Mutual. Welcome back, and thanks for joining me.Matt: Yeah, thanks for inviting me back, especially to talk about this topic.Corey: Well, we spoke about it a fair bit at the beginning of the year. And if you're listening to this, and you haven't heard that show, it's not that necessary to go into; mostly it was me spouting uninformed opinions about the CDK—the Cloud Development Kit, for those who are unfamiliar—I think of it more or less as what if you could just structure your cloud resources using a programming language you claim to already know, but in practice, copy and paste from Stack Overflow like the rest of us? Matt, you probably have a better description of what the CDK is in practice.Matt: Yeah, so we like to say it's imperative code written in a declarative way, or declarative code written in an imperative way. Either way, it lets you write code that produces CloudFormation. So, it doesn't really matter what you write in your script; the point is, at the end of the day, you still have the CloudFormation template that comes out of it. So, the whole piece of it is that it's a developer experience, developer speed play, that if you're from a background that you're more used to writing a programming language than a YAML, you might actually enjoy using the CDK over writing straight CloudFormation or SAM.Corey: When I first kicked the tires on the CDK, my first initial obstacle—which I've struggled with in this industry for a bit—is that I'm just good enough of a programmer to get myself in trouble. Whenever I wind up having a problem that StackOverflow doesn't immediately shine a light on, my default solution is to resort to my weapon of choice, which is brute force. That sometimes works out, sometimes doesn't. And as I went through the CDK, a couple of times in service to a project that I'll explain shortly, I made a bunch of missteps with it. The first and most obvious one is that AWS claims publicly that it has support in a bunch of languages: .NET, Python, there's obviously TypeScript, there's Go support for it—I believe that went generally available—and I'm sure I'm missing one or two, I think? Aren't I?Matt: Yeah, it's: TypeScript, JavaScript, Python Java.Net, and Go. I think those are the currently supported languages.Corey: Java. That's the one that I keep forgetting. It's the block printing to the script that is basically Java cursive. The problem I run into, and this is true of most things in my experience, when a company says that we have deployed an SDK for all of the following languages, there is very clearly a first-class citizen language and then the rest that more or less drift along behind with varying degrees of fidelity. In my experience, when I tried it for the first time in Python, it was not a great experience for me.When I learned just enough JavaScript, and by extension TypeScript, to be dangerous, it worked a lot better. Or at least I could blame all the problems I ran into on my complete novice status when it comes to JavaScript and TypeScript at the time. Is that directionally aligned with what you've experienced, given that you work in a large company that uses this, and presumably, once you have more than, I don't know, two developers, you start to take on aspects of a polyglot shop no matter where you are, on some level?Matt: Yeah. So personally, I jump between Java, Python, and TypeScript whenever I'm writing projects. So, when it comes to the CDK, you'd assume I'd be using all three. I typically stick to TypeScript and that's just because personally, I've had the best experience using it. For anybody who doesn't know the way CDK works for all the languages, it's not that they have written a custom, like, SDK for each of these languages; it's a case of it uses a Node process underneath them and the language actually interacts with—it's like the compiled JavaScript version is basically what they all interact with.So, it means there are some limitations on what you can do in that language. I can't remember the full list, but it just means that it is native in all those languages, but there are certain features that you might be like, “Ah,” whereas, in TypeScript, you can just use all of TypeScript. And my first inclination was actually, I was using the Python one and I was having issues with some compiler errors and things that are just caused by that process. And it's something that talking in the cdk.dev Slack community—there is actually a very active—Corey: Which is wonderful, I will point out.Matt: [laugh]. Thank you. There is actually, like, an awesome Python community in there, but if you ask them, they would all ask for improvements to the language. So, personally if someone's new, I always recommend they start with TypeScript and then branch out as they learn the CDK so they can understand is this a me problem, or is this a problem caused by the implementation?Corey: From my perspective, I didn't do anything approaching that level of deep dive. I took a shortcut that I find has served me reasonably well in the course of my career, when I'm trying to do something in Python, and you pull up a tutorial—which I'm a big fan of reading experience reports, and blog posts, and here's how to get started—and they all have the same problem, which is step one, “Run npm install.” And that's “Hmm, you know, I don't recall that being a standard part of the Python tooling.” It's clearly designed and interpreted and contextualized through a lens of JavaScript. Let's remove that translation layer, let's remove any weird issues I'm going to have in that transpilation process, and just talk in the language it written in. Will this solve my problems? Oh, absolutely not, but it will remove a subset of them that I am certain to go blundering into like a small lost child trying to cross an eight-lane freeway.Matt: Yeah. I've heard a lot of people say the same thing. Because the CDK CLI is a Node process, you need it no matter what language you use. So, if they were distributing some kind of universal binary that just integrated with the languages, it would definitely solve a lot of people's issues with trying to combine languages at deploy time.Corey: One of the challenges that I've had as I go through the process of iterating on the project—but I guess I should probably describe it for those who have not been following along with my misadventures; I write blog posts about it from time to time because I need a toy problem to kick around sometimes because my consulting work is all advisory and I don't want to be a talking head-I have a Twitter client called lasttweetinaws.com. It's free; go and use it. It does all kinds of interesting things for authoring Twitter threads.And I wanted to deploy that to a bunch of different AWS regions, as it turns out, 20 or so at the moment. And that led to a lot of interesting projects and having to learn how to think about these things differently because no one sensible deploys an application simultaneously to what amounts to every AWS region, without canary testing, and having a phased rollout in the rest. But I'm reckless, and honestly, as said earlier, a bad programmer. So, that works out. And trying to find ways to make this all work and fit together led iteratively towards me discovering that the CDK was really kind of awesome for a lot of this.That said, there were definitely some fairly gnarly things I learned as I went through it, due in no small part to help I received from generous randos in the cdk.dev Slack team. And it's gotten to a point where it's working, and as an added bonus, I even mostly understand what he's doing, which is just kind of wild to me.Matt: It's one of those interesting things where because it's a programming language, you can use it out of the box the way it's designed to be used where you can just write your simple logic which generates your CloudFormation, or you can do whatever crazy logic you want to do on top of that to make your app work the way you want it to work. And providing you're not in a company like Liberty, where I'm going to do a code review, if no one's stopping you, you can do your crazy experiments. And if you understand that, it's good. But I do think something like the multi-region deploy, I mean, with CDK, if you'd have a construct, it takes in a variable that you can just say what the region is, so you can actually just write a for loop and pass it in, which does make things a lot easier than, I don't know, try to do it with a YAML, which you can pass in parameters, but you're going to get a lot more complicated a lot quicker.Corey: The approach that I took philosophically was I wrote everything in a region-agnostic way. And it would be instantiated and be told what region to run it in as an environment variable that CDK deploy was called. And then I just deploy 20 simultaneous stacks through GitHub Actions, which invoke custom runners that runs inside of a Lambda function. And that's just a relatively basic YAML file, thanks to the magic of GitHub Actions matrix jobs. So, it fires off 20 simultaneous processes and on every commit to the main branch, and then after about two-and-a-half minutes, it has been deployed globally everywhere and I get notified on anything that fails, which is always fun and exciting to learn those things.That has been, overall, just a really useful experiment and an experience because you're right, you could theoretically run this as a single CDK deploy and then wind up having an iterate through a list of regions. The challenge I have there is that unless I start getting into really convoluted asynchronous concurrency stuff, it feels like it'll just take forever. At two-and-a-half minutes a region times 20 regions, that's the better part of an hour on every deploy and no one's got that kind of patience. So, I wound up just parallelizing it a bit further up the stack. That said, I bet they are relatively straightforward ways, given the async is a big part of JavaScript, to do this simultaneously.Matt: One of the pieces of feedback I've seen about CDK is if you have multiple stacks in the same project, it'll deploy them one at a time. And that's just because it tries to understand the dependencies between the stacks and then it works out which one should go first. But a lot of people have said, “Well, I don't want that. If I have 20 stacks, I want all 20 to go at once the way you're saying.” And I have seen that people have been writing plugins to enable concurrent deploys with CDK out of the box. So, it may be something that it's not an out-of-the-box feature, but it might be something that you can pull in a community plug-in to actually make work.Corey: Most of my problems with it at this point are really problems with CloudFormation. CloudFormation does not support well, if at all, secure string parameters from the AWS Systems Manager parameter store, which is my default go-to for secret storage, and Secrets Manager is supported, but that also cost 40 cents a month per secret. And not for nothing, I don't really want to have all five secrets deployed to Secrets Manager in every region this thing is in. I don't really want to pay $20 a month for this basically free application, just to hold some secrets. So, I wound up talking to some folks in the Slack channel and what we came up with was, I have a centralized S3 bucket that has a JSON object that lives in there.It's only accessible from the deployment role, and it grabs that at deploy time and stuffs it into environment variables when it pushes these things out. That's the only stateful part of all of this. And it felt like that is, on some level, a pattern that a lot of people would benefit from if it had better native support. But the counterargument that if you're only deploying to one or two regions, then Secrets Manager is the right answer for a lot of this and it's not that big of a deal.Matt: Yeah. And it's another one of those things, if you're deploying in Liberty, we'll say, “Well, your secret is unencrypted at runtime, so you probably need a KMS key involved in that,” which as you know, the costs of KMS, it depends on if it's a personal solution or if it's something for, like, a Fortune 100 company. And if it's personal solution, I mean, what you're saying sounds great that it's IAM restricted in S3, and then that way only at deploy time can be read; it actually could be a custom construct that someone can build and publish out there to the construct library—or the construct hub, I should say.Corey: To be clear, the reason I'm okay with this, from a security perspective is one, this is in a dedicated AWS account. This is the only thing that lives in that account. And two, the only API credentials we're talking about are the application-specific credentials for this Twitter client when it winds up talking to the Twitter API. Basically, if you get access to these and are able to steal them and deploy somewhere else, you get no access to customer data, you get—or user data because this is not charge for anything—you get no access to things that have been sent out; all you get to do is submit tweets to Twitter and it'll have the string ‘Last Tweet in AWS' as your client, rather than whatever normal client you would use. It's not exactly what we'd call a high-value target because all the sensitive to a user data lives in local storage in their browser. It is fully stateless.Matt: Yeah, so this is what I mean. Like, it's the difference in what you're using your app for. Perfect case of, you can just go into the Twitter app and just withdraw those credentials and do it again if something happens, whereas as I say, if you're building it for Liberty, that it will not pass a lot of our Well-Architected reviews, just for that reason.Corey: If I were going to go and deploy this at a more, I guess, locked down environment, I would be tempted to find alternative approaches such as having it stored encrypted at rest via KMS in S3 is one option. So, is having global DynamoDB tables that wind up grabbing those things, even grabbing it at runtime if necessary. There are ways to make that credential more secure at rest. It's just, I look at this from a real-world perspective of what is the actual attack surface on this, and I have a really hard time just identifying anything that is going to be meaningful with regard to an exploit. If you're listening to this and have a lot of thoughts on that matter, please reach out I'm willing to learn and change my opinion on things.Matt: One thing I will say about the Dynamo approach you mentioned, I'm not sure everybody knows this, but inside the same Dynamo table, you can scope down a row. You can be, like, “This row and this field in this row can only be accessed from this one Lambda function.” So, there's a lot of really awesome security features inside DynamoDB that I don't think most people take advantage of, but they open up a lot of options for simplicity.Corey: Is that tied to the very recent announcement about Lambda getting SourceArn as a condition key? In other words, you can say, “This specific Lambda function,” as opposed to, “A Lambda in this account?” Like that was a relatively recent Advent that I haven't fully explored the nuances of.Matt: Yeah, like, that has opened a lot of doors. I mean, the Dynamo being able to be locked out in your row has been around for a while, but the new Lambda from SourceArn is awesome because, yeah, as you say, you can literally say this thing, as opposed to, you have to start going into tags, or you have to start going into something else to find it.Corey: So, I want to talk about something you just alluded to, which is the Well-Architected Framework. And initially, when it launched, it was a whole framework, and AWS made a lot of noise about it on keynote stages, as they are want to do. And then later, they created a quote-unquote, “Well-Architected Tool,” which let's be very direct, it's the checkbox survey form, at least the last time I looked at it. And they now have the six pillars of the Well-Architected Framework where they talk about things like security, cost, sustainability is the new pillar, I don't know, absorbency, or whatever the remainders are. I can't think of them off the top of my head. How does that map to your experience with the CDK?Matt: Yeah, so out of the box, the CDK from day one was designed to have sensible defaults. And that's why a lot of the things you deploy have opinions. I talked to a couple of the Heroes and they were like, “I wish it had less opinions.” But that's why whenever you deploy something, it's got a bunch of configuration already in there. For me, in the CDK, whenever I use constructs, or stacks, or deploying anything in the CDK, I always build it in a well-architected way.And that's such a loaded sentence whenever you say the word ‘well-architected,' that people go, “What do you mean?” And that's where I go through the six pillars. And in Liberty, we have a process, it used to be called SCORP because it was five pillars, but not SCORPS [laugh] because they added sustainability. But that's where for every stack, we'll go through it and we'll be like, “Okay, let's have the discussion.” And we will use the tool that you mentioned, I mean, the tool, as you say, it's a bunch of tick boxes with a text box, but the idea is we'll get in a room and as we build the starter patterns or these pieces of infrastructure that people are going to reuse, we'll run the well-architected review against the framework before anybody gets to generate it.And then we can say, out of the box, if you generate this thing, these are the pros and cons against the Well-Architected Framework of what you're getting. Because we can't make it a hundred percent bulletproof for your use case because we don't know it, but we can tell you out of the box, what it does. And then that way, you can keep building so they start off with something that is well documented how well architected it is, and then you can start having—it makes it a lot easier to have those conversations as they go forward. Because you just have to talk about the delta as they start adding their own code. Then you can and you go, “Okay, you've added these 20 lines. Let's talk about what they do.” And that's why I always think you can do a strong connection between infrastructure-as-code and well architected.Corey: As I look through the actual six pillars of the Well-Architected Framework: sustainability, cost optimization, performance, efficiency, reliability, security, and operational excellence, as I think through the nature of what this shitpost thread Twitter client is, I am reasonably confident across all of those pillars. I mean, first off, when it comes to the cost optimization pillar, please, don't come to my house and tell me how that works. Yeah, obnoxiously the security pillar is sort of the thing that winds up causing a problem for this because this is an account deployed by Control Tower. And when I was getting this all set up, my monthly cost for this thing was something like a dollar in charges and then another sixteen dollars for the AWS config rule evaluations on all of the deploys, which is… it just feels like a tax on going about your business, but fine, whatever. Cost and sustainability, from my perspective, also tend to be hand-in-glove when it comes to this stuff.When no one is using the client, it is not taking up any compute resources, it has no carbon footprint of which to speak, by my understanding, it's very hard to optimize this down further from a sustainability perspective without barging my way into the middle of an AWS negotiation with one of its power companies.Matt: So, for everyone listening, watch as we do a live well-architected review because—Corey: Oh yeah, I expect—Matt: —this is what they are. [laugh].Corey: You joke; we should do this on Twitter one of these days. I think would be a fantastic conversation. Or Twitch, or whatever the kids are using these days. Yeah.Matt: Yeah.Corey: And again, if so much of it, too, is thinking about the context. Security, you work for one of the world's largest insurance companies. I shitpost for a living. The relative access and consequences of screwing up the security on this are nowhere near equivalent. And I think that's something that often gets lost, per the perfect be the enemy of the good.Matt: Yeah that's why, unfortunately, the Well-Architected Tool is quite loose. So, that's why they have the Well-Architected Framework, which is, there's a white paper that just covers anything which is quite big, and then they wrote specific lenses for, like, serverless or other use cases that are shorter. And then when you do a well-architected review, it's like loose on, sort of like, how are you applying the principles of well-architected. And the conversation that we just had about security, so you would write that down in the box and be, like, “Okay, so I understand if anybody gets this credential, it means they can post this Last Tweet in AWS, and that's okay.”Corey: The client, not the Twitter account, to be clear.Matt: Yeah. So, that's okay. That's what you just mark down in the well-architected review. And then if we go to day one on the future, you can compare it and we can go, “Oh. Okay, so last time, you said this,” and you can go, “Well, actually, I decided to—” or you just keep it as a note.Corey: “We pivoted. We're a bank now.” Yeah.Matt: [laugh]. So, that's where—we do more than tweets now. We decided to do microtransactions through cryptocurrency over Twitter. I don't know but if you—Corey: And that ends this conversation. No no. [laugh].Matt: [laugh]. But yeah, so if something changes, that's what the well-architected reviews for. It's about facilitating the conversation between the architect and the engineer. That's all it is.Corey: This episode is sponsored in part by our friend EnterpriseDB. EnterpriseDB has been powering enterprise applications with PostgreSQL for 15 years. And now EnterpriseDB has you covered wherever you deploy PostgreSQL on-premises, private cloud, and they just announced a fully-managed service on AWS and Azure called BigAnimal, all one word. Don't leave managing your database to your cloud vendor because they're too busy launching another half-dozen managed databases to focus on any one of them that they didn't build themselves. Instead, work with the experts over at EnterpriseDB. They can save you time and money, they can even help you migrate legacy applications—including Oracle—to the cloud. To learn more, try BigAnimal for free. Go to biganimal.com/snark, and tell them Corey sent you.Corey: And the lens is also helpful in that this is a serverless application. So, we're going to view it through that lens, which is great because the original version of the Well-Architected Tool is, “Oh, you built this thing entirely in Lambda? Have you bought some reserved instances for it?” And it's, yeah, why do I feel like I have to explain to AWS how their own systems work? This makes it a lot more streamlined and talks about this, though, it still does struggle with the concept of—in my case—a stateless app. That is still something that I think is not the common path. Imagine that: my code is also non-traditional. Who knew?Matt: Who knew? The one thing that's good about it, if anybody doesn't know, they just updated the serverless lens about, I don't know, a week or two ago. So, they added in a bunch of more use cases. So, if you've read it six months ago, or even three months ago, go back and reread it because they spent a good year updating it.Corey: Thank you for telling me that. That will of course wind up in next week's issue of Last Week in AWS. You can go back and look at the archives and figure out what week record of this then. Good work. One thing that I have learned as well as of yesterday, as it turns out, before we wound up having this recording—obviously because yesterday generally tends to come before today, that is a universal truism—is it I had to do a bit of refactoring.Because what I learned when I was in New York live-tweeting the AWS Summit, is that the Route 53 latency record works based upon where your DNS server is. Yeah, that makes sense. I use Tailscale and wind up using my Pi-hole, which lives back in my house in San Francisco. Yeah, I was always getting us-west-1 from across the country. Cool.For those weird edge cases like me—because this is not the common case—how do I force a local region? Ah, I'll give it its own individual region prepend as a subdomain. Getting that to work with both the global lasttweetinaws.com domain as well as the subdomain on API Gateway through the CDK was not obvious on how to do it.Randall Hunt over at Caylent was awfully generous and came up with a proof-of-concept in about three minutes because he's Randall, and that was extraordinarily helpful. But a challenge I ran into was that the CDK deploy would fail because the way that CloudFormation was rendered in the way it was trying to do stuff, “Oh, that already has that domain affiliated in a different way.” I had to do a CDK destroy then a CDK deploy for each one. Now, not the end of the world, but it got me thinking, everything that I see around the CDK more or less distills down to either greenfield or a day one experience. That's great, but throw it all away and start over is often not what you get to do.And even though Amazon says it's always day one, those of us in, you know, real companies don't get to just treat everything as brand new and throw away everything older than 18 months. What is the day two experience looking like for you? Because you clearly have a legacy business. By legacy, I of course, use it in the condescending engineering term that means it makes actual money, rather than just telling really good stories to venture capitalists for 20 years.Matt: Yeah. We still have mainframes running that make a lot of money. So, I don't mock legacy at all.Corey: “What's that piece of crap do?” “Well, about $4 billion a year in revenue. Perhaps show some respect.” It's a common refrain.Matt: Yeah, exactly. So yeah, anyone listening, don't mock legacy because as Corey says, it is running the business. But for us when it comes to day two, it's something that I'm actually really passionate about this in general because it is really easy. Like I did it with CDK patterns, it's really easy to come out and be like, “Okay, we're going to create a bunch of starter patterns, or quickstarts”—or whatever flavor that you came up with—“And then you're going to deploy this thing, and we're going to have you in production and 30 seconds.” But even day one later that day—not even necessarily day two—it depends on who it was that deployed it and how long they've been using AWS.So, you hear these stories of people who deployed something to experiment, and they either forget to delete, it cost them a lot of money or they tried to change it and it breaks because they didn't understand what was in it. And this is where the community starts to diverge in their opinions on what AWS CDK should be. There's a lot of people who think that at the minute CDK, even if you create an abstraction in a construct, even if I create a construct and put it in the construct library that you get to use, it still unravels and deploys as part of your deploy. So, everything that's associated with it, you don't own and you technically need to understand that at some point because it might, in theory, break. Whereas there's a lot of people who think, “Okay, the CDK needs to go server side and an abstraction needs to stay an abstraction in the cloud. And then that way, if somebody is looking at a 20-line CDK construct or stack, then it stays 20 lines. It never unravels to something crazy underneath.”I mean, that's one pro tip thing. It'd be awesome if that could work. I'm not sure how the support for that would work from a—if you've got something running on the cloud, I'm pretty sure AWS [laugh] aren't going to jump on a call to support some construct that I deployed, so I'm not sure how that will work in the open-source sense. But what we're doing at Liberty is the other way. So, I mean, we famously have things like the software accelerator that lets you pick a pattern or create your pipelines and you're deployed, but now what we're doing is we're building a lot of telemetry and automated information around what you deployed so that way—and it's all based on Well-Architected, common theme. So, that way, what you can do is you can go into [crosstalk 00:26:07]—Corey: It's partially [unintelligible 00:26:07], and partially at a glance, figure out okay, are there some things that can be easily remediated as we basically shift that whole thing left?Matt: Yeah, so if you deploy something, and it should be good the second you deploy it, but then you start making changes. Because you're Corey, you just start adding some stuff and you deploy it. And if it's really bad, it won't deploy. Like, that's the Liberty setup. There's a bunch of rules that all go, “Okay, that's really bad. That'll cause damage to customers.”But there's a large gap between bad and good that people don't really understand the difference that can cost a lot of money or can cause a lot of grief for developers because they go down the wrong path. So, that's why what we're now building is, after you deploy, there's a dashboard that'll just come up and be like, “Hey, we've noticed that your Lambda function has too little memory. It's going to be slow. You're going to have bad cold starts.” Or you know, things like that.The knowledge that I have had the gain through hard fighting over the past couple of years putting it into automation, and that way, combined with the well-architected reviews, you actually get me sitting in a call going, “Okay, let's talk about what you're building,” that hopefully guides people the right way. But I still think there's so much more we can do for day two because even if you deploy the best solution today, six months from now, AWS are releasing ten new services that make it easier to do what you just did. So, someone also needs to build something that shows you the delta to get to the best. And that would involve AWS or somebody thinking cohesively, like, these are how we use our products. And I don't think there's a market for it as a third-party company, unfortunately, but I do think that's where we need to get to, that at day two somebody can give—the way we're trying to do for Liberty—advice, automated that says, “I see what you're doing, but it would be better if you did this instead.”Corey: Yeah, I definitely want to spend more time thinking about these things and analyzing how we wind up addressing them and how we think about them going forward. I learned a lot of these lessons over a decade ago. I was fairly deep into using Puppet, and came to the fair and balanced conclusion that Puppet was a steaming piece of crap. So, the solution was that I was one of the very early developers behind SaltStack, which was going to do everything right. And it was and it was awesome and it was glorious, right up until I saw an environment deployed by someone else who was not as familiar with the tool as I was, at which point I realized hell is other people's use cases.And the way that they contextualize these things, you craft a finely balanced torque wrench, it's a thing of beauty, and people complain about the crappy hammer. “You're holding it wrong. No, don't do it that way.” So, I have an awful lot of sympathy for people building platform-level tooling like this, where it works super well for the use case that they're in, but not necessarily… they're not necessarily aligned in other ways. It's a very hard nut to crack.Matt: Yeah. And like, even as you mentioned earlier, if you take one piece of AWS, for example, API Gateway—and I love the API Gateway team; if you're listening, don't hate on me—but there's, like, 47,000 different ways you can deploy an API Gateway. And the CDK has to cover all of those, it would be a lot easier if there was less ways that you could deploy the thing and then you can start crafting user experiences on a platform. But whenever you start thinking that every AWS component is kind of the same, like think of the amount of ways you're can deploy a Lambda function now, or think of the, like, containers. I'll not even go into [laugh] the different ways to run containers.If you're building a platform, either you support it all and then it sort of gets quite generic-y, or you're going to do, like, what serverless cloud are doing though, like Jeremy Daly is building this unique experience that's like, “Okay, the code is going to build the infrastructure, so just build a website, and we'll do it all behind it.” And I think they're really interesting because they're sort of opposites, in that one doesn't want to support everything, but should theoretically, for their slice of customers, be awesome, and then the other ones, like, “Well, let's see what you're going to do. Let's have a go at it and I should hopefully support it.”Corey: I think that there's so much that can be done on this. But before we wind up calling it an episode, I had one further question that I wanted to explore around the recent results of the community CDK survey that I believe is a quarterly event. And I read the analysis on this, and I talked about it briefly in the newsletter, but it talks about adoption and a few other aspects of it. And one of the big things it looks at is the number of people who are contributing to the CDK in an open-source context. Am I just thinking about this the wrong way when I think that, well, this is a tool that helps me build out cloud infrastructure; me having to contribute code to this thing at all is something of a bug, whereas yeah, I want this thing to work out super well—Docker is open-source, but you'll never see me contributing things to Docker ever, as a pull request, because it does, as it says on the tin; I don't have any problems that I'm aware of that, ooh, it should do this instead. I mean, I have opinions on that, but those aren't pull requests; those are complete, you know, shifts in product strategy, which it turns out is not quite done on GitHub.Matt: So, it's funny I, a while ago, was talking to a lad who was the person who came up with the idea for the CDK. And CDK is pretty much the open-source project for AWS if you look at what they have. And the thought behind it, it's meant to evolve into what people want and need. So yes, there is a product manager in AWS, and there's a team fully dedicated to building it, but the ultimate aspiration was always it should be bigger than AWS and it should be community-driven. Now personally, I'm not sure—like you just said it—what the incentive is, given that right now CDK only works with CloudFormation, which means that you are directly helping with an AWS tool, but it does give me hope for, like, their CDK for Terraform, and their CDK for Kubernetes, and there's other flavors based on the same technology as AWS CDK that potentially could have a thriving open-source community because they work across all the clouds. So, it might make more sense for people to jump in there.Corey: Yeah, I don't necessarily think that there's a strong value proposition as it stands today for the idea of the CDK becoming something that works across other cloud providers. I know it technically has the capability, but if I think that Python isn't quite a first-class experience, I don't even want to imagine what other providers are going to look like from that particular context.Matt: Yeah, and that's from what I understand, I haven't personally jumped into the CDK for Terraform and we didn't talk about it here, but in CDK, you get your different levels of construct. And is, like, a CloudFormation-level construct, so everything that's in there directly maps to a property in CloudFormation, and then L2 is AWS's opinion on safe defaults, and then L3 is when someone like me comes along and turns it into something that you may find useful. So, it's a pattern. As far as I know, CDK for Terraform is still on L1. They haven't got the rich collection—Corey: And L4 is just hiring you as a consultant—Matt: [laugh].Corey: —to come in fix my nonsense for me?Matt: [laugh]. That's it. L4 could be Pulumi recently announced that you can use AWS CDK constructs inside it. But I think it's one of those things where the constructs, if they can move across these different tools the way AWS CDK constructs now work inside Pulumi, and there's a beta version that works inside CDK for Terraform, then it may or may not make sense for people to contribute to this stuff because we're not building at a higher level. It's just the vision is hard for most people to get clear in their head because it needs articulated and told as a clear strategy.And then, you know, as you said, it is an AWS product strategy, so I'm not sure what you get back by contributing to the project, other than, like, Thorsten—I should say, so Thorsten who wrote the book with me, he is the number three contributor, I think, to the CDK. And that's just because he is such a big user of it that if he sees something that annoys him, he just comes in and tries to fix it. So, the benefit is, he gets to use the tool. But he is a super user, so I'm not sure, outside of super users, what the use case is.Corey: I really want to thank you for, I want to say spending as much time talking to me about this stuff as you have, but that doesn't really go far enough. Because so much of how I think about this invariably winds up linking back to things that you have done and have been advocating for in that community for such a long time. If it's not you personally, just, like, your fingerprints are all over this thing. So, it's one of those areas where the entire software developer ecosystem is really built on the shoulders of others who have done a lot of work that came before. Often you don't get any visibility of who those people are, so it's interesting whenever I get to talk to someone whose work I have directly built upon that I get to say thank you. So, thank you for this. I really do appreciate how much more straightforward a lot of this is than my previous approach of clicking in the console and then lying about it to provision infrastructure.Matt: Oh, no worries. Thank you for the thank you. I mean, at the end of the day, all of this stuff is just—it helps me as much as it helps everybody else, and we're all trying to do make everything quicker for ourselves, at the end of the day.Corey: If people want to learn more about what you're up to, where's the best place to find you these days? They can always take a job at Liberty; I hear good things about it.Matt: Yeah, we're always looking for people at Liberty, so come look up our careers. But Twitter is always the best place. So, I'm @NIDeveloper on Twitter. You should find me pretty quickly, or just type Matt Coulter into Google, you'll get me.Corey: I like it. It's always good when it's like, “Oh, I'm the top Google result for my own name.” On some level, that becomes an interesting thing. Some folks into it super well, John Smith has some challenges, but you know, most people are somewhere in the middle of that.Matt: I didn't used to be number one, but there's a guy called the Kangaroo Kid in Australia, who is, like, a stunt driver, who was number one, and [laugh] I always thought it was funny if people googled and got him and thought it was me. So, it's not anymore.Corey: Thank you again for, I guess, all that you do. And of course, taking the time to suffer my slings and arrows as I continue to revise my opinion of the CDK upward.Matt: No worries. Thank you for having me.Corey: Matt Coulter, senior architect at Liberty Mutual. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice and leave an angry comment as well that will not actually work because it has to be transpiled through a JavaScript engine first.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

Nethermind, Geth, and Teku, release merge ready clients, BendDAO suffers a liquidity crisis, Gemini launches staking services, and Layerswap introduces a L2 off-ramp. Newsletter: ethdaily.substack.com

In today's episode Becky and I talk about back to school season, and some tips for getting your health journey a fall refresh.

How can we keep space safe? Neil deGrasse Tyson and comic-environmentalist co-host Matt Winning learn about the space industry and how we can keep debris out of orbit with aerospace engineers Jenna Tiwana and Danielle Wood, with words from Steve Wozniak. NOTE: StarTalk+ Patrons can watch or listen to this entire episode commercial-free here: https://startalkmedia.com/show/space-sustainability-with-steve-wozniak-guests/Thanks to our Patrons Sub Zero, Maury, Harrison Wilcox, Jim Langner, and JAYME HATTERSLEY for supporting us this week.Photo Credit: NOIRLab/NSF/AURA/P. Marenfeld, CC BY 4.0, via Wikimedia Commons

In the 19th installment of our 2022 32-Beats series, Jesse Marshall joins Ben to break down the 2021/22 Penguins season and discuss what we can expect in 2022/23. Topics discussed include: The Penguins' cup chances in 2023 after running it back Sidney Crosby's evolving game and how it stands to age The importance of Jake Guentzel Bryan Rust vs. Rickard Rakell on L1 How Evgeni Malkin disrupts defenses by going against the grain Which middle six winger should get the shot to play on L2 with Malkin? Why is Evan Rodrigues still a UFA? Kris Letang's rennaissance Jeff Petry's fit on his new club The Ty Smith reclamation project Can Tristan Jarry prove he's a consistent starting goalie? The Penguins' meagre prospect pipeline And more!! Make sure to follow Jesse on Twitter @jmarshfof and check out all of his articles on The Athletic. Want to stay up to date on all the latest NHL line combos and fantasy news? Follow our @GameDayLines, @GameDayNewsNHL, and @GameDayGoalies accounts on Twitter to know what you need to know as soon as you can know it. Plus, visit GameDayLineTweets.com to see line combo tweets sorted by NHL team! For more amazing fantasy content, subscribe to The Stream Scheme, highlighting the best free agency finds and fantasy schedules of the week. We always invite and appreciate your feedback. Let us know what you think @keepingkarlsson, and if you love the show, please rate and write us a five-star review on Apple Podcasts. * * * Join our inclusive, passionate and brilliant Keeping Karlsson community by becoming a patron of Keeping Karlsson. For the cost of one arena soft pretzel each month, patrons help us keep making new episodes and get all kinds of perks in return, like managing teams in the Keeping Karlsson Ultimate Patron Fantasy League (aka the KKUPFL), access to our patrons-only Discord Server, bonus monthly Patroncasts, and weekly show scripts. Keeping Karlsson is proudly presented by DobberHockey. Learn more about your ad choices. Visit podcastchoices.com/adchoices

SUBSCRIBE YOUTUBE: https://www.youtube.com/watch?v=KZjnnM-l2Mo&t=8s SUBSCRIBE: availableon.com/between2layers Welcome to the inaugural episode of Between 2 Layers - Carly's new podcast centered on L2 blockchains, co-hosted by Immutable X co-founder and president, Robbie Ferguson. In this episode, the two talk all things Immutable X and layer 2:  The early bet IMX made that set them apart from their competitors  the Immutable business model - and why it's designed to help all layer 2 ecosystems  Carbon neutrality The impact of blockchain gaming on indie game developers  If you are buying ether, you're making a bet on L2 - tune in make sure you understand that bet!

Episode #85:  What happens when you go on an amazing THM themed girls trip to Nashville and the air conditioning goes out in the mini-van?  Listen in to find out.  

Gloria Zhao, Bitcoin core contributor and maintainer, rejoins me on the show to chat about what bitcoin core maintainers do. We discuss: What do Bitcoin Core maintainers do? How does Bitcoin Core development work? How much ‘power' do maintainers have? Mempools - what are they and why do we need them? Interaction with L2 protocols Mempool package relay RBF Links: Twitter: @glozow Package Relay Proposal Site mentioned: Bitcoin Core PR Review Club Github: glozow Brink: @bitcoinbrink Bitcoin Core PR Reviews: @BitcoinCorePRs SLP216 Gloria Zhao Learning Bitcoin Core Contribution & Hosting PR Review Club SLP242 Jonas Schnelli Maintaining Bitcoin Core: Contributions, Consensus, Conflict Sponsors: Swan Bitcoin Mempool.space Braiins.com Voltage Unchained Capital (code LIVERA) CoinKite.com(code LIVERA)