mbo

> Scala

Note about Scala's string interpolation. They can be used as pattern match targets.

  val s"${a} + ${b}" = "1 + 2";
  println(a) // 1
  println(b) // 2

To quote patio11's "Identity Theft, Credit Reports, and You":

> You want to communicate with the bank in a manner which suggests that you’re an organized professional who is capable of escalating the matter if the bank does not handle it themselves. [...] Mean words cannot hurt a bank. Threats cannot hurt a bank. Paper trails, though, are terrifying to regulated institutions. Your bank’s customer support representatives are taught to evaluate whether someone looks like they’re competent and collecting a paper trail. If they are, the CS rep is supposed to stop touching the case immediately and instead escalate them to a supervisor or to the legal department.

This is an active issue with Rate Your Music right now: https://rateyourmusic.com/rymzilla/view?id=6108

Unfixed for 4 months.

Ridiculous. A perversion of the true spirit of conkers.

>It seems like a bad move to have a participant responsible for drilling the holes and attaching the strings.

Part of the "point" of conkers is that conker-prep is just as much as a skill as the technique during the hitting phase.

I think this was just poor scrutineering (or corruption) on the organizers side.

> The key difference between print systems and web tech is responsiveness.

True, but... we were very good at building unresponsive websites in the early 2000s. Can't we just return to tradition and disable a lot of the responsive behaviour that we've layered onto HTML with an off-the-shelf stylesheet? Hardcode some width properties, ya know? (This is not a rhetorical question, genuinely curious).

haha what a coincidence - I love Quarto and have used the Observable integration! Thank-you for your work and efforts.

Anyone know how the Python interactive REPL was working in the bottom-right hand corner?

EDIT: Looks like it's completely bespoke workflow: https://github.com/3b1b/videos?tab=readme-ov-file#workflow

First of all, I will commend the Typst community for attempting to rectify the trainwreck that is LaTeX typesetting. It appears that they have succeeded.

So Typst has its own styling system, and its own scripting system, and plugin system via WASM... isn't this just HTML with extra steps? Not to mention that Typst doesn't support HTML export https://github.com/typst/typst/issues/188#issuecomment-14933..., which is a major impediment to vision-impaired accessibility in the academic community.

I think this is all a bit of a shame that there's been no major efforts to reform HTML as the go-to file format for scientific publishing instead. All the elements are there - <cite>, citation.js, KaTex, Web Components, good plotting libraries (Observable Plot), WASM. Was all this extra engineering effort required to get us a Markdown style syntax? I know people hate XML-based markup... but it's not _that_ bad, right?

Note that there's nothing stopping you from embedding the Obervable runtime straight into scripts littered throughout a HTML document, see https://maxbo.me/celine/ (my own work).

Seems like a Parquet or SQLite file would have been more appropriate

this is a good article on styling with custom elements too: https://www.keithcirkel.co.uk/css-classes-considered-harmful...

I hate to be negative, but I'm not entirely sure why this is advantageous over just dumping a bunch of HTML files into a folder. Why can't the code live in <script type="module">'s with `display: block` tagged, using esm.sh for libraries? Why do we have to use Markdown that has to get transpiled over a format that can be natively consumed by the browser?

Protomaps (https://protomaps.com/) uses this for their PMTiles HTTP range request lookups too right (https://docs.protomaps.com/pmtiles/)?

No love for <q>? It does curly quoting!

Bitbucket started as a Mercurial host.

The (internal unverified Atlassian) mythos goes, that in the early days, both GitHub and Bitbucket were on equal MAU footing, but as Git mindshare started to take over, the Bitbucket founder, a Mercurial fan, dragged their feet on adding Git support. This delay lost them the war.

Curiously, the interpunct in the title of this article (Wall·E) can be control F searched with ("walle") but all of your usages cannot (try "sometimes" and "clarify")

Out of interest, do you have any literature that you'd recommend instead?

I'm pretty sure it's weight distribution. Like I can tell the difference between a hybrid Camry and a pure ICE Camry based on how it bobs over speed bumps, not just in cornering / acceleration.

I _think_ I can tell whether a car is an ICE / hybrid / electric just by the way their weight shifts around corners. My friends maintain they cannot, but under test conditions, I'm sure they'd be fine.

There's a great quote in Vox's "Tony Hawk breaks down skateboarding’s legendary spots" (https://www.youtube.com/watch?v=omigBsOmtjw) from Iain Borden, an architectural historian:

"[...] I think what skateboarding's always been good at, is it tests our idea of what we want public space to be. Whether it's at the Southbank in London, the ledges at the Museum of Contemporary Art in Barcelona, The Warschauer benches in Berlin, or a 25-foot stair set in Lyon... skateboarders, I think, are a constant reminder that our cities can be creative and rich places."

> Other than the clever solution of using CSS, why would you do this?

Seems lightweight enough for maybe a music theory blog post or interactive notebook.

I would recommend a pilsner. Vegemite itself has stouty tones. The pilsener would provide some contrast.

Echoes of Haskell's `accursedUnutterablePerformIO` https://hackage.haskell.org/package/bytestring-0.10.8.1/docs... :

  This \"function\" has a superficial similarity to 'unsafePerformIO' but
  it is in fact a malevolent agent of chaos. It unpicks the seams of reality
  (and the 'IO' monad) so that the normal rules no longer apply. It lulls you
  into thinking it is reasonable, but when you are not looking it stabs you
  in the back and aliases all of your mutable buffers. The carcass of many a
  seasoned Haskell programmer lie strewn at its feet.
  Do not talk about \"safe\"! You do not know what is safe!
  Yield not to its blasphemous call! Flee traveller! Flee or you will be
  corrupted and devoured!

I did something similar for fragrances a little while ago: https://observablehq.com/@55th/every-fragrance-at-once

My employer uses a combination of Protocol Buffers (for the config schema definition) and Bazel/Starlark (for concrete instantiations). Configs are validated at build time and runtime using CEL (https://github.com/google/cel-spec).

"w/" is an abbreviation for "with". "w/ mice" should be read as "with mice".

Okay, clearly the feminist angle has fallen flat here as I, an anonymous user, am now being accused of virtue signaling. I'll try a more lowbrow angle:

This paper is what I'd characterize as "horny on main" (https://knowyourmeme.com/memes/horny-on-main). It's embarrassing. They've spent all this time doing impressive, cutting edge research just to make women (and girls!) dance for them. They could have chosen a dataset that at least made them look cool, rather than like weirdos. It weirded me out! Very likely weirded out others.

I would be okay with it because men are not as systematically objectified in our society and do not face the same barriers to entry to computer science as women.

The choice of test images here feels super inappropriate. Surely there's a more diverse and standardized dataset for benchmarking this task than what was chosen here.

I quote similar criticism from Dianne P. O'Leary:

> Suggestive pictures used in lectures on image processing ... convey the message that the lecturer caters to the males only. For example, it is amazing that the "Lena" pin-up image is still used as an example in courses and published as a test image in journals today.