Spaces are here!! Come read all about MSC1772 and its various friends, children and ancestors and the shape of things to come :) 🎉🍾🚀🛰🔭🦑 https://matrix.org/blog/2021/05/17/the-matrix-space-beta
@piggo The PS2, specially the original fat one, has top Empire Strikes Back aesthetics. That, plus hackability, and the oddball hardware architecture make it my favorite PlayStation: https://www.copetti.org/writings/consoles/playstation-2/
@darius @liaizon @djsundog The guy teaching the operating systems course liked the Sun pizzaboxes because for some reason (can't remember right now) they would segfault more easily on invalid C code than x86. So we would go write some code at home that apparently worked, to be in dismay next day when it broke in the lab. This was a great lesson about “works on my computer” never being a substitute for testing, specially for cross platform code.
@darius @liaizon @djsundog also I was reminded that there was also a couple of SGI Onyx 2 which we used for the computer graphics course (because OpenGL) and the distributed systems course (because it was the only NUMA machines around). There was also a cheap Linux x86 cluster assembled from old boxes for this second course, and we would write and run there parallel algorithms using PVM (in C) and MPI (Fortran). Somehow OpenMP was not yet a thing
@darius @liaizon @djsundog so today I was mulling over this and ended up chatting with a folk who studied with me and now is a teacher: it turns out now it's all Linux and Windows x86 workstations, and students don't get exposure to other operating systems and architectures. That is such a pity! To me it was wonderful that not only we got to know other OSes existed, but also could get a taste of a few of them just by going downstaira to the labs.
@fribbledom @Agris @BalooUriza when half of the published images have security vulnerabilities in them, or at least half at the time https://www.securityweek.com/analysis-4-million-docker-images-shows-half-have-critical-vulnerabilities was written (to cite one example of sorts), I would say the norm is crappiness.
Sure one can build good images, but if I have to do it myself (likely easier than analyzing existing images I would want to use), then I can as well shove the tarball in an HTTP server and use “machinectl pull-raw” 🧙♂️
For me the main point against Docker is that it favours the mindset of “we have no idea how our thing works or won't document how to install it, so here you have a possibly outdated, bloated full system image of what developers use when working on the code; run it in prduction YOLO”
Tired: web search results.
Wired: web search results with Pinterest removed.
(Side note: the diff I'm looking at is not even *that* long, but GitLab is dog slow on it nevertheless.)
TFW adding the “.patch” suffix to a merge request URL to display the diff directly because #GitLab is painfully slow to read a long set of changes.
“Traversing the list to find the corresponding watch descriptor makes this algorithm O(n * m/2) on average, with ’n’ being the number of inotify_event read, and ‘m’ the amount of file paths being watched. While not great, in practice it's reasonable for keeping tabs on a small number of files.”
On the other hand, this code makes zero allocations, so that's neat. It does so by adding a pointer to link structs which reside in BSS or the stack to each other without involving the heap.
This is the ideal scroll bars. You may not like it, but this is what peak performance looks like.
💻 Programming 🗽💿 Free Software 🎸 Music 🚂 Traveling — 🌍 https://perezdecastro.org
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!