HackerURLs

一次又一次被重新发现的经典。

同一个链接,相隔一年以上,一次又一次被人重新发现、再次冲上 Hacker News 首页。能经受住这种时间检验的,大多是值得一读再读的文章。每篇附中文标题,讨论最热的那些再加上中文导读和高赞评论翻译。

从名人堂开始
  • 4,700+篇经过时间检验的经典

Hall of fame

名人堂

在经典库里看全部精选

上首页次数最多、而且有中文导读的 30 篇。时间轴上每个黑点是一次上首页,空心点是一次没冲上去的投稿。

  1. 正在载入经典…

Archive

经典库

按第一次上首页的年份分布,点柱子筛选。

排序

    About

    这些经典是怎么挑出来的

    1. 01

      合并同一个链接

      读取 Hacker News 自 2006 年以来的全部链接投稿,把 http/https、www、跟踪参数等写法不同的同一篇文章合并成一条。

    2. 02

      只留经得起时间的

      同一链接至少两次拿到 50 分以上(约等于上首页),而且两次相隔一年以上;再由 AI 剔除状态页、产品首页和新闻事件。

    3. 03

      写导读、译评论

      上首页次数最多的 2,000 篇配上中文导读、"为什么经久不衰",并精选翻译 HN 高赞评论。导读由 AI 生成,可能有误。

    编程与软件工程blog.mailchimp.com

    呃,你用 PHP?

    Ewww, You Use PHP?

    3次上首页
    5年跨度
    343累计得分
    334条评论

    2011 — 2016,它一次次回到首页

    黑点是上首页(≥ 50 分)的那次投稿,空心点是没冲上去的投稿,点越大分数越高。

    导读

    这是 MailChimp 博客的一篇文章,以自嘲口吻回应“你们居然用 PHP”的质疑,讨论公司使用 PHP 的背景、招聘优秀开发者的困难,以及语言和框架选择背后的工程文化。文末更新显示,四年后 MailChimp 规模大幅增长,但仍然使用 PHP。

    为什么经久不衰:它把技术鄙视链、招聘现实和务实选型放在一起,而 MailChimp 多年后仍坚持 PHP 并给出规模数据,使这场争论有了经得起时间检验的案例。

    关键词 PHPMailChimp技术选型开发者招聘

    HN 评论精选

    招聘合格 PHP 开发者很难,社区文化和工程实践比语言本身更关键。

    作为亚特兰大另一家想招优秀 PHP 开发者的创业公司,我完全理解 MailChimp。我找了好几个月本地有 TDD 或现代敏捷实践经验的 PHP 开发者,极其困难。良好的工程文化在 Ruby/Python 社区更普遍,但随着这些语言主流化,平均开发者质量也下降得很快;语言选择从技术角度没那么重要,从实践和社区角度才重要。

    apinstein查看英文原文

    As another startup in Atlanta trying to hire good PHP developers, I can sympathize entirely with MailChimp on this one. I have been searching for months for local PHP developers with experience doing TDD or other agile/modern practices and it is extremely difficult. If you are one, please feel free to contact me. I think good TDD/agile/architecture cultures are more prevalent in ruby/python but as those languages have become more mainstream the quality of the average dev in those environments has dropped quickly. A few years ago only really good devs ventured into ruby stuff. Now everyone is trying it as the tools have made the language much more accessible for the average developer. I am seeing more and more programming mistakes in the ruby code I dive into than I used to. Language choice doesn't matter too much from a technical perspective. It matters from a practical perspective. Consider the jQuery/prototypejs war. Prototypejs was technically superior for a long time, yet due to jQuery's more accessible plugin culture and prettier web site they were over time able to build a more robust community and took the mindshare lead in the js space. I still think one of the core reasons ruby/rails and python/django got big is that for a long time there was only one major framework available for the language and this caused a better community than the php landscape, which pre-dated frameworks by a long time (this happened to perl as well). So there wasn't "one true way" in php to build apps quickly, and this hurt the php community when rails got big. I think as a community we lost a lot of talent to ruby/rails in the last few years. Bottom line is that accessibility, pervasiveness and low-learning-curve are critical to the initial and continued success of any platform, whether it's a language (ruby > php > perl), OS (ios > android > rim), etc. Language advances in PHP (circular gc, traits, closures, etc) have brought php's language capabilities forward enough that it's a respectable platform for sticking with. However, you can't fix the community really since it's so fragmented. Fortunately some frameworks are getting enough traction to have rich ecosystems, and that's definitely a great thing for the language and the community.

    批评 PHP 主流应用代码混乱、缺乏架构和测试。

    我对 PHP 的主要不满是,部署最广的 PHP 应用往往是我见过最难管理、最混乱的代码,比如 WordPress 和 vBulletin。它们几乎无视 MVC 这类适合网站开发的模式,测试更无从谈起。我知道 PHP 可以写得更好,但我接触到的应用常像一团乱麻;能选时我会用 Rails 和 Sinatra。

    tibbon查看英文原文

    My main beef with PHP is that the most deployed applications that use it are some of the most difficult to manage and messy pieces of code that I've ever seen. I'm talking about Wordpress and vBulletin. While MVC isn't the only valid design pattern, some varient of it is rather nice when working with websites and these two seem to ignore it through and through. Testing? What's that? I know that better can be written in PHP, but for apps that I've had to deal with, PHP normally looks like an overpowered scripting language that's just a mess. I'll stay with Rails and Sinatra when I can.

    实际尝试 Node 后因异步复杂回到同步 PHP,认为 PHP 有缺点但务实好用。

    我公司产品后端是 PHP。我重写时先试了 Node.js,因为能共享客户端/服务端代码,而且很时髦。但几周后 Node 的异步特性让我头快炸了,我放弃并回到 PHP,因为代码可以逐行同步执行,不需要各种 hack。PHP 作为语言有缺陷,但进步很大,也不该承受所有仇恨;很多批评源于它易学、允许自由发挥,早期导致新手写出不安全代码,比如 register_globals。总之它简单、强大、能把事做完。

    ubuntuftw查看英文原文

    My company's product backend is written in PHP. I'm currently rewriting it, and when I started the process, I tried doing it in Node.js because 1) the possibility of client/server code sharing and 2) that's what all the cool kids were doing. That lasted all of a few weeks before the async nature of Node made my head nearly explode. I scraped that and went back to PHP where you can depend on code being executed line-by-line, synchronously, without hacks. As a language, PHP definitely has some warts. But, it's come a long way, and it keeps getting better all the time. Personally, I don't think it deserves all the hate it gets. Some criticism is warranted, but definitely not all of it. I think a lot of it stems from the fact that the language is so easy to learn and lets you do things your own way, which (at least in the early days) led to a lot of newbies writing insecure code. See: register_globals (since removed). That all said, I love PHP. It's simple, yet powerful. It grows with you, and most importantly, it gets the job done.

    MailChimp 规模增长后仍坚持 PHP,用数据回应质疑。

    更新(12/9/14):这篇文章写于四年前,我们已经成长很多。目前 700 万用户每天发送 4 亿封邮件,每月略超 120 亿封。是的,我们仍然使用 PHP。

    yarapavan查看英文原文

    * Update (12/9/14): We’ve grown a lot since this post was written 4 years ago. Currently, our 7 million users send 400 million emails every day, which works out to just north of 12 billion emails a month. And yes, we still use PHP.

    历次讨论

    同类还值得读

    1. 开源应用架构

      The Architecture of Open Source Applications

      《开源软件架构》(AOSA)是一本在线免费书,邀请知名开源项目的作者亲自剖析其内部设计,涵盖 SQLAlchemy、LLVM、Audacity、Apache、Bash 等系统。

      编程与软件工程上首页 9 次 · 2011–2024aosabook.org编辑精选
    2. 编程语言简史:简短、不完整且多半错误

      A Brief, Incomplete, and Mostly Wrong History of Programming Languages

      一篇以戏谑、故意不准确的方式回顾编程语言史的博客文章,用夸张轶事和讽刺定义串起 Lisp、C、C++、Java、JavaScript、PHP 等语言。

      编程与软件工程上首页 8 次 · 2009–2021james-iry.blogspot.com
    3. SQLite 是如何测试的

      How SQLite is tested

      SQLite 官方文档页,系统介绍 SQLite 的测试体系:多种测试方法(TCL 测试、模糊测试、回归测试、静态分析等)和海量测试用例,展示了这个小型开源项目如何靠极致测试获得…

      编程与软件工程上首页 8 次 · 2009–2025sqlite.org编辑精选
    4. 高级编程语言(2009)

      Advanced programming languages (2009)

      Matt Might 的经典文章,按用途推荐“高级编程语言”:如果追求就业就选主流语言,如果追求表达力、学术研究或创业,则推荐 Haskell、OCaml、Scala 等函数式语…

      编程与软件工程上首页 8 次 · 2009–2022matt.might.net
    5. 我的 Forth 与栈机器经历

      Yosefk - My history with Forth & stack machines

      作者以亲身经历回顾了使用 Forth 语言和栈式机器的历程:既赞叹其简洁优雅、代码量小、可自举的优点,也坦率指出栈操作在实际编程中的痛苦,以及 Forth 社区文化中的问题。

      编程与软件工程上首页 8 次 · 2010–2024yosefk.com编辑精选

    打赏支持

    打赏二维码

    觉得有用,请作者喝杯咖啡。

    WeChat

    关注向阳乔木

    微信公众号「向阳乔木推荐看」

    微信公众号「向阳乔木推荐看」二维码

    微信扫一扫;在微信里打开本页时,长按二维码识别。