Topics /

Software Engineering

The most popular blog posts about software engineering on Hacker News. 14,536 posts.

Any year
4621

AngularJS: The Bad Parts

Hey! If you do front end development, you should know about CatchJS. It’s a JavaScript error logging service that doesn’t suck. Below is a graph over the amount of searches for AngularJ…

4623

A Mac Podcast App You Can't Have

I wasn't going to write this post because I've already said most of what I wanted to on Twitter [http://twitter.com/steve228uk]. Yesterday though, I changed my mind when I saw this Tweet from Product Hunt. > The Best Podcast Apps for Mac 🎙️🖥️ Add your favorite 👉 https://t.

4629

Secure by Design

I really like Secure by Design. The key idea is that there is a big overlap between secure code and good software design. Code that is strict, clear and focused will be easier to reason about, and …

4630

Opus 1.2 Released

For music encoding Opus has already been shown to out-perform other audio codecs at both 64 kb/s and 96 kb/s . We originally thought that 64 kb/s was near the lowest bitrate at which Opus could be useful for streaming stereo music. However, with variable bitrate (VBR) improvements in Opus 1.1, suddenly 48 kb/s became…

4643

C++23: Removing garbage collection support

If we go through the list of C++23 features, we can stumble upon the notion of garbage collection twice. Once among the language and once among the library features. Both entries refer to the same paper (P2186R2): garbage collection (GC in short) support is getting removed from C++. Just to make it clear, it’s not…

4644

Oberon (2009)

Steven Frank's essay on the current state of the desktop UI 1 reminded me of Oberon, a delightfully insane system I used back when I was studying computer science at ETH Zürich. The first thing you have to understand about Oberon is that it evolved entirely outside of the normal genealogy of user interfaces…

4646

How to stop functional programming

You go into work and discover that a coworker isn't happy with some code you wrote because they don't understand it. They go to your manager and tell them that you're being a problem by writing code they don't understand. Your manager, being very skilled in conflict resolution, makes a technical decision to avoid…