剃须刀到底应该怎么清洗

duck2: 胡子长得快，一不注意，电动的就不好处理了，经常用手动的，特意入手了这个吉列极光刀，用是挺好用，但是实在不好清洗，手动的这种剃须刀到底应该怎么清洗，试过水冲，水泡，类似卡针的东西戳，都不理想，大家有什么好办法请教下

Read More

终于发现了一个符合我需求的摄影博客项目， exif-photo-blog

charexcalibur: 项目地址: https://github.com/sambecker/exif-photo-blog

我的部署： https://photo.axis-studio.org/

vercel 一键部署，很方便

功能：
- Built-in auth
- Photo upload with EXIF extraction
- Organize photos by tag
- Infinite scroll
- Light/dark mode
- Automatic OG image generation
- CMD-K menu with photo search
- AI-generated text descriptions
- Support for Fujifilm recipes and film simulations

Read More

苹果股价连续反弹 市场在押注iPhone获得关税豁免吗？

“90%的投资者都相信苹果将获得关税豁免”，毕竟，苹果在特朗普1.0时期就获得过一次豁免。华尔街认为，“美国优先”政策指引下，特朗普可能不会希望伤害像苹果这样的美国标志性企业，特别是在该公司承诺未来四年在美国投资5000亿美元之后。

关税豁免预期升温，苹果股价反弹。特朗普关税大棒落地后，苹果股价经历了一波暴跌，但在过去两天，意外出现了剧烈反弹。苹果股价自4月9日以来飙升了15%，市值增加4000多亿美元，本周五股价单日上涨4.1%，收于198.15美元。


这一反弹源自华尔街分析师和投资者越来越相信苹果将获得关税豁免，这一预期已成为支撑股价的关键因素。

CFRA Research分析师Angelo Zino表示，苹果获得豁免的可能性已经显著增加：

“按目前情况，关税影响对苹果来说尤为严重，潜在增加其销售成本约500亿美元。”

“我们预计苹果会推迟将任何关税成本转嫁给消费者，直到秋季产品周期，同时如果贸易协议短期内无法实现，我们将苹果获得特殊豁免的概率从20%提高到50%。”

Mizuho Securities交易台分析师Jordan Klein的观点更为乐观，他表示与之交谈的投资者都坚信特朗普将向苹果提供豁免：

“90%的投资者似乎相信苹果将获得关税豁免，毕竟该公司在2018年特朗普执政期间就获得过一次豁免。”

美国就业与政治考量支撑豁免可能

在当前地缘政治紧张局势下，苹果独特的地位可能成为其获得特殊待遇的关键。

分析师们指出，特朗普不会希望伤害像苹果这样的美国标志性企业，特别是在该公司承诺未来四年在美国制造业和其他国内投资上支出超过5000亿美元之后。

Jordan Klein强调：

“该公司雇佣了太多人，美国选民过度依赖iPhone，不会接受iPhone售价达到2000美元的情况。”

另一个支持苹果获得豁免的论点是，特朗普的关税政策可能反而助力了苹果的主要竞争对手——韩国的三星电子。从政治角度看，这种结果显然与特朗普的“美国优先”政策相悖。

苹果并非完全依赖豁免，已开始多管齐下应对

尽管市场普遍看好苹果获得豁免的前景，但该公司并未将所有希望寄托于此。

摩根士丹利分析师Erik Woodring表示：

“我们不认为苹果将仅仅押注于总统豁免，而且正如我们在跟踪该公司时所了解的，苹果始终保持长期思考。”

苹果近年来一直致力于将其产业链多元化，包括将部分iPhone生产转移到印度。在90天关税缓期内，苹果可能将寻求其印度合作伙伴，以满足美国iPhone需求。

Woodring估计，为满足美国的iPhone需求，苹果需要将其印度生产能力提高一倍，尽管这可能需要更长时间才能实现。

还有观点指出，另一种策略是通过提供融资计划、增加运营商补贴和提高以旧换新价值来缓解人为抬高的iPhone价格。

如果无法获得豁免，苹果可能会采取其他策略减轻关税压力。大摩分析称，苹果可能会取消低端iPhone存储模型，将需求转向利润率更高的iPhone型号。

Read More

刘强东回应美团高管王莆中：不打口水仗，产生不了社会价值

今日下午，京东集团新闻发言人齐珊珊在朋友圈发布了与京东集团创始人刘强东的内网对话，并表示：“又上了一课，踏实做事，努力创造社会价值。”据其朋友圈截图显示，刘强东本人得知今日早间王莆中的言论回应称：要是有空就赶紧去加入“小哥应急小组”，看看有没有外卖或者快递兄弟在大风中遇到困难的！或者去参与出口受阻企业的采购小组工作，尽快给他们提供帮助。

此外，刘强东还表示，“不要和人打口仗，不能产生社会价值。”

今日早间，美团核心本地商业CEO王莆中在社交媒体上言词激烈，火药味十足地发文炮轰京东，其称京东不是第一家想做外卖的公司，也可能不是最后一家，“阿里、滴滴、字节不是都做过，滴滴目前在海外也还在做呢。”

值得注意的是，近日，据晚点LatePost报道，京东集团SEC副主席、京东集团CEO许冉透露，“百亿补贴上线后，单量增长很迅速，京东外卖的餐饮日订单量预计下周（4 月 14 日这周）即将突破 500 万单，这个速度远远快于预期。”



附美团核心本地商业CEO王莆中发声全文：

有朋友问我怎么看京东做外卖，还有明显的人邀请我回答：）

我简单说几句：

1、京东不是第一家尝试外卖的公司，也可能不是最后一家。阿里、滴滴、字节不是都成员，滴滴目前在海外也还在做呢。

2、如果把外卖现即时零售（30分钟送东西）的一部分来说，达达和京东到家早在2014年就开始了，只不过收效甚微。据媒体报道：达达集团疑虚报数据带业务崩盘京东亏损无解、央出走、核心早已知道了。finance.sina.com.cn

3、即时零售这几年的发展如火如荼，大家都有目共睹；尤其是在生鲜、酒饮、3c数码、药品……等品类的进展速度远超预期，美团非餐饮品类的订单突破了1800万单，说让某些公司如鲠在喉，如芒在背。

4、我们原定在下周正式发布美团即时零售品牌，这在媒体圈不是秘密，发布前很可能还会有各种干扰出来。不过即时零售的发展大势是挡不住的，“狗跳墙”也好，“围魏救赵”也罢，“30分钟送万物”创造的新体验一定会满足更多用户的需要，把那些大而无当的仓配体系扫进历史垃圾堆。


Read More

A Fresh Take On Virtual Swap Space Being Pursued For The Linux Kernel

A request for comments (RFC) patch series sent out this week for the Linux kernel is working on the notion of Virtual Swap Space support. The notion of Virtual Swap Space has been talked about for years and even going back to 2011 there's been efforts to redesign the kernel's swap cache along similar lines.

This latest work on Virtual Swap Space for Linux was posted by open-source developer Nhat Pham and is currently deemed a prototype implementation. With this new code the focus is on decoupling Zswap from the backing swap file as well as simplifying/optimizing Swapoff behavior. Additionally, this code could help out for scenarios around multi-tier swapping, swapfile compaction, and other functionality.

Nhat Pham explains of this work on Virtual Swap Space for Linux:
"This RFC implements the virtual swap space idea, based on Yosry's proposals at LSFMMBPF 2023, as well as valuable
inputs from Johannes Weiner. The same idea (with different implementation details) has been floated by Rik van Riel since at least
2011.

The code attached to this RFC is purely a prototype. It is not 100% merge-ready. I do, however, want to show people this prototype/RFC, including all the bells and whistles and a couple of actual use cases, so that folks can see what the end results will look like, and give me early feedback :)

I. Motivation

Currently, when an anon page is swapped out, a slot in a backing swap device is allocated and stored in the page table entries that refer to the original page. This slot is also used as the "key" to find the swapped out content, as well as the index to swap data structures, such as the swap cache, or the swap cgroup mapping. Tying a swap entry to its backing slot in this way is performant and efficient when swap is purely just disk space, and swapoff is rare.

However, the advent of many swap optimizations has exposed major drawbacks of this design. The first problem is that we occupy a physical slot in the swap space, even for pages that are NEVER expected to hit the disk: pages compressed and stored in the zswap pool, zero-filled pages, or pages rejected by both of these optimizations when zswap writeback is disabled. This is the arguably central shortcoming of zswap:

* In deployments when no disk space can be afforded for swap (such as mobile and embedded devices), users cannot adopt zswap, and are forced to use zram. This is confusing for users, and creates extra burdens for developers, having to develop and maintain similar features for two separate swap backends (writeback, cgroup charging, THP support, etc.).

* Resource-wise, it is hugely wasteful in terms of disk usage, and limits the memory saving potentials of these optimizations by the static size of the swapfile, especially in high memory systems that can have up to terabytes worth of memory. It also creates significant challenges for users who rely on swap utilization as an early OOM signal.

Another motivation for a swap redesign is to simplify swapoff, which is complicated and expensive in the current design. Tight coupling between a swap entry and its backing storage means that it requires a whole page table walk to update all the page table entries that refer to this swap entry, as well as updating all the associated swap data structures (swap cache, etc.).
...
This design allows us to:
* Decouple zswap (and zeromapped swap entry) from backing swapfile: simply associate the virtual swap slot with one of the supported backends: a zswap entry, a zero-filled swap page, a slot on the swapfile, or an in-memory page.

* Simplify and optimize swapoff: we only have to fault the page in and have the virtual swap slot points to the page instead of the on-disk physical swap slot. No need to perform any page table walking.
...
Other than decoupling swap backends and optimizing swapoff, this new design allows us to implement the following more easily and efficiently:

* Multi-tier swapping, with transparent transferring (promotion/demotion) of pages across tiers. Similar to swapoff, with the old design we would need to perform the expensive page table walk.

* Swapfile compaction to alleviate fragmentation (as proposed by Ying Huang).

* Mixed backing THP swapin: Once you have pinned down the backing store of THPs, then you can dispatch each range of subpages to appropriate swapin handle.

* Swapping a folio out with discontiguous physical swap slots"

Those wanting to learn more about this prototype work on Virtual Swap Space for Linux can see this RFC patch series for all the details.

Read More