No, sorry, I don’t know what kind of ass-backwards somersault your windows machine did this time. Your word doc is randomly missing every third paragraph? Too right mate.

Hence, Clojure. It’s not just functions that implement IFn… as the string of “cannot cast to clojure.lang.IFn” errors that I get because I couldn’t be bothered to validate my data’s shape is eager to inform me.

In fluent speech, the conjunction (the first “that”) is unstressed, and as a result some speakers reduce the vowel a bit toward schwa. However, if you told those speakers to carefully pronounce each word, I bet they would pronounce the conjunction and the pronoun the exact same same. A more common example of this kind of reduction is the word “to”, which is almost always reduced to /tə/ ([tə] ~ [tʊ] ~ [ɾə] depending on dialect and surrounding words) in everyday speech when unstressed.

Fun fact, you can reduce just about every unstressed vowel in English to schwa (if it’s not already a schwa) and still be largely understood.

dass das das das dass da ersetzen kann ist falsch

translation: that “das” can replace “dass” there is wrong.

same shit different barbarians

In grocery stores in many parts of the US at least, it is extremely hard not to find bread in plastic bags. Even the one of 3 near me that has its own bakery puts the bread in a plastic bag, and then in another bag that is paper with a plastic “window”, and the paper part has a PE wax lining for god knows what reason.

I mean… just rotate it 90 degrees ((()))

That’s some expensive cereal…

So you’re saying that you don’t like trying to relight the thermal oxidizer for the formaldehyde stream that went out due to spillover from another process, with an emergency flare? Got it.

I mean, sure, things like that are super dangerous, but at least they’re obviously, flashily dangerous and for that reason have a lot more attention paid to them. The real nasties are arguably the ones that aren’t so flashy but are much more common amd don’t have immediate effects. Formaldehyde and benzene will give you cancer, and acrylate monomers will make it so you one day wake up allergic to the modern world.

This post made me go try something in clojure again and man I forgot just how fucking good the language is. Everything fits together so nicely.

Mr. fancypants with a garage over there. Meanwhile, ain’t no public chargers for miles around here.

you mean let.

and then letting Hindley-Milner do the rest

Man I just built a new rig last November and went with nvidia specifically to run some niche scientific computing software that only targets CUDA. It took a bit of effort to get it to play nice, but it at least runs pretty well. Unfortunately, now I’m trying to update to KDE6 and play games and boy howdy are there graphics glitches. I really wish HPC academics would ditch CUDA for GPU acceleration, and maybe ifort + mkl while they’re at it.

So many solver solutions that day, either Z3 or Gauss-Jordan lol. I got a little obsessed about doing it without solvers or (god forbid) manually solving the system and eventually found a relatively simple way to find the intersection with just lines and planes:

1. Translate all hailstones and their velocities to a reference frame in which one stone is stationary at 0,0,0 (origin).
2. Take another arbitrary hailstone (A) and cross its (rereferenced) velocity and position vectors. This gives the normal vector of a plane containing the origin and the trajectory of A, both of which the thrown stone must intersect. So, the trajectory of the thrown stone lies in that plane somewhere.
3. Take two more arbitrary hailstones B and C and find the points and times that they intersect the plane. The thrown stone must strike B and C at those points, so those points are coordinates on the line representing the thrown stone. The velocity of the thrown stone is calculated by dividing the displacement between the two points by the difference of the time points of the intersections.
4. Use the velocity of the thrown stone and the time and position info the intersection of B or C to determine the position of the thrown stone at t = 0
5. Translate that position and velocity back to the original reference frame.

It’s a suboptimal solution in that it uses 4 hailstones instead of the theoretical minimum of 3, but was a lot easier to wrap my head around. Incidentally, it is not too hard to adapt the above algorithm to not need C (i.e., to use only 3 hailstones) by using line intersections. Such a solution is not much more complicated than what I gave and still has a simple geometric interpretation, but I’ll leave that as an exercise for the reader :)

Oh absolutely, I don’t blame KDE or arch repos lol. I did see that it was a KDE update but somehow didn’t clock the version number. I had it in my head that KDE6 was much farther off.

Didn’t realize this was happening and yay -Syu went brrr and it broke my shit. Probably doesn’t help that I’m running nvidia with linux (endeavouros). Wayland doesn’t work at all (black screen on login with only mouse ptr, wrong resolution), while Xorg is now much less smooth e.g. on the switching desktop animations. Moving windows around and in-window graphics are fine. Some graphical config stuff changed too; I’m still taking inventory.

I’m also currently playing with nvidia vs nvidia-dkms with different kernels to see if that solves anything.

EDIT: Looks like that my configuration was failing to set nvidia_drm modeset=1 correctly due to my unfamiliarity with dracut. Manually adding nvidia_drm.modeset=1 to my kernel cmdline makes Wayland work (and quite well at that), though Xorg is still laggy.

Huh TIL. Growing up with the merger, I suppose I’ve come to assume that non-merger folks have different pronunciations for any words with a- or o-adjacent spellings.

cot-caught merger be like that sometimes

<esc> <esc> <esc> <esc> <esc> <esc> :wa! <cr>

Professional zero finders of derivatives of mathematical models built from duct tape, prayers, and Jimmy’s observations from before he got cataracts.