Language Selection

English French German Italian Portuguese Spanish

Programming Leftovers

Filed under
Development

  • Anti-patterns You Should Avoid in Your Code

    Every developer wants to write structured, simply planned, and nicely commented code. There are even a myriad of design patterns that give us clear rules to follow, and a framework to keep in mind.

    But we can still find anti-patterns in software that was written some time go, or was written too quickly.

    A harmless basic hack to resolve an issue quickly can set a precedent in your codebase. It can be copied across multiple places and turn into an anti-pattern you need to address.

  • AsmREPL: Wing your way through x86-64 assembly language • The Register

    Ruby developer and internet japester Aaron Patterson has published a REPL for 64-bit x86 assembly language, enabling interactive coding in the lowest-level language of all.

    REPL stands for "read-evaluate-print loop", and REPLs were first seen in Lisp development environments such as Lisp Machines. They allow incremental development: programmers can write code on the fly, entering expressions or blocks of code, having them evaluated – executed – immediately, and the results printed out. This was viable because of the way Lisp blurred the lines between interpreted and compiled languages; these days, they're a standard feature of most scripting languages.

    Patterson has previously offered ground-breaking developer productivity enhancements such as an analogue terminal bell and performance-enhancing firmware for the Stack Overflow keyboard. This only has Ctrl, C, and V keys for extra-easy copy-pasting, but Patterson's firmware removes the tedious need to hold control.

  • Wasmer 2.1 WebAssembly Implementation Adds Virtual Filesystem, Lisp + Crystal Support - Phoronix

    Wasmer as "the universal WebAssembly runtime" that focuses on being able to run WASM code on any platform is out with its next major release.

    Released this summer was Wasmer 2.0 as a step forward for this open-source WASM implementation. The project remains focused on trying to compile "everything" to WebAssembly and to then run that on any operating system / platform or embed it in other languages or run it in a web browser. Wasmer 2.1 was released today as the next major iteration of the platform.

  • What's The Big Deal With Linux Capabilities? | Hacker Noon

    The prevalent perception is that Linux users benefit from and exercise privileges, however this is not the case. It's the process or executable that runs in a certain user context and exercises rights (permission to carry out to perform the privileged operations guarded by Linux kernel).

  • Built with the Rust programming language – LinuxBSDos.com

    Not too long ago, the talk in developer circles seemed to be mainly about Go, Go, Go, Go… I’m referring, of course, to the programming language from Google.  

  • Perl Weekly Challenge 141: Number Divisors and Like Numbers
  • Closures

    A casual remark about closures which I made in My Favorite Warnings: redefine touched off a long off-topic exchange with Aristotle that I thought ought to be promoted to a top-level blog entry. The big thing I learned was that any Perl subroutine can be a closure. The rest of this blog will try to make clear why I now believe this. The words are my own, as are any errors or misconceptions.

    The second sentence of Wikipedia's definition of a closure says "Operationally, a closure is a record storing a function together with an environment." This makes it sound a lot like an object, and therefore of little additional interest in an O-O environment.

    But I came to closures pragmatically through Perl, and to me they were a magic way to make data available somewhere else. All I had to do was get a code reference where it needed to be, and any external lexical variables got the values at the time the reference was taken. So much I understood up to the fatal blog post, and it sufficed for my simple needs.