Casholic with a lisp.
Casholic with a lisp.
A process pool means extra copying of data around which incurs a huge cost and this is made worse by the tendency for parallel-processing-friendly workloads often consisting of large amounts of data.
Usually, but when it isn’t then you’ve got a bottleneck. Multithreaded performance is a major weak point if you need to do any processing that isn’t handled by one of the libraries.
That depends on what the application needs to do. There’s a reason why all performance-critical libraries for Python aren’t written in Python.
C is almost the perfect subset for me, but then I miss templates (almost exclusively for defining generic data structures) and automatic cleanup. That’s why I’m so interested in Zig with its comptime and defer features.
The graph goes up for me when I find my comfortable little subset of C++ but goes back down when I encounter other people’s comfortable little subset of C++ or when I find/remember another footgun I didn’t know/forgot about.
Rapid Abandonment Is Imperative
I mostly drink instant coffee. I’m also a dirty Windows user who mainly uses WSL (with the Ubuntu distro on that) for my Linux needs.
Funny timing on this since the mini pc market is picking up steam from what I can tell. Then again, these are overpriced compared to the competition.
I sometimes run into this when I extract an archive file on Windows and there are files named with different cases but are otherwise the same. I prefer case-sensitivity because I like precision and fewer assumptions being made about a system and how it’s used.