481
New
The latest blog posts to take off on Hacker News. 498 posts.
482
What Happens to OO When Processors Are Free? (2015)
A while ago, I presented as a crazy thought experiment the idea of using Montecito's transistor budget for creating a chip with tens of tho...
483
484
Systemd Sucks, Long Live Systemd
systemd seems to be a dividing force in the Linux community. There doesn’t seem to be a middle ground to...
485
486
487
How removing caching improved mobile performance by 25%
and how we found out.
488
489
Add a const here, delete a const there
Update, February 2019: Two years later the VC++ bug I reported here still exists, even in VS 2019 preview. However Chromium no longer builds with VC++ so I’m reverting the changes where I del…
490
Research papers in the .NET source
This post is completely inspired by (or ‘copied from’ depending on your point of view) a recent post titled JAVA PAPERS (also see the HackerNews discussion). However, instead of looking at Java and the JVM, I’ll be looking at references to research papers in the .NET language, runtime and compiler source code.
491
492
Select(2) is fundamentally broken
In a previous blog post we discussed a brief history of the select(2) syscall . The article concludes that some I/O multiplexing was necessary to do console emulation, games and non-trivial TCP/IP applications.
493
Goroutines, Nonblocking I/O, and Memory Usage
I am generally a fan of Go's approach to concurrency: writing code with goroutines is a lot easier than writing traditional nonblocking network servers in a language like C or C++. However, while working on a highly concurrent network proxy I came across an interesting realization about how the Go concurrency model…
494
495
Rumors of Cmd’s death have been greatly exaggerated
This post is in response to a story published on December 6th 2016 by ComputerWorld titled "Say goodbye to the MS-DOS command prompt" and its follow-up
496
497
Lock-Free Bugs
[ I wrote this post in mid-2014 for debuggers.co, which seems to have gone at least partly defunct, so I am reproducing it here. That site collected answers from programmers to the prompt “What’s the most interesting bug you’ve encountered?” ]
498
Why isn't memset() async-signal-safe?
Really, POSIX? Really? memset() isn't async-signal-safe? How is it not safe? … oh … that's why