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 生成,可能有误。

    编程与软件工程github.com

    Rawdrawandroid:用 C 构建 Android 应用

    Rawdrawandroid: Build Android apps in C

    2次上首页
    4年跨度
    748累计得分
    302条评论

    2020 — 2024,它一次次回到首页

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

    导读

    Rawdrawandroid 是 cnlohr 开源的一个项目,让你完全用 C 语言(配合 make 脚本)构建 Android 应用,绕开 Java/Kotlin 和庞大的构建体系,运行时依赖极小。它证明了在 JNI 层完成权限请求等'必须用 Java'的事情是可行的。

    为什么经久不衰:它挑战了 Android 生态'必须用 Java'的惯性思维,用极简工具链换来极致性能和可控性,对追求底层效率和反过度抽象的开发者始终有吸引力。

    关键词 AndroidC语言JNI极简构建

    HN 评论精选

    赞赏作者打破'必须用 Java'教条的 hacker 精神

    作者做这个项目多少也是为了回击网上那些在 Stack Overflow 下说'这不可能'或'你做法不对'的人……比如'JNI 里请求权限?必须在 Java 里做'之类的论调。我对你们关于什么可能什么不可能的意见毫无兴趣。这是计算机科学,没有限制,我什么都能做,反正都只是比特。

    Dig1t查看英文原文

    "A little bit of this also has to do to stick it to all those luddites people on the internet who post "that's impossible" or "you're doing it wrong" to Stack Overflow questions... Requesting permissions in the JNI "oh you have to do that in Java" or other dumb stuff like that. I am completely uninterested in your opinions of what is or is not possible. This is computer science. There aren't restrictions. I can do anything I want. It's just bits. You don't own me." This is so funny and so relatable.

    用亲身经历佐证:去掉 OO 抽象层、用 C 实现能带来实打实的性能提升

    我几年前做过类似实验:因为 Android 某些操作慢得让人沮丧(性能分析发现大量时间耗在嵌套构造函数等面向对象的抽象开销上),我们用纯 C 实现了一个纵向滚动 ListView。结果验证了假设——滚动毫无可感知延迟、完全不卡顿。每次回到移动开发,我都失望地看到大家不断重复造同样的样板轮子、堆叠一层层抽象。

    g_p查看英文原文

    This is quite interesting to see, as I recall experimenting with something similar a few years ago. In that case, borne out of anger and frustration from how slow Android was at some things, I complained to one of the engineers I had brought onboard about how a 1970s computer was vastly more responsive and performant (to the user's perspective) than these modern (in ~2016) Android devices. We ended up building a prototype of a vertical scrolling ListView, implemented entirely in C, implementing all the "normal" functionality required to allow Android to use it. I believe my initial frustration was borne from performance tracing of an app we were developing, and finding the amount of time spent in nested constructors and other kinds of inherited object-oriented bloat was actually impacting on the user perceived performance (users said it was slow to scroll). My hypothesis was that if the functionality itself was implemented in C, properly and efficiently, with none of these extra layers of abstraction, it would be faster. That was definitely validated. I don't recall the figures now, but you could scroll a list with no perceptible latency as fast as you liked, with no stutter. The performance traces were nice and normal. It was smooth and fast. Mobile apps were something I got far away from for a while, but every time I return, I'm disappointed to see an ecosystem of re-inventing the same (boilerplate) wheel, and running the same code. For the number of layers of abstraction I saw the OS burning cycles on, it is absurd to me why the "end-developer" is left to do so much boilerplate coding! Surely at least one of those layers of abstractions could get developers to a place of implementing their own logic, rather than platform-specific logic. Case in point, the Android activity lifecycle (!)

    赞叹项目的极简构建方式和背后巨大的摸索成本

    这看起来太棒了,我做 Android 应用那会儿要是有它就好了。我喜欢那个老式的 make 脚本,也为极小的运行时依赖感到兴奋。这背后一定需要大量实验和翻阅 SDK 角落里文档匮乏的旧示例。

    tomcam查看英文原文

    This looks wonderful. I wish it had been around when I was doing an android app. I absolutely love seeing it and a good old make script. I am thrilled at the tiny tiny runtime requirements. Bravo. This must have required an incredible amount of experimenting and mucking through old, poorly documented examples in the dusty corners of an SDK somewhere.

    补充替代方案:SDL2 也支持纯 C 的 Android 开发路径

    用 SDL2 也可以在 Android 上用 C 开发:你的应用编译成一个 .so,SDL2 提供一个薄薄的 Java 垫片来调用它,然后就可以开干了。

    pengaru查看英文原文

    You can similarly develop in C for Android using SDL2. Basically your app becomes a .so with a thin java shim SDL2 provides that calls into your .so and you're off to the races. https://wiki.libsdl.org/Android

    历次讨论

    同类还值得读

    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

    关注向阳乔木

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

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

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