91
Project Panama: Interconnecting JVM and Native Code
We are improving and enriching the connections between the Java virtual machine and well-defined but “foreign” (non-Java) APIs, including many interfaces commonly used by C programmers.
Most cited
Posts that commenters keep linking to, ranked by how many different people have cited them in Hacker News comments. 383 posts.
92
Defer, Panic, and Recover
An introduction to the Go's defer, panic, and recover control flow mechanisms.
93
PEP 3113 – Removal of Tuple Parameter Unpacking
Tuple parameter unpacking is the use of a tuple as a parameter in a function signature so as to have a sequence argument automatically unpacked. An example is:
94
95
Open-sourcing Haxl, a library for Haskell
Visit the post for more.
96
More Dots: Syntactic Loop Fusion in Julia
After a lengthy design process (https://github.com/JuliaLang/julia/issues/8450) and preliminary foundations in Julia 0.5 (/blog/2016-10-11-julia-0.5-highlights#vectorized_function_calls), Julia 0.6 includes new facilities for writing code in the "vectorized"...
97
Toward Go 2
How we will all work together toward Go 2.
98
My Clojure Workflow, Reloaded
This is a companion post to my discussion with Craig Andera on Relevance Podcast Episode 32 and my Clojure/West talk Clojure in the Large. I've talked about ...
99
Coalton: How to Have Our (Typed) Cake and (Safely) Eat It Too, in Common Lisp
By Robert Smith, Elias Lawson-Fox, Cole Scott Updated July 1, 2025 by Robert Smith. Introduction Coalton is a statically typed functional programming language built with Common Lisp. We can load it like a normal Lisp library. CL-USER> (asdf:load-system "coalton") CL-USER> (in-package #:coalton-user) COALTON-USER> This…
100
Introducing the Go Race Detector
How and why to use the Go race detector to improve your programs.
101
PEP 518 – Specifying Minimum Build System Requirements for Python Projects
This PEP specifies how Python software packages should specify what build dependencies they have in order to execute their chosen build system. As part of this specification, a new configuration file is introduced for software packages to use to specify...
102
PEP 3131 – Supporting Non-ASCII Identifiers
This PEP suggests to support non-ASCII letters (such as accented characters, Cyrillic, Greek, Kanji, etc.) in Python identifiers.
103
0.4.1: Introducing Parse
One of the greatest feature of the Rebol language has always been its parsing engine, simply called Parse. It is an amazing piece of des...
104
Error handling and Go
An introduction to Go errors.
105
PEP 374 – Choosing a distributed VCS for the Python project
Python Enhancement Proposals (PEPs)
106
Clojure - Rationale
Customers and stakeholders have substantial investments in, and are comfortable with the performance, security and stability of, industry-standard platforms like the JVM. While Java developers may envy the succinctness, flexibility and productivity of dynamic languages, they have concerns about running on…
107
PEP 318 – Decorators for Functions and Methods
The current method for transforming functions and methods (for instance, declaring them as a class or static method) is awkward and can lead to code that is difficult to understand. Ideally, these transformations should be made at the same point in the...
108
PEP 263 – Defining Python Source Code Encodings
This PEP proposes to introduce a syntax to declare the encoding of a Python source file. The encoding information is then used by the Python parser to interpret the file using the given encoding. Most notably this enhances the interpretation of Unicode ...
109
PEP 635 – Structural Pattern Matching: Motivation and Rationale
This PEP provides the motivation and rationale for PEP 634 (“Structural Pattern Matching: Specification”). First-time readers are encouraged to start with PEP 636, which provides a gentler introduction to the concepts, syntax and semantics of patterns.
110
Tutorial: Writing an Interpreter with PyPy, Part 1
This is a guest blog post written by Andrew Brown , with help from the PyPy developers on the pypy-dev mailing list. This tutorial's master...
111
Goodbye to the C++ Implementation of Zig
It’s funny - I have shared this story a handful of times with friends of mine who are qualified, competent software engineers, and each time the response was confusion about why any of this would be necessary or even remotely helpful. WebAssembly ?!
112
113
Implications of Rewriting a Browser Component in Rust
Since our first release in 2002, there have been 69 security bugs in Firefox’s style component. If we'd had a time machine and could have written this component in Rust from the start, 51% wouldn't have happened. That said, Rust is not foolproof. Developers still need to be aware of correctness bugs and data leakage…
114
115
(On | No) Syntactic Support for Error Handling
Go team plans around error handling support
116
Fixing Python Performance with Rust
Why your JavaScript events are coming in quicker now.
117
118
119
The Ten Commandments for C Programmers (1987)
``Frequently'' means thou shouldst draw thy daily guidance from it, rather than hoping thy code will achieve lint's blessing by a sudden act of repentance at the last minute. De-linting a program which has never been linted before is often a cleaning of the stables such as thou wouldst not wish on thy worst enemies…
120
Ruby 3x3: Matz, Koichi, and Tenderlove on the Future of Ruby Performance
Jonan: Welcome everyone. Today we are doing an interview to talk about new features coming in Ruby 3. I am here with my coworker, Sasada Koichi san....