Programming Leftovers
-
Jamie Brandon ☛ 0043: 2023, debog, never sort, critique of sql, status game, more fuel you
I'm not super excited about their proposed language, but they have some insightful criticisms that I haven't seen elsewhere: [...]
-
Bozhidar Batsov ☛ Weird Ruby: A Weird Way to Filter Out Elements
Imagine you want to filter out the nil elements in an array. There are many ways to do this in Ruby: [...]
-
Bozhidar Batsov ☛ Learning OCaml: Verifying tail-recursion with @tailcall
How can you be sure that an OCaml function you wrote is actually tail-recursive? You can certainly compile the code and look at the generated assembly code, but that’d be quite the overkill, given there is a much simpler way to do this.
-
DataGeeek ☛ Data Visualization of the WBL Index and Modeling with Quantile Regression using Random Forest
As we enter the new year, women still seem not to have equal rights compared to men in the working environment. This situation is more prominent in the developing and least developed countries. This article will examine that using the WBL (women, business, and law) index.
-
Perl / Raku
-
[Old] Wired ☛ Dec. 18, 1987: Perl Simplifies the Labyrinth That Is Programming Language
Perl went through a rapid series of upgrades -- less than seven years elapsed between versions 1.0 and 5.0 -- before the language was fully mature. Even at that, Perl 5 has been continuously tinkered with since 1994, with many additional features keeping Perl at the forefront of programming languages.
-
-
Python
-
Seth Michael Larson ☛ urllib3 is fundraising for HTTP/2 support
2023 was a transformative year for urllib3, headlined by the first stable release of v2.0 after multiple years of development by our maintainers and community. This major release is only the beginning of our plans to overhaul the library’s capabilities by removing constraints on our HTTP implementation while preserving backwards compatibility.
-
-
Shell/Bash/Zsh/Ksh
-
Lawrence Tratt ☛ Faster Shell Startup With Shell Switching
A few days ago Thorsten Ball wrote a post exhorting Unix users to optimise their shell’s startup time. It’s excellent advice and well worth following.
The Unix shell has two major use cases: as an interactive prompt (what we often call “the command line”); and as a “scripting” [1] or “non-interactive command” language. We normally pick one shell (bash, fish, zsh, etc.) and use it for both use cases.
However, we can use different shells for each use case. People don’t normally bother doing so because there is little functional utility in doing so. There is, however, a small performance reason for doing so, which I’m going to look at in this post. I’m going to call the technique I describe in this post “shell switching” since I’m not aware that it has an existing name.
-