はてなブックマーク

← Linguistics and Programming Languages NOTE: This is an article I've published more that a decade ago. From my today's point of view it may be a bit naive but it still makes a valid and interesting proposal. Sadly though, nobody have taken the challenge in the meantime. Can it be a time to do so now? I am republishing it here as is, with no modifications whatsover. It is quite common to use compu

← Finish your stuff If there is one principle that should be added to the UNIX philosophy, it is: "Finish your project." It's the most simple, yet the most disregarded software engineering princinple I can think of. I dare you to list three finished software projects. Having hard time, eh? Except for some basic UNIX tools, like grep or make, it's almost impossible to find anyting that's truly fini

← Priotitised Load Balancing with nanomsg Load balancing is one of the typical features of messaging systems. Although some don't do it (MQTT), most of them provide some way to spread a workload among cluster of boxes. In ZeroMQ load balancing is done via REQ (requests that require replies) or, alternatively, by PUSH socket (requests that don't require replies). When designing it, I've opted for c

← Why should I have written ZeroMQ in C, not C++ (part II) In my previous blog post I've discussed how the need for rigorous error handling in low-level infrastructure software prevents the usage of many fundamental C++ features (exceptions, constructors, destructors). The conclusion was that with such a severely limited feature set, writing the program in C yields shorter and more readable codeba

← Why should I have written ZeroMQ in C, not C++ (part I) Just to be clear from the very beginning: This is not going to be a Torvalds-ish rant against C++ from the point of view of die-hard C programmer. I've been using C++ whole my professional career and it's still my language of choice when doing most projects. Naturally, when I started ZeroMQ project back in 2007, I've opted for C++. The main