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.

இல்லை, இது பேட்ரிக்.

single thread go brrr

A French-American guy (grew up in US) in my school described an encounter at a zoo when he was a young. Apparently, he ran up to the exhibit and shouted, “look! it’s a daddy fuck and a mommy fuck with a baby fuck!”, much to the chagrin of his parents.

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

Nijmegen? Is it particularly exceptional, or just normal Dutch? /'nɛɪ.meː.ɣə(n)/, in a GenAm accent I would imagine something like NYE-may-ghen or NAY-may-ghen… but being American, it’s not something I’ve ever actually heard one of my compatriots say aloud.

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.

you mean let.

and then letting Hindley-Milner do the rest

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 :)

  :wa! 

Pure by ocular spectroscopy = it looked good enough

Pharma distillation = tossing the chemical and buying a new bottle from Sigma

Retro-retro-Cope rearrangement = no reaction happened, go home and cry

I think water is rather rare as a coolant these days. Organics (chemical sense not farming sense) like propylene glycol or some kind of glyme aren’t potentially corrosive to metals if spilled, are harder to grow shit in, have lower volatility, and have a higher thermal limit. Maybe also with a little bit of antifouling agent thrown in. My main gripe with them is that if you do spill them, they don’t evaporate and you’re slipping over the floor for the next few days because you missed a spot.

But yeah, air cooling ftw

Just bought one of those brown monsters for a new build, can’t wait to try it

Khshenshchizhevoshitseh poviat wenkowovih

Yeah, transliterating to an English spelling doesn’t help much.

I think rz is linguistically equivalent to a soft r, so in this case rze would be “ре”, not “ж”. In some areas, rz is pronounced closer to the Czech ř. IIRC, ж transliterates to ż (not to be confused with ź, which is a soft z). The Polish Roman alphabet is very regular and well adapted to the language, representing palatalization and other non-Latin sounds as digraphs in a similar way to Italian or English.

The cyrillicization of Polish was historically done to a limited extent, but carried with it some, shall we say, sociopolitical baggage. There are also some peculiarities to Polish that either don’t exist or have ambiguous transliterations into Cyrillic, such as the Polish nasals ą and ę or ó (historically a long o, but currenly pronouned /u/).

Nonono, you don’t understand, flame wars build character! 'Twere the early aughts that made me the healthy and well adjusted person I am today!

Or at least, that’s what I’d say if what actually happened wasn’t that I became a jaded bastard and if I didn’t think it was just some ploy to drive engagement to let OP feel popular for a moment… in the best case scenario

Don’t worry, I was being 100% facetious! After all, γ is generally believed to have been a hard /g/ in Ancient Greek, which is the version of Greek that “graphic” is based on and is CLEARLY the wrong way to say gif :D

Kinda sorta un-jerking (but not really) for a moment, I don’t think that I’d include the rhotic in your hypothetical pronunciation in NASA and thus would say /neæ.sə/ over /neɚ.sə/. I also don’t palatalize the U in SCUBA (/sku:.bə/, not /sk^(j)u:bə/), but I suspect that’s just a dialectical difference.

Edit: I just saw your NZ lemmy instance name and now I understand the vowel choices. Cheers!

Well, you see, the g in gif stands for “graphics” which is ultimately from Greek “γραφικός,” and because this is the 21st century, γ in front of a close front vowel is pronounced as neither /g/ nor /d͡ʒ/ but rather /ʝ/, which is pronounced a bit like English’s y, so in its purest rendition gif is really pronounced “yiff”, which doubles as homage to the online communities that OP frequents.