当前位置:首页>Linux>Linux 现在已足够好;一个摧毁所有网站的网站;用户无法直接创建 Issues 的原因

Linux 现在已足够好;一个摧毁所有网站的网站;用户无法直接创建 Issues 的原因

  • 2026-02-07 05:34:22
Linux 现在已足够好;一个摧毁所有网站的网站;用户无法直接创建 Issues 的原因

2026-01-03 Hacker News Top Stories

1. Linux 现在已足够好 (I'm brave enough to say it: Linux is good now — and if you want to feel like you actually own your PC, make 2026 the year of Linux on your desktop)

https://www.pcgamer.com/software/linux/im-brave-enough-to-say-it-linux-is-good-now-and-if-you-want-to-feel-like-you-actually-own-your-pc-make-2026-the-year-of-linux-on-your-desktop/

作者回顾了 2025 年在多台设备上使用 Linux 的积极体验,称现代 Linux 已在游戏兼容性、驱动支持和用户控制权方面大幅改进,推荐像 Bazzite 这样的开箱即用发行版,并指出旧电脑可作为稳定的媒体服务器或多座位游戏机。尽管 HDR 支持和部分反作弊仍有问题,但整体已足够成熟,值得在 2026 年考虑从 Windows 转向 Linux,重获对自己电脑的掌控感。

HN 热度 1126 points | 评论 923 comments | 作者:Vinnl | 1 day ago

  • • 使用 Linux 后,系统稳定性与性能明显优于 Windows,且无广告和预装软件干扰,游戏兼容性良好,仅 Battlefield 和 League of Legends 因反作弊机制无法运行。
  • • 通过 SystemD 实现多用户多座位配置,利用旧显卡和声卡为孩子提供独立游戏环境,成本低且灵活,适合家庭 LAN 房间搭建。
  • • 多座位系统需注意显卡驱动兼容性,建议使用相同驱动的显卡,避免驱动冲突问题。
  • • 单一显卡多输出虽理论上可行,但实际操作受限,仍推荐使用独立显卡实现多座位。
  • • 多座位系统具备高容错性,硬件升级时仅影响单个座位,不影响整体使用,提升系统可用性。

2. 一个摧毁所有网站的网站 (A website to destroy all websites)

https://henry.codes/writing/a-website-to-destroy-all-websites/

文章认为互联网已从早期赋能个体的多样化天地,演变为由少数平台和算法控制的注意力农场,导致内容同质化与精神贫乏。作者以汽车工业为喻,说明技术常由“初期增益”转向“后期剥削”,并呼吁重建可被掌控、以人为本的数字工具与去中心化的网络文化,使技术重新服务于人的成长、创造与尊严。

HN 热度 750 points | 评论 369 comments | 作者:g0xA52A2A | 1 day ago

  • • 该网站的设计初衷是创造具有个性和艺术感的网络体验,但部分用户因不适应其设计而抱怨,反映出评论者自身对设计的偏好与网站目标之间的冲突。
  • • 网站的视觉风格让人联想到美术馆或艺术展览,具有浓厚的复古杂志感,体现了对传统出版美学的致敬与现代网页技术的结合。
  • • 部分用户在桌面宽屏上浏览时发现布局混乱、图片与文字重叠,而移动端或竖屏设备上则呈现更理想的效果,说明网站的响应式设计存在设备适配问题。
  • • 有观点指出,部分批评者因关闭 JavaScript 而无法正常浏览内容,进而否定整个作品,这种以自身技术限制为标准来评判创作的做法并不合理。
  • • 一些用户认为网站过于强调视觉表现,可能对中老年人或视力不佳者不够友好,字体过小、缺乏可调性,影响可读性。

3. 用户无法直接创建 Issues 的原因 (Why users cannot create Issues directly)

https://github.com/ghostty-org/ghostty/issues/3558

该项目要求用户先在 Discussions 发起问题讨论,维护者会在问题被确认为明确且可复现后再转为正式的 Issue。此做法旨在过滤因使用误解、环境或配置问题造成的“非 bug”报告,以及模糊的功能请求,从而提高维护效率。项目提供了 CONTRIBUTING.md 供参考,确认后自动转为 Issue,无需用户额外操作。

HN 热度 713 points | 评论 265 comments | 作者:xpe | 24 hours ago

  • • 用户提交问题时缺乏基本的沟通素养,常忽略关键信息如错误提示内容,导致问题难以复现和解决。
  • • 即使是技术背景的用户,面对错误信息时也可能完全无法理解或采取有效行动,表现出对计算机提示的“语言失能”。
  • • 错误信息应设计得更友好,提供清晰的用户语言描述和可追踪的错误编号,以辅助用户自助排查。
  • • 一些系统设计本身存在问题,例如云服务的公开 IP 返回 403 错误,误导用户误判为网络问题,加剧了误解。
  • • 将错误信息的收集流程简化,如通过“上传支持”按钮自动收集日志,能显著提升问题反馈效率。

4. 我是大型食品外卖平台的工程师 (I'm a developer for a major food delivery app)

https://news.ycombinator.com/item?id=46461563

一名前后端工程师在离职后揭露公司内部操作:优先配送费和司机福利费被公司截留,派单和运价通过算法被操控以榨取更多利润;平台用“绝望分”等信号屏蔽穷司机的高价单;通过预测小费动态压低基础运费,使乘客的高额小费反而成了公司省钱的手段。作者因良心不安辞职,呼吁监管与公众关注平台对司机与消费者的剥削性设计。

HN 热度 573 points | 评论 275 comments | 作者:apayan | 20 hours ago

  • • 工程师在工作中常被系统性地隔绝于真实用户的影响之外,公司通过 KPI、敏捷会议和术语设计,使工程师难以思考其技术对人的实际影响。
  • • 一些工程师在开发 AI 系统时,仅关注算法效率和数据优化,完全忽视其对人类员工或用户可能造成的负面影响,甚至提出用 AI 评估员工绩效以决定裁员。
  • • 有工程师承认自己曾产生过用计算机监控和控制人类行为的念头,虽然意识到这种想法的不道德,但部分同事因不直接影响自身而对此无感。
  • • 银行等金融机构存在设计上不利于客户的机制,例如信用卡若全额还款需支付额外费用,这实质上是通过制度设计鼓励客户长期负债以获取利息收益。
  • • 企业中的“邪恶”并非源于极端恶行,而是由日常的管理流程、术语包装和系统性脱敏机制逐步构建而成,其根源在于办公室中的“理性”决策。

5. 相机与镜头(2020) (Cameras and Lenses (2020))

https://ciechanow.ski/cameras-and-lenses/

本文由 Bartosz Ciechanowski 撰写,通过交互式模拟介绍相机成像原理:感光像素如何将光子转为电信号、拜耳滤镜和去马赛克重建彩色图像、针孔相机如何通过限制入射方向形成清晰倒置像,以及针孔大小与孔到传感器距离对清晰度与视角的影响,最后引出镜头替代针孔以提升成像质量。

HN 热度 529 points | 评论 57 comments | 作者:sebg | 1 day ago

  • • 这个网站的交互体验让人怀念 Adobe Flash 时代的网页乐趣,尽管技术上不完全可比,但情感共鸣强烈。
  • • Flash 应用可以打包为独立的 SWF 文件,而现代动态网页难以实现长期保存,存在未来无法访问的风险。
  • • 使用 Browsertrix 等工具可以有效存档这类动态网站,导出为.wacz 格式,具有较好的长期保存潜力。
  • • 虽然静态网站容易存档,但高度动态的前端网页因依赖大量 JavaScript 和浏览器特性,存档难度大。
  • • 网站虽看似动态,实则为静态网站,但部分存档工具无法正确保留交互功能。

6. FracturedJson:一种兼顾可读性与紧凑性的 JSON 格式化工具 (FracturedJson)

https://github.com/j-brooke/FracturedJson/wiki

FracturedJson 是一套在可读性与紧凑性之间取得平衡的 JSON 格式化工具。它倾向于将简单结构的对象与数组压缩为单行、对相似结构对齐字段、保留注释并提供丰富配置(如单行最大嵌套深度、行宽等)。该项目已实现多语言移植并发布为 Rust CLI,可与数据驱动和变异测试结合以确保不同实现间行为一致。

HN 热度 502 points | 评论 136 comments | 作者:PretzelFisch | 13 hours ago

  • • 构建一个跨语言的统一测试套件是确保 FracturedJson 多语言实现行为一致性的理想方式,有助于未来扩展更多语言支持。
  • • 一个全面的数据驱动测试套件能极大提升不同实现间的兼容性与可维护性,接近实际意义上的功能等价。
  • • 通过变异测试(mutation testing)可确保代码中所有分支路径都被覆盖,从而增强对实现正确性的信心。
  • • FracturedJson 是纯函数式操作,非常适合编写自动化测试框架,便于验证其行为一致性。
  • • 已将 FracturedJson 移植至 Rust 并发布为 CLI 工具,支持格式化、注释处理、换行控制等多种选项。

7 HPV 疫苗使丹麦致癌型 HPV16/18 感染率从 16% 降至 1% 以下 (HPV vaccination reduces oncogenic HPV16/18 prevalence from 16% to <1% in Denmark)

https://www.eurosurveillance.org/content/10.2807/1560-7917.ES.2025.30.27.2400820

该研究(或报道)指出,丹麦接种 HPV 疫苗后,致癌型 HPV16/18 的检出率从约 16% 下降到不足 1%,显示疫苗在预防高危型 HPV 感染上具有显著群体效应。该结果支持广泛接种计划可大幅降低相关癌症风险,并强调男女均应考虑接种以实现更好的群体免疫与传播阻断。注意:原始网页当前处于 Cloudflare 验证页面,无法直接读取全文;以上摘要基于题目与公开讨论信息。

HN 热度 498 points | 评论 259 comments | 作者:stared | 15 hours ago

  • • HPV 非常普遍,80% 的男性和 90% 的女性一生中至少会感染一种类型,除非完全禁欲,否则极有可能感染。
  • • HPV 不仅通过性行为传播,也可能通过皮肤接触传播,即使没有性行为也存在感染风险。
  • • HPV 感染通常无症状,多数人感染后会自然清除,但部分高危型别可能持续存在并导致癌症。
  • • 疫苗接种年龄上限为 45 岁,对成年人仍有保护作用,不应因年龄或性别而忽视接种。
  • • 男性接种疫苗不仅保护自身,还能减少对女性的传播,对公共卫生具有重要意义。

8. 芬兰扣押涉嫌损坏赫尔辛基-塔林海底电缆的货轮及船员 (Finland detains ship and its crew after critical undersea cable damaged)

https://www.cnn.com/2025/12/31/europe/finland-estonia-undersea-cable-ship-detained-intl

2025年12月31日,芬兰以直升机行动扣押了疑在芬兰或爱沙尼亚海域损坏赫尔辛基—塔林海底通信电缆的货轮Fitburg及其14名船员。警方称该船在芬兰水域下放锚链,事件导致由Elisa运营的电缆部分故障,另一条由Arelion运营的电缆亦受损但未中断服务。案件以“加重刑事破坏”等罪名调查,事件激起对俄罗斯可能涉入的担忧,促使芬兰与爱沙尼亚加强合作应对。

HN 热度 480 points | 评论 642 comments | 作者:wslh | 1 day ago

  • • 芬兰和 Estonia 在 1990 年代出于对俄罗斯的善意,限制了其在波罗的海的领海主张,但俄罗斯并未以善意回应,这种做法已不再合理。
  • • 若将该水域划为海峡,俄罗斯将获得更大通行权,反而不利于防范其破坏行为,因此当前的领海安排实际上限制了俄罗斯的合法权利。
  • • 当前的国际法框架为俄罗斯提供了可被滥用的漏洞,使其能以“无害通过”为名实施破坏活动,而芬兰和 Estonia 应重新评估现有协议以增强执法能力。
  • • 欧洲实际上已处于与俄罗斯的战争状态,尽管形式是非动能的,但包括网络攻击、破坏基础设施、海上袭击等,战争已真实发生。
  • • 有人指出,破坏海底电缆的行为显然不属于“无害通过”,因此该船被扣押是合法且必要的,表明国际法仍可有效应对恶意行为。

9. 十年个人财务的纯文本文件记录 (10 years of personal finances in plain text files)

https://sgoel.dev/posts/10-years-of-personal-finances-in-plain-text-files/

作者记录了自 2016 年起用 Beancount 管理个人财务的十年实践:每月花 30–45 分钟将银行 CSV 导入到纯文本账本,现有 ~10,000 笔交易、1086 个账户,数据以按年拆分的 16 个文本文件存储并通过 include 整合,配合自建 Python importer 自动化导入德国多家银行数据,提升税务和审计效率,强调 Plain Text Accounting 的长期可读性与可控性。

HN 热度 429 points | 评论 166 comments | 作者:wrxd | 14 hours ago

  • • 双-entry accounting 的核心在于资金流动的追踪,通过图论视角能更直观地理解账户间的资金流向。
  • • 初学者常困惑于为何一笔交易要拆分为两个账户记录,实际是为了确保资金来源与去向的平衡,而非简单地“多记一笔”。
  • • 传统单-entry 系统(如 Quicken)允许资金“凭空出现或消失”,而双-entry 系统通过借贷平衡机制杜绝了这种不一致性。
  • • 将个人财务系统类比为项目构建流程,使用脚本自动化处理原始数据、转换格式、导入并生成可追溯的账本,提升可维护性和可扩展性。
  • • 使用 Python 或其他脚本语言处理 PDF 报表、银行对账单等非结构化数据,实现自动分类和账目生成,减少手动录入工作量。

10. 2026 年公共领域日特别专题 (Happy Public Domain Day 2026)

https://publicdomainreview.org/blog/2026/01/public-domain-day-2026/

本文介绍 2026 年公共领域日,说明不同国家的版权期限(生命+70、生命+50 及美国对 1929 年出版物的特殊规则),并点名若干今年进入公共领域的重要作品:威廉·福克纳《我弥留之际》、阿瑟·兰索姆《掠夺者与亚马逊人》、南·谢泼德《天气之屋》、兰斯顿·休斯《不无欢笑》、赫尔曼·黑塞《纳尔齐斯与歌尔德蒙》。文章还提供完整清单与可免费下载阅读的资源链接(如 Faded Page、Standard Books)。

HN 热度 414 points | 评论 84 comments | 作者:apetresc | 24 hours ago

  • • 美国的版权期限过长,令人遗憾,尽管具体责任方存在争议,但普遍认为当前制度不合理。
  • • 版权延长法案主要受国际条约和欧盟版权期限影响,而非单纯由迪士尼推动,欧盟内部也存在不同利益诉求。
  • • 欧盟版权规则基于创作者道德权利理念,与美国以促进社会公共利益为导向的模式不同,导致部分作品在美国已进入公有领域但在欧盟仍受保护。
  • • 电影进入公有领域后,任何人都可自由复制和分发,但需注意原始素材的获取问题,如原件被垄断或缺失。
  • • 修复版或新配乐、字幕等新增创作内容仍受版权保护,而原始作品本身则不再受限制。

完整摘要请点击 “阅读原文” 👇👇👇

Hacker News 精彩评论及翻译

Why users cannot create Issues directly

https://news.ycombinator.com/item?id=46461421

100% agree.

If it's someone else's project, they have full authority to decide what is and isn't an issue. With large enough projects, you're going to have enough bad actors, people who don't read error messages, and just downright crazy people. Throw in people using AI for dubious purposes like CVE inflation, and it's even worse.

ok123456

完全同意。如果是别人的项目,他们有完全的权利决定什么是问题、什么不是问题。对于足够大的项目,你总会遇到足够多的行为不当者、不读错误信息的人,以及简直完全疯狂的人。再加上一些用AI达到可疑目的的人,比如CVE数量膨胀,情况就更糟了。


Why users cannot create Issues directly

https://news.ycombinator.com/item?id=46461860

Note that this is an active discussion where we're trying to get to a point of clarity where we can promote to an issue (when it is actionable). The discussion is open and this is the system working as intended!

I want to clarify though that there isn't a known widespread "memory leak issue." You didn't say "widespread", but just in case that is taken by anyone else. :) To clarify, there are a few challenges here:

  1. 1. The report at hand seems to affect a very limited number of users (given the lack of reports and information about them). There are lots of X meme posts about Ghostty in the macOS "Force Close" window using a massive amount of RAM but that isn't directly useful because that window also reports all the RAM child processes are using (e.g. if you run a command in your shell that consumes 100 GB of RAM, macOS reports it as Ghostty using 100 GB of RAM). And the window by itself also doesn't tell us what you were doing in Ghostty. It farms good engagement, though.
  2. 2. We've run Ghostty on Linux under Valgrind in a variety of configurations (the full GUI), we run all of Ghostty's unit tests under Valgrind in CI for every commit, and we've run Ghostty on macOS with the Xcode Instruments leak checker in a variety of configurations and we haven't yet been able to find any leaks. Both of these run fully clean. So, the "easy" tools can't find it.
  3. 3. Following point 1 and 2, no maintainer familiar with the codebase has ever seen leaky behavior. Some of us run a build of Ghostty, working full time in a terminal, for weeks, and memory is stable.
  4. 4. Our Discord has ~30K users, and within it, we only have one active user who periodically gets a large memory issue. They haven't been able to narrow this down to any specific reproduction and they aren't familiar enough with the codebase to debug it themselves, unfortunately. They're trying!

To be clear, I 100% believe that there is some kind of leak affecting some specific configuration of users. That's why the discussion is open and we're soliciting input. I even spent about an hour today on the latest feedback (posted earlier today) trying to use that information to narrow it down. No dice, yet.

If anyone has more info, we'd love to find this. :)

mitchellh

请注意,这是一个正在进行的讨论,我们正努力寻求一个清晰的观点,以便在问题可以解决时将其提升为正式问题。讨论是开放的,这正是系统预期的运作方式!

不过,我想澄清一下,并没有已知的“广泛性内存泄漏”问题。您没有说“广泛性”,但以防其他人会这么理解。:) 为了澄清,这里有几个挑战:

  1. 1. 当前的报告似乎只影响到非常有限的用户(考虑到缺乏相关的报告和信息)。在 macOS 的“强制退出”窗口中,有很多关于 Ghostty 占用大量内存的 X 平台梗图,但这并不直接有用,因为该窗口还会报告所有子进程占用的内存(例如,如果您在 shell 中运行一个消耗 100 GB 内存命令,macOS 会报告 Ghostty 占用了 100 GB 内存)。而且,该窗口本身也无法告诉我们您在 Ghostty 中做了什么。不过,这倒是能吸引不少互动。
  2. 2. 我们已在多种配置(包括完整的 GUI)下,使用 Valgrind 在 Linux 上运行了 Ghostty,在每次提交时,我们也在 CI(持续集成)中通过 Valgrind 运行了 Ghostty 的所有单元测试,我们还使用 Xcode Instruments 漏洞检查器在多种配置下在 macOS 上运行了 Ghostty,但至今未能发现任何内存泄漏。这两项工具的运行结果都非常干净。因此,那些“简单”的工具找不到它。
  3. 3. 结合第 1 点和第 2 点,没有一个熟悉代码库的维护者曾见过内存泄漏的行为。我们中的一些人连续数周使用 Ghostty 的构建版本在终端中全职工作,内存使用情况一直很稳定。
  4. 4. 我们的 Discord 服务器约有 3 万用户,其中只有一位活跃用户间歇性地遇到严重的内存问题。不幸的是,他们还没有能够将这个问题缩小到任何特定的重现步骤,而且他们对代码库不够熟悉,无法自己进行调试。不过,他们正在努力!

明确地说,我 100% 相信存在某种内存泄漏,影响了某些特定配置的用户。这就是为什么讨论是开放的,并且我们正在征求大家的意见。我今天甚至花了大约一个小时来研究最新的反馈(今天早些时候发布的),试图利用这些信息来缩小范围,但还没有结果。

如果任何人有更多信息,我们非常希望能找到它。:)


A website to destroy all websites

https://news.ycombinator.com/item?id=46459874

I've read your comment before visiting the site, and it got me wondering -- how bad can it be? Can it be worse than those acid green on red sites of the 90s-00s?

Imagine my surprise, when I opened the site and it looked and felt just like a museum or art exhibit. This was the literal feeling I had -- being at an art gallery, but online.

I guess, these comments tell more about the commenters, than TFA. We should remind ourselves to be more critical to the content we consume, regardless where it comes from.

pavlus

我在访问这个网站之前读到了你的评论,这让我很好奇——它能有多糟糕?会比90年代到00年代那些酸绿色配红色的网站更糟糕吗?可以想象我有多惊讶,当我打开这个网站时,它的外观和感觉就像一个博物馆或艺术展览。我确实有这种感觉——就像身处一个在线的艺术画廊。我想,这些评论更多地反映了评论者自身,而不是TFA(那篇文章)。我们应该提醒自己,对我们所消费的内容要更具批判性,无论它来自哪里。


Linux is good now

https://news.ycombinator.com/item?id=46457940

I think its interesting that mainstream PC gaming press is now talking about Linux. We have the benchmark Youtube channels doing some benchmarks of it as well and plenty of reports of "it just works", which is pretty promising at least for the games that aren't intentionally excluded by DRM. For me its still controllers and equipment incompatibility due to my VR headset and sim wheel/pedals setup, I use Linux everywhere else in my router and home servers. I just hope that Nvidia notices that there does appear to be a swing happening and improves their driver situation.

PaulKeeble

有趣的是,主流PC游戏媒体现在开始讨论Linux了。评测类的YouTube频道也对其进行了测试,并且有许多报告称“开箱即用”,这至少对于那些未被DRM(数字版权管理)故意排除的游戏来说,是相当有前景的。对我来说,问题依然是控制器和设备的不兼容,这主要是因为我使用的VR头显和模拟方向盘/踏板的设置。在我的路由器和家庭服务器上,我则全部使用Linux。我只希望英伟达能注意到,这种转变似乎确实正在发生,并改善他们的驱动支持状况。


BYD Sells 4.6M Vehicles in 2025, Meets Revised Sal...

https://news.ycombinator.com/item?id=46456529

I bought BYD stock in 2025 before split in the hope that their market dominance will translate to great returns. The stock has pretty consistently traded down since then. Meanwhile Tesla stock soared purely on the air coming out of Elon’s mouth.

malshe

我在2025年比亚迪股票分拆前买入,希望他们凭借市场主导地位能带来丰厚的回报。但自那以后,股价就一直持续下跌。与此同时,特斯拉的股价却纯粹是因为埃隆·马斯克的空口承诺而一飞冲天。


I'm a developer for a major food delivery app

https://news.ycombinator.com/item?id=46462595

Believability aside (I do think it’s believable personally) this is pretty much how “evil” (from outsider perspective) is done at every company, including mine. Inside it’s all sprint meetings, KPIs and terminology that are either intentionally or unintentionally designed to keep engineers far from thinking about impact on real people. It’s easy to convince a 25 year old whiz kid to optimize human assets, it’s just like Factorio and it feels good to see the number go up. In-jokes and dark humor fly and it all feels not real and just like a game. Sometimes on purpose by management, sometimes automatic as a coping mechanism. Defense (my field) is very much the same way.

nxtfari

抛开可信度不谈(我个人认为这是可信的),这基本上就是每家公司,包括我所在的公司,所谓的“邪恶”(从外部视角看)是如何运作的。在公司内部,到处都是冲刺会议、KPI和各种术语,这些术语要么是故意设计的,要么是无意中形成的,目的都是让工程师们远离对真实人群影响的思考。说服一个25岁的天才少年去优化“人力资源”很容易,这就像玩《异星工厂》一样,看到数字上涨会让人感觉很爽。内部笑话和黑色幽默满天飞,一切都感觉不真实,就像一场游戏。有时是管理层有意为之,有时则是作为一种无意识的应对机制。


50% of U.S. vinyl buyers don't own a record player

https://news.ycombinator.com/item?id=46460206

I oversee pressing for over 150k+ records a year. We eliminated download cards a while ago because the redemption rate was so low. I wouldn’t doubt if the number of buyers who don’t own a record player is even higher tha 50%, and that the percentage of people who actually play the records is actually 10-20%. I don’t have data on that, it’s just a hunch.

Many of us in the indie music industry (hip hop sustained record plants for many years, arguably until independent music started pressing in the 2000s) have mixed feelings about records. It’s a lot of plastic. A lot of waste. And they’re cubersome to bring on tour.

But there isn’t another physical medium that sells at all as well as vinyl. Soft apparel always does well. But people want vinyl.

I don’t love the Gen Z framing of this though. Vinyl purchasing at this point is multi generational.

I don’t think it’s some mysterious Gen Z love of physical. I think we all know that Spotify doesn’t pay artists appropriately and we want to help sustain the music we love. Buying digitally is just isn’t the same for a lot of people (even though it arguably is the best and easiest income generator for artists).

superultra

我每年负责压制超过15万张唱片。我们不久前就不再使用下载卡了,因为它们的兑换率实在太低。我毫不怀疑,不拥有唱机的买家比例可能高达50%以上,而真正会播放唱片的人,比例或许只有10%到20%。我没有这方面的数据,这只是一种直觉。

我们许多独立音乐行业的人(嘻哈音乐曾多年支撑着唱片厂的生产,可以说直到21世纪初独立音乐开始自行压制唱片为止)对黑胶唱片都怀有复杂的感情。它们是大量塑料,造成巨大浪费,而且带去巡演也十分笨重。但没有任何其他实体媒介能卖得像黑胶唱片一样好。柔软的服饰产品也一直卖得不错。但人们就是想要黑胶唱片。

不过,我不喜欢将这件事框定为Z世代的特有现象。如今,购买黑胶唱片的行为是跨越多世代的。我认为这并非什么神秘的Z世代对实体产品的热爱。我想我们都知道,Spotify并没有给艺术家们支付应有的报酬,而我们希望能帮助我们所热爱的音乐得以延续。对许多人来说,数字购买就是无法带来同样的感受(尽管这可以说是艺术家们最好、最容易的收入来源)。


Finland detains ship and its crew after critical u...

https://news.ycombinator.com/item?id=46458086

The fact that this area where the incident happened, Gulf of Finland, is not fully part Finnish/Estonian territorial waters, is only because of a bilateral Finnish-Estonian agreement. This was done in the 1990's purely for benevolence towards Russia.

Russia clearly hasn't acted in such way that they should enjoy these kinds of acts of benevolence. Finland and Estonia should seriously consider retreating from this agreement.

deliciousturkey

事件发生地芬兰湾之所以不完全属于芬兰和爱沙尼亚的领海,纯粹是因为一项芬兰与爱沙尼亚之间的双边协议。这项协议是在1990年代纯粹出于对俄罗斯的善意而达成的。俄罗斯显然没有表现出值得享受此类善意的行为。芬兰和爱沙尼亚应该认真考虑退出该协议。


50% of U.S. vinyl buyers don't own a record player

https://news.ycombinator.com/item?id=46455292

My dad grew up in the 50s & 60s. During COVID he purchased my daughters' the, I quote, "shittiest briefcase record players" he could find. Both girls listen to their music on their devices, but also buy vinyl. The other day, my eldest came down from her room complaining that her vinyl "sounded awful". I told her to bring it up with their Grampy. His response: "you can't appreciate good playback until you've heard awful playback on shitty record players like I had to.". My eldest is now plotting a complete hifi system, and is learning all about how to transfer "vinyl" to "digital" without losing the parts of the vinyl she likes.

This was a 5 year play by my dad. Shout out.

thechao

我爸爸成长于50和60年代。疫情期间,他给女儿们买了能找到的、用他的话说“最烂的公文包式唱片机”。两个女儿平时都用电子设备听音乐,但也购买黑胶唱片。前几天,我大女儿从她房间里下来,抱怨说她的黑胶唱片“听起来太糟糕了”。我让她去问问她们的爷爷。他的回答是:“你得先像我当年那样,在烂唱片机上听过难听的音质,才能真正欣赏好的音质。”我大女儿现在正计划搞一套完整的Hi-Fi系统,并且在学习如何将“黑胶”转为“数字文件”,同时又不丢掉她喜欢的部分。这是我爸布的一个五年的局。致敬一下。


I'm a developer for a major food delivery app

https://news.ycombinator.com/item?id=46461843

I’m posting this from a library Wi-Fi on a burner laptop because I am technically under a massive NDA. I don’t care anymore. I put in my two weeks yesterday and honestly, I hope they sue me.

Why bother using library Wi-Fi on a burner laptop if he doesn't care anymore? Why give out the biggest clue, which is the time of his resignation letter? If the story is real, this company is a straight-up scammer waiting for the biggest headline and lawsuit of the year.

hussachai

我正在用图书馆的Wi-Fi在一台一次性笔记本电脑上发帖,因为我在技术上还受制于一份重大的保密协议。我不在乎了。我昨天递交了离职信,说实话,我希望他们起诉我。

如果他已经不在乎了,何必还用图书馆的Wi-Fi和一次性笔记本电脑?为什么要透露离职信这个最大的破绽?如果这个故事是真的,那这家公司就是个彻头彻尾的骗子,正等着今年的头条新闻和最大规模的诉讼。


Bluetooth Headphone Jacking: A Key to Your Phone [...

https://news.ycombinator.com/item?id=46457307

One of the researchers here. Many people seem to prefer text to videos, which I sympathize with. So please excuse me hijacking the top comment with links to our blog post and white paper:

Blog: https://insinuator.net/2025/12/bluetooth-headphone-jacking-full-disclosure-of-airoha-race-vulnerabilities/

Paper: https://ernw.de/en/publications.html

willnix

我是研究人员之一。很多人似乎更偏爱文字而非视频,我对此深有同感。因此,请允许我占用置顶评论的位置,附上我们博客文章和白皮书的链接:

博客:https://insinuator.net/2025/12/bluetooth-headphone-jacking-full-disclosure-of-airoha-race-vulnerabilities/

论文:https://ernw.de/en/publications.html


I'm a developer for a major food delivery app

https://news.ycombinator.com/item?id=46461886

It's the biggest clue that it's typical reddit brained fanfic.

symbogra

这是它典型的Reddit脑粉丝创作最明显的线索。


HPV vaccination reduces oncogenic HPV16/18 prevale...

https://news.ycombinator.com/item?id=46464474

I would like to add:

  • • HPVs are extremely common: 80% of men and 90% of women will have at least one strain in their lives. Unless you plan to remain completely celibate, you are likely to contract a strain.
  • • Sooner is better, but vaccination can be done at any age. Guidelines often lag behind, but vaccination makes sense even if you are currently HPV-positive. While it won't clear an existing infection, it protects against different strains and reinfection (typically body removed HPV in 1-2 years). See: https://pubmed.ncbi.nlm.nih.gov/38137661/
  • • HPV16 is responsible for a large number of throat cancers (around 50% in smokers and 80% in non-smokers!). This affects both men and women. Vaccinating men is important for their own safety and to reduce transmission to their partners.

stared

我想补充几点:

  • • HPV感染非常普遍:80%的男性和90%的女性在一生中至少会感染一种HPV病毒株。除非你打算完全禁欲,否则你很可能会感染其中一种。
  • • 越早接种越好,但任何年龄都可以接种。相关的指南往往滞后,但即使你目前HPV检测呈阳性,接种疫苗也是有意义的。虽然它不能清除已有的感染,但它可以预防感染其他类型的病毒株以及再次感染(通常身体会在1-2年内清除HPV)。详见:https://pubmed.ncbi.nlm.nih.gov/38137661/
  • • HPV16是导致许多喉癌的罪魁祸首(在吸烟者中约占50%,在不吸烟者中高达80%)!无论男女都会受到影响。为男性接种疫苗对保障他们自身的安全以及减少传染给伴侣都至关重要。

Finland detains ship and its crew after critical u...

https://news.ycombinator.com/item?id=46460087

I will never understand why it has to be this way and Russia cannot be a normal country that has the goal to join the EU and be prosperous instead of doing nonsense for over a hundred years now.

ajmurmann

我永远无法理解,为什么俄罗斯就不能成为一个正常的国家,将加入欧盟、实现繁荣作为目标,而不是像过去一百多年那样,总是在做一些毫无意义的事情。


Linux is good now

https://news.ycombinator.com/item?id=46459185

These games are all rated gold or platinum on protondb, indicating that they work perfectly for most people.

Hard to say what might be going wrong for you without more details. I would guess there's something wrong with your video driver. Maybe you have an nvidia card and the OS has installed the nouveau drivers by default? Installing the nvidia first-party drivers (downloaded from the nvidia web site) will fix a lot of things. This is indeed a sore spot for Linux gaming, though to be fair graphics driver problems are not exactly unheard of on Windows either.

Personally I have a bunch of machines dedicated to gaming in my house ( https://lanparty.house ) which have proven to be much more stable running Linux than they were with Windows. I think this is because the particular NIC in these machines just has terrible Windows drivers, but decent Linux drivers (and I am netbooting, so network driver stability is pretty critical to the whole system).

kentonv

这些游戏在ProtonDB上都是金级或白金级评分,说明它们对大多数人来说都能完美运行。没有更多细节很难说你的问题可能出在哪里。我猜是你的显卡驱动有问题。可能你用的是NVIDIA显卡,而系统默认安装了nouveau驱动?安装NVIDIA官方驱动(从NVIDIA官网下载)能解决很多问题。这确实是Linux游戏的一个痛点,但公平地说,Windows上的显卡驱动问题也并非罕见。我个人家里有几台专门玩游戏的机器(https://lanparty.house),事实证明它们运行Linux比运行Windows稳定得多。我想这是因为这些机器中的特定网卡在Windows上的驱动很差,但在Linux上驱动不错(而且我是通过网络启动的,所以网络驱动的稳定性对整个系统至关重要)。


I rebooted my social life

https://news.ycombinator.com/item?id=46458638

a significant proportion of the people you used to hang out with have kids and disappear off the face of the Earth for two decades.

I’ve been on both sides of this, so I’m going to put this out into the universe:

Your friends with kids still want to see you.

They have a lot to deal with suddenly. They’re exhausted.

But they miss hanging out with you, and will leap at the opportunity to hang out if you take the initiative and make some kid-friendly accommodations.

They may decline more often than before, because the kid is sick or sleeping or not sleeping so the adults just need to lay low. But don’t take that “no” as a “stop asking”.

fleeting900

你以前常来往的朋友中,有相当一部分人因为有了孩子,就好像从人间蒸发一样消失了二十年。

我既有过孩子的体验,也当过没孩子的朋友,所以我想把这点心声分享给大家:

你那些有孩子的朋友们,他们依然很想见你。

他们突然要应付很多事情,身心俱疲。

但他们很想念和你在一起的时光,只要你主动一些,并做一些对孩子友好的安排,他们就会很乐意抓住机会和你相聚。

他们可能会比以前更频繁地拒绝你,可能是因为孩子生病了,或者在睡觉,或者睡不着,所以大人们需要安静地休息一下。但不要把他们的“不行”理解为“别再问了”。


2025: The Year in LLMs

https://news.ycombinator.com/item?id=46452114

All these improvement in a single year, 2025. While this may seem obvious to those who follows along the AI / LLM news. It may be worth pointing out again ChatGPT was introduced to us in November 2022.

I still dont believe AGI, ASI or Whatever AI will take over human in short period of time say 10 - 20 years. But it is hard to argue against the value of current AI, which many of the vocal critics on HN seems to have the opinion of. People are willing to pay 1B dollar runway already.

Being more of a Hardware person, the most interesting part to me is the funding of all the developments of latest hardware. I know this is another topic HN hate because of the DRAM and NAND pricing issue. But it is exciting to see this from a long term view where the pricing are short term pain. Right now the industry is asking, we have together over a trillion dollar to spend on Capex over the next few years and will even borrow more if it needs to be, when can you ship us 16A / 14A / 10A and 8A or 5A, LPDDR6, Higher Capacity DRAM at lower power usage, better packaging, higher speed PCIe or a jump to optical interconnect? Every single part of the hardware stack are being fused with money and demand. The last time we have this was Post-PC / Smartphone era which drove the hardware industry forward for 10 - 15 years. The current AI can at least push hardware for another 5 - 6 years while pulling forward tech that was initially 8 - 10 years away.

I so wished I brought some Nvidia stock. Again, I guess no one knew AI would be as big as it is today, and it is only just started.

ksec

短短一年,就取得了所有这些进步。对于那些一直关注人工智能和大型语言模型新闻的人来说,这或许显而易见。或许有必要再次指出,ChatGPT是在2022年11月才向大众推出的。

我仍然不相信,AGI(通用人工智能)、ASI(超级人工智能)或任何其他形式的人工智能会在短短10到20年内超越人类。然而,很难否定当前人工智能的价值,尽管许多Hacker News上直言不讳的批评者们似乎并不这么认为。人们愿意每月支付200美元,而相关服务已经获得了高达10亿美元的运营资金。

作为一名更偏向硬件领域的人,最让我感兴趣的是所有这些最新硬件开发所获得的资金支持。我知道,由于DRAM和NAND闪存的价格问题,这个话题在Hacker News上又是一个不受欢迎的讨论点。但从长远来看,这令人兴奋,因为眼前的价格波动只是暂时的阵痛。如今,整个行业都在问:我们未来几年将共同投入超过万亿美元的资本支出,如果需要,甚至还会借更多钱,那你们什么时候才能给我们提供16A/14A/10A和8A或5A工艺、LPDDR6、更大容量、更低功耗的DRAM、更好的封装、更高速的PCIe,或者直接跃升至光互连技术?

硬件栈的每一个部分都在与资金和需求深度融合。上一次出现这种景象,还是在后PC/智能手机时代,那个时代推动了硬件行业长达10至15年的发展。当前的人工智能至少还能在未来5到6年内推动硬件发展,并将那些原本计划8到10年后才会出现的技术提前到来。

我真希望当初买了些英伟达的股票。不过我猜,当初没人知道人工智能会发展到今天这样的规模,而这才刚刚开始。


A website to destroy all websites

https://news.ycombinator.com/item?id=46459232

Hacker News, probably noticeably since 2016 or so, has been a negative, curmudgeonly place. It has become political (toward the left), sclerotic, and bitterly nostalgic. It's bad and no longer represents the future. I notice it every time I visit. It's sad.

An easy way to help with the negativity is to stop leaving bait comments

evantbyrne

黑客新闻自2016年左右起就明显变得负面而愤世嫉俗了。它已经变得政治化(偏向左翼)、僵化且苦涩怀旧。它很糟糕,不再代表未来。每次我访问时都会注意到这一点。真令人难过。一个帮助改善这种负面氛围的简单方法,就是停止留下引战评论。


最新文章

随机文章

基本 文件 流程 错误 SQL 调试
  1. 请求信息 : 2026-02-09 04:05:11 HTTP/2.0 GET : https://f.mffb.com.cn/a/459752.html
  2. 运行时间 : 0.169511s [ 吞吐率:5.90req/s ] 内存消耗:4,785.06kb 文件加载:140
  3. 缓存信息 : 0 reads,0 writes
  4. 会话信息 : SESSION_ID=94bae2020fa2b5865203aa6a0996508f
  1. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/public/index.php ( 0.79 KB )
  2. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/autoload.php ( 0.17 KB )
  3. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/composer/autoload_real.php ( 2.49 KB )
  4. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/composer/platform_check.php ( 0.90 KB )
  5. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/composer/ClassLoader.php ( 14.03 KB )
  6. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/composer/autoload_static.php ( 4.90 KB )
  7. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-helper/src/helper.php ( 8.34 KB )
  8. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-validate/src/helper.php ( 2.19 KB )
  9. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/helper.php ( 1.47 KB )
  10. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/stubs/load_stubs.php ( 0.16 KB )
  11. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Exception.php ( 1.69 KB )
  12. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-container/src/Facade.php ( 2.71 KB )
  13. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/symfony/deprecation-contracts/function.php ( 0.99 KB )
  14. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/symfony/polyfill-mbstring/bootstrap.php ( 8.26 KB )
  15. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/symfony/polyfill-mbstring/bootstrap80.php ( 9.78 KB )
  16. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/symfony/var-dumper/Resources/functions/dump.php ( 1.49 KB )
  17. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-dumper/src/helper.php ( 0.18 KB )
  18. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/symfony/var-dumper/VarDumper.php ( 4.30 KB )
  19. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/App.php ( 15.30 KB )
  20. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-container/src/Container.php ( 15.76 KB )
  21. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/psr/container/src/ContainerInterface.php ( 1.02 KB )
  22. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/app/provider.php ( 0.19 KB )
  23. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Http.php ( 6.04 KB )
  24. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-helper/src/helper/Str.php ( 7.29 KB )
  25. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Env.php ( 4.68 KB )
  26. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/app/common.php ( 0.03 KB )
  27. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/helper.php ( 18.78 KB )
  28. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Config.php ( 5.54 KB )
  29. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/config/app.php ( 0.95 KB )
  30. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/config/cache.php ( 0.78 KB )
  31. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/config/console.php ( 0.23 KB )
  32. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/config/cookie.php ( 0.56 KB )
  33. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/config/database.php ( 2.48 KB )
  34. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/facade/Env.php ( 1.67 KB )
  35. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/config/filesystem.php ( 0.61 KB )
  36. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/config/lang.php ( 0.91 KB )
  37. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/config/log.php ( 1.35 KB )
  38. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/config/middleware.php ( 0.19 KB )
  39. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/config/route.php ( 1.89 KB )
  40. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/config/session.php ( 0.57 KB )
  41. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/config/trace.php ( 0.34 KB )
  42. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/config/view.php ( 0.82 KB )
  43. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/app/event.php ( 0.25 KB )
  44. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Event.php ( 7.67 KB )
  45. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/app/service.php ( 0.13 KB )
  46. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/app/AppService.php ( 0.26 KB )
  47. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Service.php ( 1.64 KB )
  48. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Lang.php ( 7.35 KB )
  49. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/lang/zh-cn.php ( 13.70 KB )
  50. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/initializer/Error.php ( 3.31 KB )
  51. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/initializer/RegisterService.php ( 1.33 KB )
  52. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/services.php ( 0.14 KB )
  53. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/service/PaginatorService.php ( 1.52 KB )
  54. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/service/ValidateService.php ( 0.99 KB )
  55. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/service/ModelService.php ( 2.04 KB )
  56. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-trace/src/Service.php ( 0.77 KB )
  57. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Middleware.php ( 6.72 KB )
  58. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/initializer/BootService.php ( 0.77 KB )
  59. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/Paginator.php ( 11.86 KB )
  60. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-validate/src/Validate.php ( 63.20 KB )
  61. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/Model.php ( 23.55 KB )
  62. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/model/concern/Attribute.php ( 21.05 KB )
  63. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/model/concern/AutoWriteData.php ( 4.21 KB )
  64. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/model/concern/Conversion.php ( 6.44 KB )
  65. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/model/concern/DbConnect.php ( 5.16 KB )
  66. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/model/concern/ModelEvent.php ( 2.33 KB )
  67. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/model/concern/RelationShip.php ( 28.29 KB )
  68. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-helper/src/contract/Arrayable.php ( 0.09 KB )
  69. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-helper/src/contract/Jsonable.php ( 0.13 KB )
  70. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/model/contract/Modelable.php ( 0.09 KB )
  71. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Db.php ( 2.88 KB )
  72. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/DbManager.php ( 8.52 KB )
  73. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Log.php ( 6.28 KB )
  74. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Manager.php ( 3.92 KB )
  75. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/psr/log/src/LoggerTrait.php ( 2.69 KB )
  76. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/psr/log/src/LoggerInterface.php ( 2.71 KB )
  77. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Cache.php ( 4.92 KB )
  78. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/psr/simple-cache/src/CacheInterface.php ( 4.71 KB )
  79. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-helper/src/helper/Arr.php ( 16.63 KB )
  80. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/cache/driver/File.php ( 7.84 KB )
  81. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/cache/Driver.php ( 9.03 KB )
  82. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/contract/CacheHandlerInterface.php ( 1.99 KB )
  83. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/app/Request.php ( 0.09 KB )
  84. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Request.php ( 55.78 KB )
  85. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/app/middleware.php ( 0.25 KB )
  86. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Pipeline.php ( 2.61 KB )
  87. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-trace/src/TraceDebug.php ( 3.40 KB )
  88. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/middleware/SessionInit.php ( 1.94 KB )
  89. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Session.php ( 1.80 KB )
  90. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/session/driver/File.php ( 6.27 KB )
  91. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/contract/SessionHandlerInterface.php ( 0.87 KB )
  92. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/session/Store.php ( 7.12 KB )
  93. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Route.php ( 23.73 KB )
  94. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/route/RuleName.php ( 5.75 KB )
  95. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/route/Domain.php ( 2.53 KB )
  96. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/route/RuleGroup.php ( 22.43 KB )
  97. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/route/Rule.php ( 26.95 KB )
  98. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/route/RuleItem.php ( 9.78 KB )
  99. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/route/app.php ( 1.72 KB )
  100. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/facade/Route.php ( 4.70 KB )
  101. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/route/dispatch/Controller.php ( 4.74 KB )
  102. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/route/Dispatch.php ( 10.44 KB )
  103. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/app/controller/Index.php ( 4.81 KB )
  104. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/app/BaseController.php ( 2.05 KB )
  105. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/facade/Db.php ( 0.93 KB )
  106. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/connector/Mysql.php ( 5.44 KB )
  107. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/PDOConnection.php ( 52.47 KB )
  108. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/Connection.php ( 8.39 KB )
  109. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/ConnectionInterface.php ( 4.57 KB )
  110. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/builder/Mysql.php ( 16.58 KB )
  111. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/Builder.php ( 24.06 KB )
  112. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/BaseBuilder.php ( 27.50 KB )
  113. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/Query.php ( 15.71 KB )
  114. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/BaseQuery.php ( 45.13 KB )
  115. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/concern/TimeFieldQuery.php ( 7.43 KB )
  116. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/concern/AggregateQuery.php ( 3.26 KB )
  117. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/concern/ModelRelationQuery.php ( 20.07 KB )
  118. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/concern/ParamsBind.php ( 3.66 KB )
  119. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/concern/ResultOperation.php ( 7.01 KB )
  120. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/concern/WhereQuery.php ( 19.37 KB )
  121. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/concern/JoinAndViewQuery.php ( 7.11 KB )
  122. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/concern/TableFieldInfo.php ( 2.63 KB )
  123. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-orm/src/db/concern/Transaction.php ( 2.77 KB )
  124. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/log/driver/File.php ( 5.96 KB )
  125. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/contract/LogHandlerInterface.php ( 0.86 KB )
  126. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/log/Channel.php ( 3.89 KB )
  127. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/event/LogRecord.php ( 1.02 KB )
  128. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-helper/src/Collection.php ( 16.47 KB )
  129. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/facade/View.php ( 1.70 KB )
  130. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/View.php ( 4.39 KB )
  131. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Response.php ( 8.81 KB )
  132. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/response/View.php ( 3.29 KB )
  133. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/Cookie.php ( 6.06 KB )
  134. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-view/src/Think.php ( 8.38 KB )
  135. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/framework/src/think/contract/TemplateHandlerInterface.php ( 1.60 KB )
  136. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-template/src/Template.php ( 46.61 KB )
  137. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-template/src/template/driver/File.php ( 2.41 KB )
  138. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-template/src/template/contract/DriverInterface.php ( 0.86 KB )
  139. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/runtime/temp/067d451b9a0c665040f3f1bdd3293d68.php ( 11.98 KB )
  140. /yingpanguazai/ssd/ssd1/www/f.mffb.com.cn/vendor/topthink/think-trace/src/Html.php ( 4.42 KB )
  1. CONNECT:[ UseTime:0.000602s ] mysql:host=127.0.0.1;port=3306;dbname=f_mffb;charset=utf8mb4
  2. SHOW FULL COLUMNS FROM `fenlei` [ RunTime:0.000844s ]
  3. SELECT * FROM `fenlei` WHERE `fid` = 0 [ RunTime:0.001563s ]
  4. SELECT * FROM `fenlei` WHERE `fid` = 63 [ RunTime:0.003553s ]
  5. SHOW FULL COLUMNS FROM `set` [ RunTime:0.000721s ]
  6. SELECT * FROM `set` [ RunTime:0.002767s ]
  7. SHOW FULL COLUMNS FROM `article` [ RunTime:0.000781s ]
  8. SELECT * FROM `article` WHERE `id` = 459752 LIMIT 1 [ RunTime:0.006576s ]
  9. UPDATE `article` SET `lasttime` = 1770581111 WHERE `id` = 459752 [ RunTime:0.006724s ]
  10. SELECT * FROM `fenlei` WHERE `id` = 67 LIMIT 1 [ RunTime:0.000885s ]
  11. SELECT * FROM `article` WHERE `id` < 459752 ORDER BY `id` DESC LIMIT 1 [ RunTime:0.001324s ]
  12. SELECT * FROM `article` WHERE `id` > 459752 ORDER BY `id` ASC LIMIT 1 [ RunTime:0.003551s ]
  13. SELECT * FROM `article` WHERE `id` < 459752 ORDER BY `id` DESC LIMIT 10 [ RunTime:0.014978s ]
  14. SELECT * FROM `article` WHERE `id` < 459752 ORDER BY `id` DESC LIMIT 10,10 [ RunTime:0.031106s ]
  15. SELECT * FROM `article` WHERE `id` < 459752 ORDER BY `id` DESC LIMIT 20,10 [ RunTime:0.026606s ]
0.171189s